Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

AssemblyBuilder.DefineDynamicModule Method (String, String, Boolean)

Defines a persistable dynamic module, specifying the module name, the name of the file to which the module will be saved, and whether symbol information should be emitted using the default symbol writer.

Namespace:  System.Reflection.Emit
Assembly:  mscorlib (in mscorlib.dll)
public ModuleBuilder DefineDynamicModule(
	string name,
	string fileName,
	bool emitSymbolInfo
)

Parameters

name
Type: System.String
The name of the dynamic module. Must be less than 260 characters in length.
fileName
Type: System.String
The name of the file to which the dynamic module should be saved.
emitSymbolInfo
Type: System.Boolean
If true, symbolic information is written using the default symbol writer.

Return Value

Type: System.Reflection.Emit.ModuleBuilder
A ModuleBuilder object representing the defined dynamic module.
ExceptionCondition
ArgumentNullException

name or fileName is null.

ArgumentException

The length of name or fileName is zero.

-or-

The length of name is greater than or equal to 260.

-or-

fileName contains a path specification (a directory component, for example).

-or-

There is a conflict with the name of another file that belongs to this assembly.

InvalidOperationException

This assembly has been previously saved.

NotSupportedException

This assembly was called on a dynamic assembly with the Run attribute.

ExecutionEngineException

The assembly for default symbol writer cannot be loaded.

-or-

The type that implements the default symbol writer interface cannot be found.

SecurityException

The caller does not have the required permission.

To define a persistable dynamic module, this assembly needs to be created with the Save or the RunAndSave attribute.

If you want the module to contain the assembly manifest, name should be the same as the name of the assembly (that is, the AssemblyName.Name property of the AssemblyName used to create the dynamic assembly) and fileName should be the same as the filename you specify when you save the assembly.

In an assembly with only one module, that module should contain the assembly manifest.

NoteNote

To suppress optimizations when debugging dynamic modules, apply the DebuggableAttribute attribute to the dynamic assembly before calling DefineDynamicModule. Create an instance of DebuggableAttribute with the DisableOptimizations flag and apply it using the SetCustomAttribute method. The attribute must be applied to the dynamic assembly. It has no effect if applied to the module.

NoteNote

Starting with the .NET Framework version 2.0 Service Pack 1, this member no longer requires ReflectionPermission with the ReflectionPermissionFlag.ReflectionEmit flag. (See Security Issues in Reflection Emit.) To use this functionality, your application should target the .NET Framework version 3.5 or later.

[Visual Basic, C#]

The code example below demonstrates how to create a persistent dynamic module with symbol emission using DefineDynamicModule.


	   AppDomain myAppDomain = Thread.GetDomain(); 
	   AssemblyName myAsmName = new AssemblyName();
	   myAsmName.Name = "MyAssembly";
	   AssemblyBuilder myAsmBuilder = myAppDomain.DefineDynamicAssembly(
							myAsmName,
							AssemblyBuilderAccess.Run);
	   // Create a dynamic module that can be saved as the specified DLL name. By
	   // specifying the third parameter as true, we can allow the emission of symbol info.
	   ModuleBuilder myModuleBuilder = myAsmBuilder.DefineDynamicModule("MyModule4",
									    "MyModule4.dll",
									     true);


.NET Framework

Supported in: 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.