Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Specifies that the compiler shouldn't insert an assembly manifest into the output file.
Syntax
/LN
Remarks
By default, /LN isn't in effect, and the compiler inserts an assembly manifest into the output file.
When you use /LN, you must also use one of the /clr (Common Language Runtime Compilation) options.
A managed program that doesn't have assembly metadata in the manifest is called a module. If you compile with /c (Compile Without Linking) and /LN, specify /NOASSEMBLY (Create a MSIL Module) in the linker phase to create the output file.
Create modules if you want to take a component-based approach to building assemblies. You can author types and compile them into modules. Then, you can generate an assembly from one or more modules. For more information on creating assemblies from modules, see .netmodule Files as Linker Input or Al.exe (Assembly Linker).
The default file extension for a module is .netmodule.
In releases before Visual Studio 2005, you created a module with /clr:noAssembly.
The MSVC linker accepts .netmodule files as input. The output file produced by the linker is an assembly or .netmodule with no run-time dependence on any of the .netmodules that you input to the linker. For more information, see .netmodule Files as Linker Input.
To set this compiler option in the Visual Studio development environment
- Specify
/NOASSEMBLY(Create a MSIL Module) in the linker phase to create the output file.
To set this compiler option programmatically
- You can't change this compiler option programmatically.