AppDomain.DefineDynamicAssembly Method (AssemblyName, AssemblyBuilderAccess, Evidence)
Defines a dynamic assembly using the specified name, access mode, and evidence.
Assembly: mscorlib (in mscorlib.dll)
[<ObsoleteAttribute("Assembly level declarative security is obsolete and is no longer enforced by the CLR by default. See http://go.microsoft.com/fwlink/?LinkID=155570 for more information.")>] abstract DefineDynamicAssembly : name:AssemblyName * access:AssemblyBuilderAccess * evidence:Evidence -> AssemblyBuilder [<ObsoleteAttribute("Assembly level declarative security is obsolete and is no longer enforced by the CLR by default. See http://go.microsoft.com/fwlink/?LinkID=155570 for more information.")>] override DefineDynamicAssembly : name:AssemblyName * access:AssemblyBuilderAccess * evidence:Evidence -> AssemblyBuilder
The unique identity of the dynamic assembly.
The mode in which the dynamic assembly will be accessed.
The evidence supplied for the dynamic assembly. The evidence is used unaltered as the final set of evidence used for policy resolution.
Return ValueType: System.Reflection.Emit.AssemblyBuilder
A dynamic assembly with the specified name and features.
Only fully trusted callers can supply their evidence when defining a dynamic Assembly. The runtime will map the Evidencethrough the security policy to determine the granted permissions. Partially trusted callers must supply a null evidence. If evidence is null, 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.
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.
During the development of code that emits dynamic assemblies, it is recommended that you use an overload of the DefineDynamicAssembly method that specifies evidence and permissions, supply the evidence you want the dynamic assembly to have, and 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.
First, the code example tries to create an instance of MyDynamicType by calling the CreateInstance method with an invalid assembly name, and catches the resulting exception.
The code example then adds an event handler for the AssemblyResolve event, and again tries to create an instance ofMyDynamicType. During the call to CreateInstance, the AssemblyResolve event is raised for the invalid assembly. The event handler creates a dynamic assembly that contains a type named MyDynamicType, gives the type a parameterless constructor, and returns the new dynamic assembly. The call to CreateInstance then finishes successfully, and the constructor for MyDynamicType displays a message at the console.
Available since 1.1