![]() This trend, however, is starting to be reversed. The stuff in system.dll was basically everything that wasn't "worthy" of being included in mscorlib. Then you don't have to waste time going and binding a whole bunch of different assemblies. If everybody is going to want to use something, then it makes sense to put it inside the assembly that everybody has to load. This includes things like HashTable and List. Originally, a lot of "optional" stuff (things that technically aren't required to run an app) was put into mscorlib because they were things that were highly likely to be used by everybody. It has the distinction of being the only assembly that the CLR requires to be loaded inside every managed process. Mscorlib does contains both native and managed code.Īmongst other things it contains the System.Object implementation, which must always be present in order for everything to work. I work on the CLR/BCL team and just answered your email.
0 Comments
Leave a Reply. |