One thing we are doing that will help here is starting from beta3 the ironpython codeplex sources will have the silverlight sources (including Chiron) and Ironpython.sln will be configured the way Ivan mentioned in the IronRuby alias so that a msbuild /p:Configuration="Release" builds the desktop version of ipy/dlr and msbuild /p:Configuration="Silverlight Release" builds the silverlight version.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jimmy Schementi Sent: Tuesday, June 10, 2008 4:44 PM To: Discussion of IronPython Subject: Re: [IronPython] System, Version 2.0.5.0 Silverlight is not a host, it's a platform, with unique compilers and libraries. The .NET framework shipped with Silverlight is not the same as what's on the desktop, though meant to look the same by having a similar API. Plus, there are "platform" specific features of each, like security levels and the file system on the Desktop and HtmlBridge and isolated storage on Silverlight. Point being, to use something on a specific platform, it must be built for that platform. The source code may be the same for each, but that's a detail of the implementation. If you look at your Silverlight installation location, there is mscorlib.dll, System.Windows.dll, etc ... all have "equivalent" Desktop versions, but they are definitely not interchangeable. This is what it's like living in a compiled world =P Make sense? ~Jimmy > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:users- > [EMAIL PROTECTED] On Behalf Of Ben Hall > Sent: Tuesday, June 10, 2008 4:17 PM > To: Discussion of IronPython > Subject: Re: [IronPython] System, Version 2.0.5.0 > > Thanks for your reply. Do you not think that will get really > confusing for people - having two different Microsoft.Scripting > assemblies based on the host? > > Cheers > > Ben > > On Tue, Jun 10, 2008 at 11:54 PM, Srivatsn Narayanan > <[EMAIL PROTECTED]> wrote: > > The DSL package has the languages and DLR sources compiled against > the silverlight CLR. The sources need to be compiled against the > desktop CLR for it to work with 2.0.0.0. For the latest desktop > IronPython you'd need to wait for IronPython beta 3 coming very soon. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:users- > [EMAIL PROTECTED] On Behalf Of Ben Hall > > Sent: Tuesday, June 10, 2008 3:49 PM > > To: Discussion of IronPython > > Subject: [IronPython] System, Version 2.0.5.0 > > > > Hello, > > > > I have just downloaded and upgraded my WinForms application to use > the > > latest Dynamic Languages for Silverlight Beta 2. I think I must be > > confused, but the two DLR assemblies (Microsoft.Scripting.Core, > > Version=2.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 and > > Microsoft.Scripting, Version=2.0.5.0, Culture=neutral, > > PublicKeyToken=31bf3856ad364e35) both reference System, Version > > 2.0.5.0 - the one shipped with Silverlight and not System, Version > > 2.0.0.0 as shipped with IronPython Beta 2. > > > > I expected the DLR assemblies to work in both WinForms and > Silverlight. > > > > As such, when I try and execute IronPython code, I get the following > exception. > > > > Unhandled Exception System.IO.FileNotFoundException: Could not load > > file or assembly 'System, Version=2.0.5.0, Culture=neutral, > > PublicKeyToken=7cec85d7bea7798e' or one of its dependencies. The > > system cannot find the file specified. > > File name: 'System, Version=2.0.5.0, Culture=neutral, > > PublicKeyToken=7cec85d7bea7798e' > > at IronPython.Compiler.Parser.Reset(SourceUnit sourceUnit, > > PythonLanguageFeatures languageFeatures) > > at IronPython.Compiler.Parser..ctor(Tokenizer tokenizer, ErrorSink > > errorSink, ParserSink parserSink, PythonLanguageFeatures > > languageFeatures) > > at IronPython.Compiler.Parser.CreateParser(CompilerContext context, > > PythonEngineOptions options, Boolean verbatim) > > at IronPython.Compiler.Parser.CreateParser(CompilerContext context, > > PythonEngineOptions options) > > at IronPython.Runtime.PythonContext.ParseSourceCode(CompilerContext > context) > > at Microsoft.Scripting.SourceUnit.Parse(CompilerOptions options, > > ErrorSink errorSink) > > at Microsoft.Scripting.SourceUnit.Compile(CompilerOptions options, > > ErrorSink errorSink) > > at Microsoft.Scripting.SourceUnit.Execute(Scope scope, ErrorSink > errorSink) > > at Microsoft.Scripting.SourceUnit.Execute(Scope scope) > > at Microsoft.Scripting.Hosting.ScriptScope.Execute(String code) > > at DLRHost.Engine.ScriptExecutor.ExecuteStatement(String code) in > > E:\Source > Control\DLRHost\trunk\src\DLRHost.Engine\ScriptExecutor.cs:line > > 33 > > > > If someone could explain this to me, that would be great! > > > > Thanks > > > > Ben > > Blog.BenHall.me.uk > > _______________________________________________ > > 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 > > > _______________________________________________ > 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 _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
