Yeah I wonder about the need to replicate the functions in such a critical namespace such as System.
Renaming the namespaces is a viable option. My application right now actually runs on IronPyton for ASP.Net (July 2007 CTP - gasp) and gasp, it ran on IronPython 2 Alpha and has not been updated ever since. And I need to do DLR hosting stuff, so I have been having IronPythonX2.dll and IronPYthonX2.dll with changes namespace so I can run both the hosting IronPython and IronPython for ASP.Net together. It's pretty ugly but it works for now. Dody G. On Tue, Aug 19, 2008 at 2:59 PM, Fernando Correia < [EMAIL PROTECTED]> wrote: > Thanks, Dody. I figured that could be an option. Not sure if I can > just remove classes from Microsoft.Scripting.Core, though. I wonder if > they are just copies of those in System.Core or if they are somewhat > tailored for this version of the DLR. > > Oh man, all this stuff about System.Core and Microsoft.Scripting.Core > is quite confusing. Is there some clarification somewhere about the > strategy of this move and how the final product will deal with the > compatibility issues? > > 2008/8/19 Dody Gunawinata <[EMAIL PROTECTED]>: > > Try to build the source yourself and manually refactor the System > namespace > > in Microsoft.Scripting.Core assembly and deal with anything that blows > up. > > This is the simplest workaround right now. I'll do that work today > because > > yeah, my project is tied with this issue as well. I prefer this thing is > > addressed in the next beta because otherwise I have to do the namespace > hack > > again and again. > -- nomadlife.org
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
