There was a discussion in cnblogs.com a couple of months ago. The discussion is about how CLR loads assembly, does CLR load the assembly wholely or step by step. Some people the community said that CLR loads the metadata first, and then load methods
according to execution of the assembly. Some other people said that CLR loads the assembly entirely. And some of them did experiments to prove their points, like: they created a tiny console application, and a big size .net assembly, with 100 classes,
each of the classes with 100 fields, 100 properties, 100 methods, and refers to the assembly, and measure the memory occupation of the application. The size of the assembly is about 10M bytes, but the memory occupation of the application is about 1M bytes.
Does this mean the CLR loads an assembly steps by steps?
Could some one explain how CLR loads assembly in detail ?
View Complete Post