.NET build and build process

Question

A building is a sequence consisting of compilation and layout.

In .NET, source code is compiled into an assembly containing the Common Intermediate Language and type information. At run time, the JIT compiler converts the CIL code into native code.

I do not understand in .NET how and when binding occurs.

Can someone explain the process?

Thanks in advance

Answer 1

There is no connection with C ++.

I mean that no intermediate "obj" / "lib" files exist, which can later be distributed and linked to other "obj" files. A reference to an assembly always has dynamic behavior (always a dynamic library), unlike the static C ++ link.

The combination of how is creating .netmodule . You can create .NET source code with the compiler in .netmodule instead of the assembly (see here , especially the section "Differences between the C # Compiler and the C ++ Compiler" , and then you can link these modules together into one assembly (see al.exe )

But this is an unusual practice - most assemblies contain one module, and this work (source → module → assembly) was done by the compiler (for example, csc.exe ) behind the scenes. Also, I don’t remember that any product is redistributed as a .netmodule set (and not as an assembly set).