Hi,
Thank you for fixing them.
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.
Note that a solution would be to modify (and possibliy rename to
SetMscorlib) LoadMscorlib so that it
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
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
I would recommend SetMscorlib over LoadMscorlib because that would not
restrict how you can create or load mscorlib.dll.
That feels like painting yourself into a corner to me. Using SetMscorlib would
require modifying DefineDynamicAssembly in a way that would make it hard to
remain compatible
Please see the attached patch.
I belive that this is actually an easier and cleaner solution than the
current one.
You can use Load, LoadFile, DefineDynamicAssembly, etc. to load
mscorlib.dll.
Kornél
Jeroen Frijters write:
I would recommend SetMscorlib over LoadMscorlib because that
Please see the attached patch.
I belive that this is actually an easier and cleaner solution than the
current one.
I disagree. You have to look at it from an API development point of view. This
creates a huge window for undefined behavior and dependencies on implementation
specifics,
We're excited to let you know that Tony Alexander Hild has invited you to
Dropbox!
Tony Alexander Hild has been using Dropbox to sync and share files online and
across computers, and thought you might want it too.
Visit http://www.dropbox.com/link/20.zqHyRNSn8o/NjE2Nzc0MzM5Nw to get started.
Hi there,
I'm trying the simple sample at: http://www.mono-project.com/MonoCurses
Application.Init (false);
Dialog d = new Dialog (40, 8, Hello);
d.Add (new Label (0, 0, Hello World));
Application.Run (d);
on an OpenSuse box.
But it doesn't work for me, it just exits and breaks the