Good question; right now there's not an easy answer, since Microsoft.Scripting.Silverlight is not packaged with IronPython ... i.e. IronPython on http://codeplex.com/ironpython is only ensured to work on the Desktop. The IronPython version on http://codeplex.com/sdlsdk will always work with the current released version of Silverlight. However, sdlsdk does not get updated as often as ironpython, and there's kind of a good reason for that.
As we're working on IronPython, we need it to stay working with internal builds of Silverlight. Also keeping it working with the public Silverlight bits at the same time would be significantly harder, as we'd need to have a branch for IronPython+DLR+SLBeta1 and backporting all our work to there to make sure it still works. It's the tradeoff of either releasing IronPython working when Silverlight releases, or having every release of IronPython always work on the current version of Silverlight. If we also shipped the Microsoft.Scripting.Silverlight that correspond to each IronPython release, it could just work with the public SL release. We'd need it to be tested though, and I'm not sure how much free time Dave has. =) I agree, it's a little confusing to see the "Silverlight Debug/Release" builds and have them not work. We should remove it if it won't build. So, does this piss you off? Personally I like that we're able to ship Python immediately with a new version of SL, but I'd like to know what you folks think. ~js On 5/3/08 11:58 AM, "Dan Eloff" <[EMAIL PROTECTED]> wrote: Trying to build the new Beta 2 "Silverlight Debug" but it references a file that does not exist either in the Silverlight SDK or IronPython. How can I fix this? Thanks, -Dan _______________________________________________ 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
