OK. Thanks a lot. In the meantime, I'll proceed try to modifying the namespaces in Microsoft.Scripting.Core (if it's actually possible. Hopefully there's no internal classes being used)
Dody G. On Tue, Aug 19, 2008 at 9:38 PM, Dino Viehland <[EMAIL PROTECTED]> wrote: > I'm continuing to look into it... We're going to have conflicting names > because Microsoft.Scripting.Core includes a superset of the functionality in > the v3.5 System.Core - and changing that would complicate our internal > builds quite a bit. But hopefully we can find a way to get the aliases > working in web site mode. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of Fernando Correia > Sent: Tuesday, August 19, 2008 11:33 AM > To: Discussion of IronPython > Subject: Re: [IronPython] defined in multiple assemblies (framework 3.5) > > This issue is very bad for my project too. Do you think there is a way > we can make IronPython compatible with the Framework 3.5? > > I find it appalling that we even have to consider that... > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > -- nomadlife.org
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
