Ok, another thought... can you GAC the DLR assemblies and then add an updated
compilers tag to web.config which includes the alias? Something like:
<system.codedom>
<compilers>
<compiler language="c#;cs;csharp" extension=".cs"
type="Microsoft.CSharp.CSharpCodeProvider, System, Version=%ASSEMBLY_VERSION%,
Culture=neutral, PublicKeyToken=%ECMA_PUBLICKEY%" warningLevel="1"
compilerOptions="/reference:DLR=Microsoft.Scripting.Core.dll"/>
</compilers>
</system.codedom>
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fernando Correia
Sent: Tuesday, August 19, 2008 4:19 AM
To: [EMAIL PROTECTED]; Discussion of IronPython
Subject: Re: [IronPython] defined in multiple assemblies (framework 3.5)
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
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
