Jimmy,<br><br>Please see this tweet: <span class="status-body"><span class="entry-content"> <a href="http://is.gd/22y9D" rel="nofollow" target="_blank">http://is.gd/22y9D</a><br><br>I'm running the vmware image of the latest opensuse 11.1 with Mono 2.4.2.3. The Moonlight/Ipy application I was developing acts like it is loading but nothing displays. It works fine using Ipy 2.6 B1 and Moonlight 1.9.5. The Clock and Repl python samples (IronRuby 0.9.0 samples) are also broken using Ipy 2.6 B2 and Moonlight 1.9.6 (the latest). The background for the clock displays but not the control. The Repl simply does not display. Additionally, tested against the agdlr 0.5.0 samples:<br>
<a href="http://twitter.com/railcar88/status/2692911187">http://twitter.com/railcar88/status/2692911187</a><br><br>My thought is that perhaps building against Silverlight 3 might have broken compatibility with Moonlight 1.9.6. It could just as well be something else on the Mono or Moonlight side too (hopefully not user error :-) ).<br>
<br>I'd like to use the latest of Ipy and the Moonlight Preview of Moonlight 2 to develop against.<br><br>Thanks,<br><br>Scott<br><br></span></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Message: 5<br>
Date: Mon, 10 Aug 2009 18:31:52 +0000<br>
From: Jimmy Schementi <<a href="mailto:Jimmy.Schementi@microsoft.com">Jimmy.Schementi@microsoft.com</a>><br>
Subject: Re: [IronPython] Omit SILVERLIGHT_3 from IronPython Build<br>
To: Discussion of IronPython <<a href="mailto:users@lists.ironpython.com">users@lists.ironpython.com</a>><br>
Cc: Discussion of IronPython <<a href="mailto:users@lists.ironpython.com">users@lists.ironpython.com</a>>,<br>
"<a href="mailto:users@lists.ironpython.com">users@lists.ironpython.com</a>" <<a href="mailto:users@lists.ironpython.com">users@lists.ironpython.com</a>><br>
Message-ID: <<a href="mailto:EAB5BBAE-6332-46F9-99F3-70F0407ADC1F@microsoft.com">EAB5BBAE-6332-46F9-99F3-70F0407ADC1F@microsoft.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Sorry for the confusion; the IronPython CODEPLEX sources are NOT<br>
buildable with Silverlight 2; the csproj files contain direct<br>
references to silverlight 3 assemblies. So you need to build with<br>
Silverlight 3 installed. However, if you want to ensure the assemblies<br>
still work on Silverlight 2, you'll have to remove the SILVERLIGHT_3<br>
flag; then you install SL2 and test everything out.<br>
<br>
You are NOT required to have the silverlight tools installed to build<br>
the ironpython binaries; just the silverlight 3 runtime.<br>
<br>
How come you have a SL2 requirement though? You can't download SL2<br>
from the web anymore, and everyones SL2 installs should be prompting<br>
them to update to SL3. SL3 should be entirely backward comaptible, so<br>
I'd like to know the reason your bound to SL2.<br>
<br>
~Jimmy<br>
<br>
On Aug 10, 2009, at 10:15 AM, "Jimmy Schementi" <<a href="mailto:Jimmy.Schementi@microsoft.com">Jimmy.Schementi@microsoft.com</a><br>
> wrote:<br>
<br>
> If you see errors in Stubs, then it's definitely not building in<br>
> "Silverlight Debug" or "Silverlight Release" configurations. I'll get<br>
> the codeplex sources and double check that things are working<br>
> properly, but please make sure your building in the Silverlight<br>
> configuration.<br>
><br>
> ~Jimmy<br>
><br>
> On Aug 10, 2009, at 9:00 AM, "Scott Scites" <<a href="mailto:railcar88@gmail.com">railcar88@gmail.com</a>><br>
> wrote:<br>
><br>
>> I've been unsuccessful at building IronPython 2.6 B2 for a<br>
>> Silverlight 2 environment. Are there any special requirements other<br>
>> than the Silverlight 2 developer tools for building IPy 2.6 B2 on a<br>
>> vista machine? I am using the Silverlight Release build and<br>
>> omitting the SILVERLIGHT_3 flag. Microsoft.Scripting.Core has<br>
>> numerous System library conflict errors related to the stubs.cs.<br>
>> The rest of the errors are related to the inability to find the IPy<br>
>> libraries in the referenced directory. Those may clear up if I can<br>
>> get past the errors related to stubs.cs.<br>
>><br>
>> If needed, I can provide specific build error messages...they are<br>
>> unavailable to me at the moment.<br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@lists.ironpython.com">Users@lists.ironpython.com</a><br>
>> <a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" target="_blank">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.ironpython.com">Users@lists.ironpython.com</a><br>
> <a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" target="_blank">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br>
><br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.ironpython.com">Users@lists.ironpython.com</a><br>
<a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" target="_blank">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br>
<br>
<br>
End of Users Digest, Vol 61, Issue 16<br>
*************************************<br>
</blockquote></div><br>