LocalReport.ExecuteReportInSandboxAppDomain Method

NOTE: This method is now obsolete.

Causes processing extensions and expressions to be run with limited permissions in an application domain.

Namespace: Microsoft.Reporting.WebForms
Assembly: Microsoft.ReportViewer.WebForms (in microsoft.reportviewer.webforms.dll)

Syntax

'Declaration
<ObsoleteAttribute("This method requires Code Access Security policy, which is deprecated.  For more information please go to https://go.microsoft.com/fwlink/?LinkId=160787.")> _
Public Sub ExecuteReportInSandboxAppDomain
'Usage
Dim instance As LocalReport

instance.ExecuteReportInSandboxAppDomain

[ObsoleteAttribute("This method requires Code Access Security policy, which is deprecated.  For more information please go to https://go.microsoft.com/fwlink/?LinkId=160787.")] 
public void ExecuteReportInSandboxAppDomain ()

[ObsoleteAttribute(L"This method requires Code Access Security policy, which is deprecated.  For more information please go to https://go.microsoft.com/fwlink/?LinkId=160787.")] 
public:
void ExecuteReportInSandboxAppDomain ()

/** @attribute ObsoleteAttribute("This method requires Code Access Security policy, which is deprecated.  For more information please go to https://go.microsoft.com/fwlink/?LinkId=160787.") */ 
public void ExecuteReportInSandboxAppDomain ()

ObsoleteAttribute("This method requires Code Access Security policy, which is deprecated.  For more information please go to https://go.microsoft.com/fwlink/?LinkId=160787.") 
public function ExecuteReportInSandboxAppDomain ()

Remarks

Important

This method is deprecated for .NET Framework 4 because the code access security (CAS) feature it relies on is deprecated in .NET Framework 4. Instead, the ReportViewer control always executes in the sandboxed application domain. To set the base permissions for the sandboxed application domain, use SetBasePermissionsForSandboxAppDomain. To allow full-trust processing extensions, use AddFullTrustModuleInSandboxAppDomain.

When used with .NET Framework 4, this method has no effect unless you use the <NetFx40_LegacySecurityPolicy> configuration element in the Web.config file of your ASP.NET application. This scenario is only applicable if you want to switch between the sandboxed application domain and current application domain modes.

For more information, see Code Access Security Policy Compatibility and Migration.

See the table below for the default application domain modes in different .NET Framework versions.

.NET Framework Version	LegacySecurityPolicy Enabled?	Default Application Domain	Useable Application Domain Modes
4	No (Default)	Sandboxed	Sandboxed
4	Yes	Current	Sandboxed and current
3.5	N/A	Current	Sandboxed and current

This mode is designed to enable untrusted reports that use untrusted processing extensions to run securely.

This mode negatively impacts performance.

See Also

Reference

LocalReport Class
LocalReport Members
Microsoft.Reporting.WebForms Namespace