That sounds like a good idea, and if I might suggest an addition: Make sure that the mono.dll is strongly named. That way, an installer can add mono.dll to the GAC for all .net programs to use, rather than maintaining a copy of mono.dll for each program. Once such an assembly is available, I'd be happy to use it for cross-platform development... I could use Mono's PlatformID code instead of MS's one to be sure of cross platform support.
--Oren > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On > Behalf Of Guenther Roith > Sent: Wednesday, July 10, 2002 1:51 PM > To: Oren Novotny > Cc: mono-list > Subject: Re: [Mono-list] System.PlatformID Issues > > > How is Mono addressing the issue of extending MS's framework in this > > way, since I've noticed that there are a few other additions. Programs > > using those additions (to the system/corlib) will all have problems when > > on MS's framework... > > There was once a discussion about this, I think, and the result was, all > additions should be put in the "mono namespace". The best way, would > perhaps > be compile these to a new assembly mono.dll, that could be distributed > with > such programs. > > Johannes > > > _______________________________________________ > Mono-list maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
