TypeBuilder.IsSecuritySafeCritical Property

Reference

Definition

Namespace:: System.Reflection.Emit

Assembly:: System.Reflection.Emit.dll

Assembly:: mscorlib.dll

Assembly:: netstandard.dll

Package:: System.Reflection.Emit v4.7.0

Source:: TypeBuilder.cs

Important

Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

Gets a value that indicates whether the current type is security-safe-critical; that is, whether it can perform critical operations and can be accessed by transparent code.

public:
 virtual property bool IsSecuritySafeCritical { bool get(); };

public override bool IsSecuritySafeCritical { get; }

member this.IsSecuritySafeCritical : bool

Public Overrides ReadOnly Property IsSecuritySafeCritical As Boolean

Property Value

Boolean

true if the current type is security-safe-critical; false if it is security-critical or transparent.

Exceptions

NotSupportedException

The current dynamic type has not been created by calling the CreateType() method.

Remarks

The IsSecurityCritical, IsSecuritySafeCritical, and IsSecurityTransparent properties report the transparency level of the type, as determined by the common language runtime (CLR). The combinations of these properties are shown in the following table:

Security level	IsSecurityCritical	IsSecuritySafeCritical	IsSecurityTransparent
Critical	`true`	`false`	`false`
Safe-critical	`true`	`true`	`false`
Transparent	`false`	`false`	`true`

Using these properties is much simpler than examining the security annotations of an assembly and its types, checking the current trust level, and attempting to duplicate the runtime's rules.

The runtime begins evaluating transparency levels at the assembly. For example, if the dynamic assembly is security-critical, annotations on types are ignored, and all types are security-critical.

By default, a dynamic assembly inherits the transparency of the assembly that emits it. You can override this default by using the AppDomain.DefineDynamicAssembly(AssemblyName, AssemblyBuilderAccess, IEnumerable<CustomAttributeBuilder>), AppDomain.DefineDynamicAssembly(AssemblyName, AssemblyBuilderAccess, String, Boolean, IEnumerable<CustomAttributeBuilder>), or AppDomain.DefineDynamicAssembly(AssemblyName, AssemblyBuilderAccess, String, Evidence, PermissionSet, PermissionSet, PermissionSet, Boolean, IEnumerable<CustomAttributeBuilder>) method overload and specifying security attributes. You cannot elevate security levels by doing this; that is, transparent code cannot emit security-critical or security-safe-critical code. Attributes must be specified when the dynamic assembly is created, or they do not take effect until the assembly has been saved to disk and reloaded.

Note

Default inheritance is limited to the runtime's evaluation of transparency. No attributes are applied to the dynamic assembly. If you want to add security attributes, you must apply them yourself.

For more information about reflection emit and transparency, see Security Issues in Reflection Emit. For information about transparency, see Security Changes.

Applies to

Jaa