AppDomain.DefineDynamicAssembly Method (AssemblyName, AssemblyBuilderAccess, Evidence, PermissionSet, PermissionSet, PermissionSet)

Defines a dynamic assembly using the specified name, access mode, evidence, and permission requests.

Namespace:  System
Assembly:  mscorlib (in mscorlib.dll)

public final function DefineDynamicAssembly(
	name : AssemblyName, 
	access : AssemblyBuilderAccess, 
	evidence : Evidence, 
	requiredPermissions : PermissionSet, 
	optionalPermissions : PermissionSet, 
	refusedPermissions : PermissionSet
) : AssemblyBuilder

Parameters

name
Type: System.Reflection.AssemblyName

The unique identity of the dynamic assembly.

access
Type: System.Reflection.Emit.AssemblyBuilderAccess

The mode in which the dynamic assembly will be accessed.

evidence
Type: System.Security.Policy.Evidence

The evidence supplied for the dynamic assembly. The evidence is used unaltered as the final set of evidence used for policy resolution.

requiredPermissions
Type: System.Security.PermissionSet

The required permissions request.

optionalPermissions
Type: System.Security.PermissionSet

The optional permissions request.

refusedPermissions
Type: System.Security.PermissionSet

The refused permissions request.

Return Value

Type: System.Reflection.Emit.AssemblyBuilder
Represents the dynamic assembly created.

Implements

_AppDomain.DefineDynamicAssembly(AssemblyName, AssemblyBuilderAccess, Evidence, PermissionSet, PermissionSet, PermissionSet)

ExceptionCondition
ArgumentNullException

name is a null reference (Nothing in Visual Basic).

ArgumentException

The Name property of name is a null reference (Nothing in Visual Basic).

-or-

The Name property of name begins with white space, or contains a forward or backward slash.

AppDomainUnloadedException

The operation is attempted on an unloaded application domain.

The permission requests specified for requiredPermissions, optionalPermissions, and refusedPermissions are used only if evidence is also supplied, or if the dynamic assembly is saved and reloaded into memory.

NoteNote:

During the development of code that emits dynamic assemblies, it is recommended that you include SecurityPermissionFlag.SkipVerification in refusedPermissions. Including SkipVerification in the refusedPermissions parameter ensures that the MSIL is verified. A limitation of this technique is that it also causes SecurityException to be thrown when used with code that demands full trust.

Only fully trusted callers can supply their evidence when defining a dynamic Assembly. The runtime will map the Evidence through the security policy to determine the granted permissions. Partially trusted callers must supply a null evidence. If evidence is a null reference (Nothing in Visual Basic), the runtime copies the permission sets, that is, the current grant and deny sets, from the caller's Assembly to the dynamic Assembly being defined and marks policy as resolved.

If the dynamic Assembly is saved to disk, subsequent loads will get grants based on policies associated with the location where the Assembly was saved.

This method should only be used to define a dynamic assembly in the current application domain. For more information, see the Load(AssemblyName) method overload.

NoteNote:

In the .NET Framework versions 1.0, 1.1, and 2.0, the declarative security attributes applied to a dynamic assembly by using the requiredPermissions, optionalPermissions, and refusedPermissions parameters are stored in the old XML metadata format. See Emitting Declarative Security Attributes.

The following example demonstrates the DefineDynamicAssembly method and AssemblyResolve event.

For this code example to run, you must provide the fully qualified assembly name. For information about how to obtain the fully qualified assembly name, see Assembly Names.

No code example is currently available or this language may not be supported.

Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98

The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

.NET Framework

Supported in: 3.5, 3.0, 2.0, 1.1, 1.0
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft