Hi, There simply is no special case for building mscorlib.dll.
There is a /nostdlib option however that enables features required for building mscorlib.dll. I would recommend SetMscorlib over LoadMscorlib because that would not restrict how you can create or load mscorlib.dll. Kornél Jeroen Frijters wrote: >> I've just realized that DefineDynamicAssemblyImpl should not hardcode >> the name "mscorlib" since C# compiler is able to us any name when >> compiling with nostdlib. > > The hardcoded name bother me too, but then I couldn't think of any realistic > scenario where you'd build an mscorlib with a different name. Do you have any > examples? > > Also, how does gmcs know that it is compiling mscorlib? > > BTW, the solution I would prefer would be to add DefineMscorlib() (taking the > same parameters as DefineDynamicAssembly). > > Regards, > Jeroen > _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
