Ok - so that makes sense. So to use some C# 4 features with Silverlight and IronPython you *will* need a version of IronPython for Silverlight built specifically against Silverlight 4. I guess that means that apps using that version of IronPython *won't* work in earlier versions of Silverlight.
Yes, which is true for any app using C# dynamic as well, or apps that depend on SL4 specific features. In general versions of IronPython built against (for example) Silverlight 2 *can* use features from Silverlight 3. (Try Python uses IronPython that was built against Silverlight 2 - but dynamically uses some Silverlight 3 APIs if they are available.) As Silverlight 4 includes a different version of the CLR - and not just different API sets - I guess it particularly makes a difference if you are compiling C# code that works with IronPython. Odd and annoying that it won't even add references to earlier versions though. Does *everything* need to be specially compiled to be used with .NET 4? The *current* Silverlight builds can use SL4 features; like webcam, etc. This is because IronPython calls .NET APIs dynamically. However, since the Silverlight 2 builds don't statically depend on any of the new APIs in the Silverlight 4, any CLR4 features that the compilers/libraries usually depend on in .NET 4 aren't available in Silverlight 4; that's what the Silverlight 4 build will do for you. With regard to adding references to assemblies; as long as the same APIs exist in both versions of Silverlight, it will work in both, regardless of which compiler you use. It's the same situation with different .NET versions. Did I miss something where someone reported not being able to do this?
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
