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 <[EMAIL PROTECTED]>: > - 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 of > System.Core facilities in their code base. The nicest thing about .Net 3.5 > 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 .Net > 3.5 libraries. _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
