.NET building process and linking

Question

Building is the sequence composed of compiling and linking.

In .NET the source code is compiled into the assembly that contains Common Intermediate Language and type info. At run time the JIT compiler converts the CIL code into native code.

I do not understand, in .NET ,how and when the linking is occurring.

Can someone please explain the process ?

Thanks in advance

@SergRogovtsev [Linker (computing)](http://en.wikipedia.org/wiki/Linker_%28computing%29) — Nasreddine, Aug 27 '12 at 08:44
in c++ : [linking](http://cplus.about.com/od/glossar1/g/linkdefn.htm) ( also see lhttp://www.cprogramming.com/compilingandlinking.html) I wanted to know about that process in .NET — ProgNet, Aug 27 '12 at 09:29

score 13 · Accepted Answer · answered Aug 27 '12 at 10:13

There's no linking in terms of C++.

I mean, there's no any intermediate "obj"/"lib" files, that can be distributed and linked with another "obj" files later. Reference to an assembly always has dynamic behavior (always dynamic-link library), as opposed to C++ static linking.

Something like linking is a creation of .netmodule. You can build .NET source code with compiler into .netmodule instead of assembly (look here, especially section "Differences Between C# Compiler and C++ Compiler Output"), and later you can link these modules together into a single assembly (see al.exe).

But this is uncommon practice - most of assemblies contains single module, and this work (source -> module -> assembly) has been done by compiler (e.g., csc.exe) behind the scenes. Also, I can't remember any product being redistributed as a set of .netmodule (not as a set of assemblies).

.NET building process and linking

1 Answers1