[IronPython] defined in multiple assemblies (framework 3.5)
empirebuilder at gmail.com
Tue Aug 19 04:28:27 PDT 2008
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.
On Tue, Aug 19, 2008 at 2:18 PM, Fernando Correia <
fernandoacorreia at gmail.com> wrote:
> That's a huge issue for my project. I'm trying to leverage the DLR and
> IronPython on a ASP.NET application that targets 3.5. I hope there is
> a work-around.
> 2008/8/19 Dody Gunawinata <empirebuilder at gmail.com>:
> > - This pretty much locks up IronPython 2 from any .Net 3.5 based website.
> > The ASP.Net MVC framework is based on .Net 3.5 too and they use a bunch
> > System.Core facilities in their code base. The nicest thing about .Net
> > is to be able to use LINQ on code behind and right now when I compile my
> > application, I got a bunch of warnings about duplicated LINQ definition
> > methods existing in 2 assemblies. Now I cannot use Action<> or Func<> in
> > code behind.
> > - I think this will prevent the next IP for ASP.Net to be able to use
> > 3.5 libraries.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users