[IronPython] System, Version 2.0.5.0

[Rainer Worbis]

Thank you, I will try that. Is there any chance to integrate a version of JScript into these Libraries?

Rainer

-----Ursprüngliche Nachricht-----
Von: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] Im Auftrag von Ben Hall
Gesendet: Mittwoch, 11. Juni 2008 10:24
An: Discussion of IronPython
Betreff: Re: [IronPython] System, Version 2.0.5.0

Not at the moment. Sounds like Beta 3 will be the next package,
hopefully IronRuby will be packaged at the same time (I have requested
a set of binaries already).

To get this Dynamic silverlight package to compile for the desktop,
what you need to do is this:
1) Add a new build configuration.
2) For each project in the properties, you need to remove the
SILVERLIGHT compile flag (done on the Build tab of the properties).
3) Update all the references for the .Net 2.0 assemblies (mscorlib,
system) to use .Net 2.0.0.0 and not Silverlight.

When you compile, the code has special checks to see if the
SILVERLIGHT flag has been set, if it hasn't (because we removed it on
the properties) then that code isn't compiled into the release.  As
such, it will work on the desktop.

This step should have been done for us in Beta 3 so we can just
compile the code for desktop\silverlight based on our requirements.

Hope this makes sense,

Ben


On Wed, Jun 11, 2008 at 5:51 AM, Rainer Worbis <r.worbis at cubido.at> wrote:
> Hallo,
>
>
> Is there an 'easy' to use package which includes IronPython, Ruby and JScript for use with desktop applications - or an documentation how to compile these things from an silverlight distributation?
>
> Rainer
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] Im Auftrag von Srivatsn Narayanan
> Gesendet: Mittwoch, 11. Juni 2008 00:54
> An: Discussion of IronPython
> Betreff: Re: [IronPython] System, Version 2.0.5.0
>
> 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: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] 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
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
_______________________________________________
Users mailing list
Users at lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com