Doh! I forgot you probably need to use the fully qualified assembly name - /reference:DLR=Microsoft.Scripting.Core, Version=1.0.0.4000, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
From: Dody Gunawinata [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 19, 2008 9:40 AM To: Dino Viehland Cc: Discussion of IronPython Subject: Re: [IronPython] defined in multiple assemblies (framework 3.5) Yikes.. "Error 19 Metadata file 'Microsoft.Scripting.Core.dll' could not be found". This is weird. <compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0<http://2.0.0.0>, Culture=neutral, PublicKeyToken=b77a5c561934e089" compilerOptions="/reference:DLR=Microsoft.Scripting.Core.dll"> <providerOption name="CompilerVersion" value="v3.5"/> <providerOption name="WarnAsError" value="false"/> </compiler> On Tue, Aug 19, 2008 at 7:00 PM, Dino Viehland <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: 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]> [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of Fernando Correia Sent: Tuesday, August 19, 2008 4:19 AM To: [EMAIL PROTECTED]<mailto:[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<http://ASP.NET> application that targets 3.5. I hope there is a work-around. 2008/8/19 Dody Gunawinata <[EMAIL PROTECTED]<mailto:[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<mailto:Users@lists.ironpython.com> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com -- nomadlife.org<http://nomadlife.org>
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
