I know that this is Windows PE32, but I also know that the deployment unit in .NET is an assembly, which in turn has a manifest and can consist of several managed modules.
My questions:
1) How to create several managed modules when creating a project, for example, in the lib class or in a console application, etc.
2) Is there a way to tell this to the compiler (for example, using project properties) to split source code files into several managed modules. If so, what is the use of this?
3) Can managed modules span assemblies?
4) Are separate files created on disk when the source code is compiled or are they created in memory and directly built into the assembly?
EDIT:
@John:
For 2): So, does compiling / creating a source in visual studio always create one managed module? If so, I do not understand why VS does not provide a mechanism for this, despite the fact that .NET supports this. I agree that it would be uncontrollable to create an assembly with modules from different languages. Is this the only reason .NET allows you to create assemblies with multiple modules? I read in Richter CLR via C # that modules can also span assemblies, and this can help reduce assembly sizes and reduce memory by loading assemblies on demand when certain functionality is called for the first time, but I'm not quite sure why place the module in assemblies, why not just create a new assembly in which implicity creates a new module in the process. You still get the same benefits.
4) ".netmodule".
VS ".netmodule", obj. .pdb,.dll/.exe * FileListAbsolute , , , .
EDIT:
@Jon: CLR # (3- ) Pg 43:
, , , ( , ) .
", .
. , ,
, , ,
. , (ISV),
(
Microsoft Logo). ,
.
, codeBase
(. 3) . codeBase
URL, , . "