http://www.codeplex.com/sdlsdk/Wiki/View.aspx?title=Homesdlsdk Wiki Rss Descriptionhttp://sdlsdk.codeplex.com/wikipage?version=31<div class="wikidoc"><h1>These site is obsolete and just here for archival purposes. Go to IronRuby and IronPython&#39;s CodePlex sites for all Silverlight-related content.</h1> Please visit the respective pages for IronRuby and IronPython releases, which work in Silverlight &quot;out of the box&quot;; this project was merged directly into the languages releases.<br /><br /><b><a href="http://ironruby.net/browser/" class="externalLink">IronRuby in Silverlight<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://ironpython.net/browser/" class="externalLink">IronPython in Silverlight<span class="externalLinkIcon"></span></a></b><br /><br /><i>Note: IronRuby also contains IronPython binaries for using them together. Unless you need a specific version of IronPython, just download IronRuby&#39;s latest release to get both.</i><br /><br />This site&#39;s discussions and issue tracker is no longer moderated. If you have any questions on using IronRuby and IronPython in Silverlight, please post them on the language&#39;s mailing list:<br /><br /><b><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" class="externalLink">Join the IronRuby Mailing List<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" class="externalLink">Join the IronPython Mailing List<span class="externalLinkIcon"></span></a></b><br /></div><div class="ClearBoth"></div>jimmyschFri, 30 Apr 2010 05:17:39 GMTUpdated Wiki: Home 20100430051739Ahttp://sdlsdk.codeplex.com/wikipage?version=30<div class="wikidoc"><h1>These site is obsolete and just here for archival purposes. Go to IronRuby and IronPython&#39;s CodePlex sites for all Silverlight-related content.</h1> Please visit the respective pages for IronRuby and IronPython releases, which work in Silverlight &quot;out of the box&quot;; this project was merged directly into the languages releases.<br /><br /><b><a href="http://ironruby.net/download/" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://ironpython.net/download/" class="externalLink">IronPython<span class="externalLinkIcon"></span></a></b><br /><br /><i>Note: IronRuby also contains IronPython binaries for using them together. Unless you need a specific version of IronPython, just download IronRuby&#39;s latest release to get both.</i><br /><br />This site&#39;s discussions and issue tracker is no longer moderated. If you have any questions on using IronRuby and IronPython in Silverlight, please post them on the language&#39;s mailing list:<br /><br /><b><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" class="externalLink">Join the IronRuby Mailing List<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" class="externalLink">Join the IronPython Mailing List<span class="externalLinkIcon"></span></a></b><br /></div><div class="ClearBoth"></div>jimmyschFri, 30 Apr 2010 05:17:04 GMTUpdated Wiki: Home 20100430051704Ahttp://sdlsdk.codeplex.com/wikipage?version=29<div class="wikidoc"><h1>These site is obsolete and just here for archival purposes. Go to IronRuby and IronPython's CodePlex sites for all Silverlight-related content.</h1> Please visit the respective pages for IronRuby and IronPython releases, which work in Silverlight &quot;out of the box&quot;.<br /><br /><b><a href="http://ironruby.net/Download" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://ironpython.codeplex.com" class="externalLink">IronPython<span class="externalLinkIcon"></span></a></b><br /><br /><i>Note: IronRuby also contains IronPython binaries for using them together. Unless you need a specific version of IronPython, just download IronRuby's latest release to get both.</i><br /><br />This site's discussions and issue tracker is no longer moderated. If you have any questions on using IronRuby and IronPython in Silverlight, please post them on the language's mailing list:<br /><br /><b><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" class="externalLink">Join the IronRuby Mailing List<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" class="externalLink">Join the IronPython Mailing List<span class="externalLinkIcon"></span></a></b><br /></div><div class="ClearBoth"></div>jimmyschTue, 10 Nov 2009 09:46:24 GMTUpdated Wiki: Home 20091110094624Ahttp://sdlsdk.codeplex.com/wikipage?version=28<div class="wikidoc"><h1>These site is obsolete and just here for archival purposes. Go to IronRuby and IronPython's CodePlex sites for all Silverlight-related content.</h1> Please visit the respective pages for IronRuby and IronPython releases, which work in Silverlight out of the box.<br /><br /><b><a href="http://ironruby.net/Download" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://ironpython.codeplex.com" class="externalLink">IronPython<span class="externalLinkIcon"></span></a></b><br /><br /><i>Note: IronRuby also contains IronPython binaries for using them together. Unless you need a specific version of IronPython, just download IronRuby's latest release to get both.</i><br /><br />This site's discussions and issue tracker is no longer moderated. If you have any questions on using IronRuby and IronPython in Silverlight, please post them on the language's mailing list:<br /><br /><b><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" class="externalLink">Join the IronRuby Mailing List<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" class="externalLink">Join the IronPython Mailing List<span class="externalLinkIcon"></span></a></b><br /></div><div class="ClearBoth"></div>jimmyschTue, 10 Nov 2009 09:46:02 GMTUpdated Wiki: Home 20091110094602Ahttp://sdlsdk.codeplex.com/wikipage?version=27<div class="wikidoc"><h1>These site is obsolete and just here for archival puroses. Go to IronRuby and IronPython's CodePlex sites for all Silverlight-related content.</h1> Please visit the respective pages for IronRuby and IronPython releases, which work in Silverlight out of the box.<br /><br /><b><a href="http://ironruby.net/Download" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://ironpython.codeplex.com" class="externalLink">IronPython<span class="externalLinkIcon"></span></a></b><br /><br /><i>Note: IronRuby also contains IronPython binaries for using them together. Unless you need a specific version of IronPython, just download IronRuby's latest release to get both.</i><br /><br />This site's discussions and issue tracker is no longer moderated. If you have any questions on using IronRuby and IronPython in Silverlight, please post them on the language's mailing list:<br /><br /><b><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" class="externalLink">Join the IronRuby Mailing List<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" class="externalLink">Join the IronPython Mailing List<span class="externalLinkIcon"></span></a></b><br /></div><div class="ClearBoth"></div>jimmyschTue, 10 Nov 2009 03:32:45 GMTUpdated Wiki: Home 20091110033245Ahttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Home&version=26<div class="wikidoc"><h1>IronPython and IronRuby in Silverlight are no longer hosted here!</h1> Please visit the respective pages for IronRuby and IronPython releases, which work in Silverlight out of the box.<br /><br /><b><a href="http://ironruby.net/Download" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://ironpython.codeplex.com" class="externalLink">IronPython<span class="externalLinkIcon"></span></a></b><br /><br /><i>Note: IronRuby also contains IronPython binaries for using them together. Unless you need a specific version of IronPython, just download IronRuby's latest release to get both.</i><br /><br />This site is no longer moderated. If you have any questions on using IronRuby and IronPython in Silverlight, please post them on the language's mailing list:<br /><br /><b><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" class="externalLink">Join the IronRuby Mailing List<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" class="externalLink">Join the IronPython Mailing List<span class="externalLinkIcon"></span></a></b><br /></div><div class="ClearBoth"></div>jimmyschFri, 17 Jul 2009 01:54:09 GMTUpdated Wiki: Home 20090717015409Ahttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Home&version=25<div class="wikidoc"><h1>IronPython and IronRuby in Silverlight are no longer hosted here!</h1> Please visit the respective pages for IronRuby and IronPython releases, which work in Silverlight out of the box.<br /><br /><b><a href="http://ironruby.net/Download" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://ironpython.codeplex.com" class="externalLink">IronPython<span class="externalLinkIcon"></span></a></b><br /><br />This site is no longer moderated. If you have any questions on using IronRuby and IronPython in Silverlight, please post them on the language's mailing list:<br /><br /><b><a href="http://rubyforge.org/mailman/listinfo/ironruby-core" class="externalLink">Join the IronRuby Mailing List<span class="externalLinkIcon"></span></a></b><br /><b><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" class="externalLink">Join the IronPython Mailing List<span class="externalLinkIcon"></span></a></b><br /></div><div class="ClearBoth"></div>jimmyschFri, 17 Jul 2009 01:52:44 GMTUpdated Wiki: Home 20090717015244Ahttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Home&version=24<div class="wikidoc"><h1>IronPython and IronRuby in Silverlight are no longer hosted here!</h1> Please visit the respective pages for IronRuby and IronPython releases, which work in Silverlight out of the box.<br /><br /><a href="http://ironruby.net/Download" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a><br /><a href="http://ironpython.codeplex.com" class="externalLink">IronPython<span class="externalLinkIcon"></span></a><br /></div><div class="ClearBoth"></div>jimmyschFri, 17 Jul 2009 01:36:26 GMTUpdated Wiki: Home 20090717013626Ahttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hosting&version=10<div class="wikidoc"><h1>Hosting the DLR in Silverlight</h1> Hosting a dynamic language in Silverlight gives any Silverlight application (in any Silverlight language: C#/VB/Ruby/Python/JScript/others) the ability to run code in either Python, Ruby, JScript, or any other DLR-based language, from inside itself. For more information on the DLR and hosting, see <a href="http://dlr.codeplex.com/Wiki/View.aspx?titleDocs%20and%20specs&amp;referringTitleHome" class="externalLink">http://dlr.codeplex.com/Wiki/View.aspx?titleDocs%20and%20specs&amp;referringTitleHome<span class="externalLinkIcon"></span></a><br /> <h2>Differences between desktop and Silverlight</h2> The code necessary to host the DLR inside of Silverlight is different than on the desktop. Also, the code different between static and dynamic languages. In both cases, they only differ in how you construct the ScriptRuntimeSetup object. <h3>Discovering languages</h3> The first difference is how ScriptRuntimeSetup finds out the available languages. This information can either be loaded from a configuration file inside the XAP (language.config), or from the already-loaded assemblies themselves. The desktop does not allow loading from the assemblies, since it doesn't want to encourage loading all the language assemblies when they are not needed. However, Silverlight pre-loads all assemblies anyway, so both options are given in Silverlight.<br /><br />Microsoft.Scripting.Silverlight.Configuration has helper methods to load the configuration from either a language.config from the XAP file, or, to avoid having the config file, the language assemblies themselves. <h3>Platform Adaptation Layer</h3> The desktop and Silverlight differ in a big way when it comes to the File system; Silverlight does not have access to the machine's file system. Instead, it can only access files inside the XAP file, or in Isolated Storage. The DLR abstracts platform functionality into a PlatformAdaptationLayer (PAL), which can be changed by supplying a custom ScriptHost, which knows about a custom PAL. <br /><br />The DLR's default PAL doesn't define any behavior for Silverlight; it just throws &quot;NotImplementedException&quot; if any platform functionality is used. Microsoft.Scripting.Silverlight.BrowserScriptHost is a custom ScriptHost which knows about an internal BrowserPAL class, which directs any read-only file system access to the XAP.<br /> <h2>Hosting the DLR from C# or VB</h2> The following tells the ScriptRuntimeSetup about the avaliable languages from the loaded assemblies, and sets the HostType to BrowserScriptHost, which will make read-only platform-specific features work. It also pre-references platform assemblies so AddReference/LoadAssembly doesn't need to be called from script code. <h3>C#</h3> <pre> using Microsoft.Scripting.Hosting; using Microsoft.Scripting.Silverlight; ScriptRuntimeSetup setup = Configuration.LoadFromAssemblies(Package.GetManifestAssemblies()); setup.HostType = typeof(BrowserScriptHost); ScriptRuntime runtime = new ScriptRuntime(setup); // load platform assemblies so you don't need to call LoadAssembly in script code. foreach (string name in new string[] { &quot;mscorlib&quot;, &quot;System&quot;, &quot;System.Windows&quot;, &quot;System.Windows.Browser&quot;, &quot;System.Net&quot; }) { runtime.LoadAssembly(runtime.Host.PlatformAdaptationLayer.LoadAssembly(name)); } // now the desktop and Silverlight are the same ... ScriptEngine engine = runtime.GetEngine(&quot;Python&quot;) ScriptSource source = engine.CreateScriptSourceFromString(&quot;System.Windows.Browser.HtmlPage.Document.Message.innerHTML = 'Hello, World'&quot;) source.Compile().Execute(); </pre><br /> <h2>Hosting the DLR from Python, Ruby, or JScript</h2> Since the DLR/Silverlight integration is a C# application and hosts the DLR itself, the above work is already done for a dynamic language. Therefore, dynamic languages only need access to the ScriptRuntime or ScriptRuntimeSetup objects.<br /> <h3>Ruby</h3> <pre> require 'Microsoft.Scripting' include Microsoft.Scripting.Silverlight include Microsoft.Scripting.Hosting runtime = ScriptRuntime.new(DynamicApplication.current.runtime.setup) # or, is you just want to reuse the ScriptRuntime object: runtime = DynamicApplication.current.runtime </pre><br /> <h3>Python</h3> <pre> import clr clr.AddReference(&quot;Microsoft.Scripting&quot;) from Microsoft.Scripting.Hosting import ScriptRuntime, ScriptRuntimeSetup from Microsoft.Scripting.Silverlight import DynamicApplication runtime = ScriptRuntime(DynamicApplication.Current.Runtime.Setup # or, is you just want to reuse the ScriptRuntime object: runtime = DynamicApplication.Current.Runtime </pre></div>jimmyschFri, 15 May 2009 18:06:22 GMTUpdated Wiki: Hosting 20090515060622Phttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Extensions&version=3<div class="wikidoc"> <i>This is a Silverlight 3 feature only. For similar behavior in Silverlight 2, see Chiron.exe.confg</i><br /> <br />Silverlight 3 supports <b>caching of transparent platform extensions</b>, which in English means extensions of Silverlight (Controls, DLR, etc) can be downloaded on-demand and cached by the browser the first time the Silverlight application is visited, rather than packaging everything inside the XAP. While Silverlight 2 supported loading assemblies from outside the XAP, some domains (Microsoft.com, for example) do not allow the transmission of DLLs, so a Silverlight &quot;extension&quot; (.slvx file) is the unit of transport. A SLVX file is simply a deflate-compressed archive (identical to the compression used on a XAP file), which contains one or more DLLs to load when the application is run. <br /> <br />Silverlight extensions is only for platform assemblies, not user code. This is enforced by the extension's location; it can only be hosted on a Microsoft.com domain. However, it can be redirected to any domain from there (see below).<br /> <br />AgDLR uses Silverlight extensions to deliver DLR+Language assemblies from Codeplex.com when a IronRuby or IronPython application is visited, rather than needing the assemblies in the XAP, or even deployed on your webserver.<br /> </div>jimmyschWed, 25 Mar 2009 21:58:30 GMTUpdated Wiki: Extensions 20090325095830Phttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Extensions&version=2<div class="wikidoc"> <i>This is a Silverlight 3 feature only. For similar behavior in Silverlight 2, see Chiron.exe.confg</i><br /> <br />Silverlight 3 supports <b>caching of transparent platform extensions</b>, which in English means extensions of Silverlight (Controls, DLR, etc) can be downloaded on-demand and cached by the browser the first time the Silverlight application is visited, rather than packaging everything inside the XAP. While Silverlight 2 supported loading assemblies from outside the XAP, some domains (Microsoft.com, for example) do not allow the transmission of DLLs, so a Silverlight &quot;extension&quot; (.slvx file) is the unit of transport. A SLVX file is simply a deflate-compressed archive (identical to the compression used on a XAP file), which contains one or more DLLs to load when the application is run. <br /> <br />Silverlight extensions is only for platform assemblies, not user code. This is enforced by the extension's location; it can only be hosted on a Microsoft.com domain. However, it can be redirected to any domain from there (see below).<br /> <br />AgDLR uses Silverlight extensions to deliver DLR+Language assemblies from Codeplex.com when a IronRuby or IronPython application is visited, rather than needing the assemblies in the XAP, or even deployed on your webserver.<br /> <br /><a href="javascript:window.location.href='http://sdlsdk.codeplex.com/Project/Download/FileDownload.aspx?DownloadId=63160';">IronRuby-0.5.0.slvx</a><br /><a href="javascript:window.location.href='http://sdlsdk.codeplex.com/Project/Download/FileDownload.aspx?DownloadId=63159';">IronPython-0.5.0.slvx</a><br /><a href="javascript:window.location.href='http://sdlsdk.codeplex.com/Project/Download/FileDownload.aspx?DownloadId=63161';">Microsoft.Scripting-0.5.0.slvx</a><br /> </div>jimmyschWed, 25 Mar 2009 21:52:32 GMTUpdated Wiki: Extensions 20090325095232Phttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Extensions&version=1<div class="wikidoc"> <i>This is a Silverlight 3 feature only. For similar behavior in Silverlight 2, see Chiron.exe.confg</i><br /> <br />Silverlight 3 supports <b>caching of transparent platform extensions</b>, which in English means extensions of Silverlight (Controls, DLR, etc) can be downloaded on-demand and cached by the browser the first time the Silverlight application is visited, rather than packaging everything inside the XAP. While Silverlight 2 supported loading assemblies from outside the XAP, some domains (Microsoft.com, for example) do not allow the transmission of DLLs, so a Silverlight &quot;extension&quot; (.slvx file) is the unit of transport. A SLVX file is simply a deflate-compressed archive (identical to the compression used on a XAP file), which contains one or more DLLs to load when the application is run. <br /> <br />Silverlight extensions is only for platform assemblies, not user code. This is enforced by the extension's location; it can only be hosted on a Microsoft.com domain. However, it can be redirected to any domain from there (see below).<br /> <br />AgDLR uses Silverlight extensions to deliver DLR+Language assemblies from Codeplex.com when a IronRuby or IronPython application is visited, rather than needing the assemblies in the XAP, or even deployed on your webserver.<br /> </div>jimmyschWed, 25 Mar 2009 21:37:57 GMTUpdated Wiki: Extensions 20090325093757Phttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Home&version=23<div class="wikidoc"> <h1> IronPython and IronRuby in Silverlight </h1>This is the project site for the <b><a href="http://silverlight.net/learn/dynamiclanguages.aspx" class="externalLink">Silverlight Dynamic Languages SDK<span class="externalLinkIcon"></span></a></b>, which lets you write browser applications with dynamic languages, like <a href="http://ruby-lang.org" class="externalLink">Ruby<span class="externalLinkIcon"></span></a> and <a href="http://python.org" class="externalLink">Python<span class="externalLinkIcon"></span></a>. The project is released under the <a href="http://www.opensource.org/licenses/ms-pl.html" class="externalLink">Microsoft Public License<span class="externalLinkIcon"></span></a>.<br /> <br />The <a href="http://silverlight.net/learn/dynamiclanguages.aspx" class="externalLink">Dynamic Languages SDK<span class="externalLinkIcon"></span></a> contains support for writing Ruby and Python applications in the browser. However, since this project provides a bridge between Silverlight™ and the <a href="http://dlr.codeplex.com" class="externalLink">Dynamic Language Runtime (DLR)<span class="externalLinkIcon"></span></a>, any language running on the DLR will be enabled to build Silverlight™ applications.<br /> <br />This project also enables hosting Ruby or Python inside VB and C# Silverlight™ applications, to add scripting support for you or your application's users. Lastly, it includes instructions on how write tests for a VB and C# applications with Ruby or Python.<br /><h2> Documentation </h2><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Getting%20Started&amp;referringTitle=Home">Getting Started</a><br /><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hello%2c%20World&amp;referringTitle=Home">Hello, World</a><br /><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hosting&amp;referringTitle=Home">Hosting</a><br /><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Extensions&amp;referringTitle=Home">Extensions</a><br /><h2> Daily Builds </h2><a href="http://nightlybuilds.cloudapp.net/Project.aspx?project=dlr" class="externalLink">DLR Daily Builds<span class="externalLinkIcon"></span></a> includes builds for the DLR in Silverlight™; simply replace the files in the /bin directory of sdlsdk with a daily builds. This is possible because the <a href="http://dlr.codeplex.com" class="externalLink">DLR CodePlex project<span class="externalLinkIcon"></span></a> includes a copy of this SDK in it's binary releases, and in it's source code repository.<br /><h2> Contributing </h2>The source code for this project is available on the <a href="http://github.com/jschementi/agdlr" class="externalLink"> AgDLR GitHub site<span class="externalLinkIcon"></span></a>. You can track daily progress there, as well as use bleeding edge features.<br /> <br />This project is open to the community for submitting samples for Silverlight™ that are written in dynamic languages implemented on the DLR. Please post your submissions in the Discussions tab.<br /><h2> Language Websites </h2><a href="http://ironpython.codeplex.com" class="externalLink">IronPython<span class="externalLinkIcon"></span></a><br /><a href="http://www.ironruby.net" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a><br /> </div>jimmyschWed, 25 Mar 2009 21:05:46 GMTUpdated Wiki: Home 20090325090546Phttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hello, World&version=4<div class="wikidoc"> <a href="javascript:window.location.href='http://sdlsdk.codeplex.com/Project/Download/FileDownload.aspx?DownloadId=63153';">agdlr-400.png</a><br /> </div>jimmyschWed, 25 Mar 2009 21:02:15 GMTUpdated Wiki: Hello, World 20090325090215Phttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hello, World&version=3<div class="wikidoc"> Testing attachments<br /> </div>jimmyschWed, 25 Mar 2009 21:01:53 GMTUpdated Wiki: Hello, World 20090325090153Phttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Home&version=22<div class="wikidoc"> <h1> IronPython and IronRuby in Silverlight </h1>This is the project site for the <b><a href="http://silverlight.net/learn/dynamiclanguages.aspx" class="externalLink">Silverlight Dynamic Languages SDK<span class="externalLinkIcon"></span></a></b>, which lets you write browser applications with dynamic languages, like <a href="http://ruby-lang.org" class="externalLink">Ruby<span class="externalLinkIcon"></span></a> and <a href="http://python.org" class="externalLink">Python<span class="externalLinkIcon"></span></a>. The project is released under the <a href="http://www.opensource.org/licenses/ms-pl.html" class="externalLink">Microsoft Public License<span class="externalLinkIcon"></span></a>.<br /> <br />The <a href="http://silverlight.net/learn/dynamiclanguages.aspx" class="externalLink">Dynamic Languages SDK<span class="externalLinkIcon"></span></a> contains support for writing Ruby and Python applications in the browser. However, since this project provides a bridge between Silverlight™ and the <a href="http://dlr.codeplex.com" class="externalLink">Dynamic Language Runtime (DLR)<span class="externalLinkIcon"></span></a>, any language running on the DLR will be enabled to build Silverlight™ applications.<br /> <br />This project also enables hosting Ruby or Python inside VB and C# Silverlight™ applications, to add scripting support for you or your application's users. Lastly, it includes instructions on how write tests for a VB and C# applications with Ruby or Python.<br /><h2> Documentation </h2><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Getting%20Started&amp;referringTitle=Home">Getting Started</a><br /><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hello%2c%20World&amp;referringTitle=Home">Hello, World</a><br /><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hosting&amp;referringTitle=Home">Hosting</a><br /><h2> Daily Builds </h2><a href="http://nightlybuilds.cloudapp.net/Project.aspx?project=dlr" class="externalLink">DLR Daily Builds<span class="externalLinkIcon"></span></a> includes builds for the DLR in Silverlight™; simply replace the files in the /bin directory of sdlsdk with a daily builds. This is possible because the <a href="http://dlr.codeplex.com" class="externalLink">DLR CodePlex project<span class="externalLinkIcon"></span></a> includes a copy of this SDK in it's binary releases, and in it's source code repository.<br /><h2> Contributing </h2>The source code for this project is available on the <a href="http://github.com/jschementi/agdlr" class="externalLink"> AgDLR GitHub site<span class="externalLinkIcon"></span></a>. You can track daily progress there, as well as use bleeding edge features.<br /> <br />This project is open to the community for submitting samples for Silverlight™ that are written in dynamic languages implemented on the DLR. Please post your submissions in the Discussions tab.<br /><h2> Language Websites </h2><a href="http://ironpython.codeplex.com" class="externalLink">IronPython<span class="externalLinkIcon"></span></a><br /><a href="http://www.ironruby.net" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a><br /> </div>jimmyschTue, 24 Mar 2009 05:13:28 GMTUpdated Wiki: Home 20090324051328Ahttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Home&version=21<div class="wikidoc"> <h1> IronPython and IronRuby in Silverlight </h1>This is the project site for the <b><a href="http://silverlight.net/learn/dynamiclanguages.aspx" class="externalLink">Silverlight Dynamic Languages SDK<span class="externalLinkIcon"></span></a></b>, which lets you write browser applications with dynamic languages, like <a href="http://ruby-lang.org" class="externalLink">Ruby<span class="externalLinkIcon"></span></a> and <a href="http://python.org" class="externalLink">Python<span class="externalLinkIcon"></span></a>. The project is released under the <a href="http://www.opensource.org/licenses/ms-pl.html" class="externalLink">Microsoft Public License<span class="externalLinkIcon"></span></a>.<br /> <br />The <a href="http://silverlight.net/learn/dynamiclanguages.aspx" class="externalLink">Dynamic Languages SDK<span class="externalLinkIcon"></span></a> contains support for writing Ruby and Python applications in the browser. However, since this project provides a bridge between Silverlight™ and the <a href="http://dlr.codeplex.com" class="externalLink">Dynamic Language Runtime (DLR)<span class="externalLinkIcon"></span></a>, any language running on the DLR will be enabled to build Silverlight™ applications.<br /> <br />This project also enables hosting Ruby or Python inside VB and C# Silverlight™ applications, to add scripting support for you or your application's users. Lastly, it includes instructions on how write tests for a VB and C# applications with Ruby or Python.<br /><h2> Documentation </h2><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Getting%20Started&amp;referringTitle=Home">Getting Started</a><br /><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hello%2c%20World&amp;referringTitle=Home">Hello, World</a><br /><a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hosting&amp;referringTitle=Home">Hosting</a><br /><h2> Daily Builds </h2><a href="http://nightlybuilds.cloudapp.net/Project.aspx?project=dlr" class="externalLink">DLR Daily Builds<span class="externalLinkIcon"></span></a> includes builds for the DLR in Silverlight™; simply replace the files in the /bin directory of sdlsdk with a daily builds. This is possible because the <a href="http://dlr.codeplex.com" class="externalLink">DLR CodePlex project<span class="externalLinkIcon"></span></a> includes a copy of this SDK in it's binary releases, and in it's source code repository.<br /><h2> Contributing </h2>The source code for this project is available on the <a href="http://github.com/jschementi/agdlr" class="externalLink"> AgDLR GitHub site<span class="externalLinkIcon"></span></a>. You can track daily progress there, as well as use bleeding edge features.<br /> <br />This project is open to the community for submitting samples for Silverlight™ that are written in dynamic languages implemented on the DLR. Please post your submissions in the Discussions tab.<br /><h2> Language Websites </h2><a href="http://ironpython.codeplex.com" class="externalLink">IronPython<span class="externalLinkIcon"></span></a><br /><a href="http://www.ironruby.net" class="externalLink">IronRuby<span class="externalLinkIcon"></span></a><br /> </div>jimmyschTue, 24 Mar 2009 05:10:28 GMTUpdated Wiki: Home 20090324051028Ahttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hosting&version=9<div class="wikidoc"> <h1> Hosting the DLR in Silverlight </h1>Hosting a dynamic language in Silverlight gives any Silverlight application (in any Silverlight language: C#/VB/Ruby/Python/JScript/others) the ability to run code in either Python, Ruby, JScript, or any other DLR-based language, from inside itself. For more information on the DLR and hosting, see <a href="http://dlr.codeplex.com/Wiki/View.aspx?titleDocs%20and%20specs&amp;referringTitleHome" class="externalLink">http://dlr.codeplex.com/Wiki/View.aspx?titleDocs%20and%20specs&amp;referringTitleHome<span class="externalLinkIcon"></span></a><br /> <br /><h2> Differences between desktop and Silverlight </h2>The code necessary to host the DLR inside of Silverlight is different than on the desktop. Also, the code different between static and dynamic languages. In both cases, they only differ in how you construct the ScriptRuntimeSetup object.<br /><h3> Discovering languages </h3>The first difference is how ScriptRuntimeSetup finds out the available languages. This information can either be loaded from a configuration file inside the XAP (language.config), or from the already-loaded assemblies themselves. The desktop does not allow loading from the assemblies, since it doesn't want to encourage loading all the language assemblies when they are not needed. However, Silverlight pre-loads all assemblies anyway, so both options are given in Silverlight.<br /> <br />Microsoft.Scripting.Silverlight.Configuration has helper methods to load the configuration from either a language.config from the XAP file, or, to avoid having the config file, the language assemblies themselves. <br /><h3> Platform Adaptation Layer </h3>The desktop and Silverlight differ in a big way when it comes to the File system; Silverlight does not have access to the machine's file system. Instead, it can only access files inside the XAP file, or in Isolated Storage. The DLR abstracts platform functionality into a PlatformAdaptationLayer (PAL), which can be changed by supplying a custom ScriptHost, which knows about a custom PAL. <br /> <br />The DLR's default PAL doesn't define any behavior for Silverlight; it just throws &quot;NotImplementedException&quot; if any platform functionality is used. Microsoft.Scripting.Silverlight.BrowserScriptHost is a custom ScriptHost which knows about an internal BrowserPAL class, which directs any read-only file system access to the XAP.<br /> <br /><h2> Hosting the DLR from C# or VB </h2>The following tells the ScriptRuntimeSetup about the avaliable languages from the loaded assemblies, and sets the HostType to BrowserScriptHost, which will make read-only platform-specific features work. It also pre-references platform assemblies so AddReference/LoadAssembly doesn't need to be called from script code.<br /><h3> C# </h3><pre> using Microsoft.Scripting.Hosting; using Microsoft.Scripting.Silverlight; ScriptRuntimeSetup setup = Configuration.LoadFromAssemblies(Package.GetManifestAssemblies()); setup.HostType = typeof(BrowserScriptHost); ScriptRuntime runtime = new ScriptRuntime(setup); // load platform assemblies so you don't need to call LoadAssembly in script code. foreach (string name in new string[] { &quot;mscorlib&quot;, &quot;System&quot;, &quot;System.Windows&quot;, &quot;System.Windows.Browser&quot;, &quot;System.Net&quot; }) { runtime.Host.PlatformAdaptationLayer.LoadAssembly(name); } // now the desktop and Silverlight are the same ... ScriptEngine engine = runtime.GetEngine(&quot;Python&quot;) ScriptSource source = engine.CreateScriptSourceFromString(&quot;System.Windows.Browser.HtmlPage.Document.Message.innerHTML = 'Hello, World'&quot;) source.Compile().Execute(); </pre> <br /><h3> VB </h3><pre> coming soon </pre> <br /> <br /><h2> Hosting the DLR from Python, Ruby, or JScript </h2>Since the DLR/Silverlight integration is a C# application and hosts the DLR itself, the above work is already done for a dynamic language. Therefore, dynamic languages only need access to the ScriptRuntime or ScriptRuntimeSetup objects.<br /> <br /><h3> Ruby </h3><pre> require 'Microsoft.Scripting' include Microsoft.Scripting.Silverlight include Microsoft.Scripting.Hosting runtime = ScriptRuntime.new(DynamicApplication.current.runtime.setup) # or, is you just want to reuse the ScriptRuntime object: runtime = DynamicApplication.current.runtime </pre> <br /> <br /><h3> Python </h3><pre> import clr clr.AddReference(&quot;Microsoft.Scripting&quot;) from Microsoft.Scripting.Hosting import ScriptRuntime, ScriptRuntimeSetup from Microsoft.Scripting.Silverlight import DynamicApplication runtime = ScriptRuntime(DynamicApplication.Current.Runtime.Setup # or, is you just want to reuse the ScriptRuntime object: runtime = DynamicApplication.Current.Runtime </pre> <br /> </div>jimmyschTue, 10 Mar 2009 20:24:44 GMTUpdated Wiki: Hosting 20090310082444Phttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hosting&version=8<div class="wikidoc"> <h1> Hosting the DLR in Silverlight </h1>Hosting a dynamic language in Silverlight gives any Silverlight application (in any Silverlight language: C#/VB/Ruby/Python/JScript/others) the ability to run code in either Python, Ruby, JScript, or any other DLR-based language, from inside itself. For more information on the DLR and hosting, see <a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=DLR%20docs%3a%20http%3a%2f%2fdlr.codeplex.com%2fWiki%2fView.aspx%3ftitleDocs%2520and%2520specs%26referringTitleHome&amp;referringTitle=Hosting">DLR docs: http://dlr.codeplex.com/Wiki/View.aspx?titleDocs%20and%20specs&amp;referringTitleHome</a><br /> <br /><h2> Differences between desktop and Silverlight </h2>The code necessary to host the DLR inside of Silverlight is different than on the desktop. Also, the code different between static and dynamic languages. In both cases, they only differ in how you construct the ScriptRuntimeSetup object.<br /><h3> Discovering languages </h3>The first difference is how ScriptRuntimeSetup finds out the available languages. This information can either be loaded from a configuration file inside the XAP (language.config), or from the already-loaded assemblies themselves. The desktop does not allow loading from the assemblies, since it doesn't want to encourage loading all the language assemblies when they are not needed. However, Silverlight pre-loads all assemblies anyway, so both options are given in Silverlight.<br /> <br />Microsoft.Scripting.Silverlight.Configuration has helper methods to load the configuration from either a language.config from the XAP file, or, to avoid having the config file, the language assemblies themselves. <br /><h3> Platform Adaptation Layer </h3>The desktop and Silverlight differ in a big way when it comes to the File system; Silverlight does not have access to the machine's file system. Instead, it can only access files inside the XAP file, or in Isolated Storage. The DLR abstracts platform functionality into a PlatformAdaptationLayer (PAL), which can be changed by supplying a custom ScriptHost, which knows about a custom PAL. <br /> <br />The DLR's default PAL doesn't define any behavior for Silverlight; it just throws &quot;NotImplementedException&quot; if any platform functionality is used. Microsoft.Scripting.Silverlight.BrowserScriptHost is a custom ScriptHost which knows about an internal BrowserPAL class, which directs any read-only file system access to the XAP.<br /> <br /><h2> Hosting the DLR from C# or VB </h2>The following tells the ScriptRuntimeSetup about the avaliable languages from the loaded assemblies, and sets the HostType to BrowserScriptHost, which will make read-only platform-specific features work. It also pre-references platform assemblies so AddReference/LoadAssembly doesn't need to be called from script code.<br /><h3> C# </h3><pre> using Microsoft.Scripting.Hosting; using Microsoft.Scripting.Silverlight; ScriptRuntimeSetup setup = Configuration.LoadFromAssemblies(Package.GetManifestAssemblies()); setup.HostType = typeof(BrowserScriptHost); ScriptRuntime runtime = new ScriptRuntime(setup); // load platform assemblies so you don't need to call LoadAssembly in script code. foreach (string name in new string[] { &quot;mscorlib&quot;, &quot;System&quot;, &quot;System.Windows&quot;, &quot;System.Windows.Browser&quot;, &quot;System.Net&quot; }) { runtime.Host.PlatformAdaptationLayer.LoadAssembly(name); } // now the desktop and Silverlight are the same ... ScriptEngine engine = runtime.GetEngine(&quot;Python&quot;) ScriptSource source = engine.CreateScriptSourceFromString(&quot;System.Windows.Browser.HtmlPage.Document.Message.innerHTML = 'Hello, World'&quot;) source.Compile().Execute(); </pre> <br /><h3> VB </h3><pre> coming soon </pre> <br /> <br /><h2> Hosting the DLR from Python, Ruby, or JScript </h2>Since the DLR/Silverlight integration is a C# application and hosts the DLR itself, the above work is already done for a dynamic language. Therefore, dynamic languages only need access to the ScriptRuntime or ScriptRuntimeSetup objects.<br /> <br /><h3> Ruby </h3><pre> require 'Microsoft.Scripting' include Microsoft.Scripting.Silverlight include Microsoft.Scripting.Hosting runtime = ScriptRuntime.new(DynamicApplication.current.runtime.setup) # or, is you just want to reuse the ScriptRuntime object: runtime = DynamicApplication.current.runtime </pre> <br /> <br /><h3> Python </h3><pre> import clr clr.AddReference(&quot;Microsoft.Scripting&quot;) from Microsoft.Scripting.Hosting import ScriptRuntime, ScriptRuntimeSetup from Microsoft.Scripting.Silverlight import DynamicApplication runtime = ScriptRuntime(DynamicApplication.Current.Runtime.Setup # or, is you just want to reuse the ScriptRuntime object: runtime = DynamicApplication.Current.Runtime </pre> <br /> </div>jimmyschTue, 10 Mar 2009 20:23:43 GMTUpdated Wiki: Hosting 20090310082343Phttp://sdlsdk.codeplex.com/Wiki/View.aspx?title=Hosting&version=7<div class="wikidoc"> <h1> Hosting the DLR in Silverlight </h1>Hosting a dynamic language in Silverlight gives any Silverlight application (in any Silverlight language: C#/VB/Ruby/Python/JScript/others) the ability to run code in either Python, Ruby, JScript, or any other DLR-based language, from inside itself. For more information on the DLR and hosting, see <a href="http://sdlsdk.codeplex.com/Wiki/View.aspx?title=DLR%20docs%3ahttp%3a%2f%2fdlr.codeplex.com%2fWiki%2fView.aspx%3ftitleDocs%2520and%2520specs%26referringTitleHome&amp;referringTitle=Hosting">DLR docs:http://dlr.codeplex.com/Wiki/View.aspx?titleDocs%20and%20specs&amp;referringTitleHome</a><br /> <br /><h2> Differences between desktop and Silverlight </h2>The code necessary to host the DLR inside of Silverlight is different than on the desktop. Also, the code different between static and dynamic languages. In both cases, they only differ in how you construct the ScriptRuntimeSetup object.<br /><h3> Discovering languages </h3>The first difference is how ScriptRuntimeSetup finds out the available languages. This information can either be loaded from a configuration file inside the XAP (language.config), or from the already-loaded assemblies themselves. The desktop does not allow loading from the assemblies, since it doesn't want to encourage loading all the language assemblies when they are not needed. However, Silverlight pre-loads all assemblies anyway, so both options are given in Silverlight.<br /> <br />Microsoft.Scripting.Silverlight.Configuration has helper methods to load the configuration from either a language.config from the XAP file, or, to avoid having the config file, the language assemblies themselves. <br /><h3> Platform Adaptation Layer </h3>The desktop and Silverlight differ in a big way when it comes to the File system; Silverlight does not have access to the machine's file system. Instead, it can only access files inside the XAP file, or in Isolated Storage. The DLR abstracts platform functionality into a PlatformAdaptationLayer (PAL), which can be changed by supplying a custom ScriptHost, which knows about a custom PAL. <br /> <br />The DLR's default PAL doesn't define any behavior for Silverlight; it just throws &quot;NotImplementedException&quot; if any platform functionality is used. Microsoft.Scripting.Silverlight.BrowserScriptHost is a custom ScriptHost which knows about an internal BrowserPAL class, which directs any read-only file system access to the XAP.<br /> <br /><h2> Hosting the DLR from C# or VB </h2>The following tells the ScriptRuntimeSetup about the avaliable languages from the loaded assemblies, and sets the HostType to BrowserScriptHost, which will make read-only platform-specific features work. It also pre-references platform assemblies so AddReference/LoadAssembly doesn't need to be called from script code.<br /><h3> C# </h3><pre> using Microsoft.Scripting.Hosting; using Microsoft.Scripting.Silverlight; ScriptRuntimeSetup setup = Configuration.LoadFromAssemblies(Package.GetManifestAssemblies()); setup.HostType = typeof(BrowserScriptHost); ScriptRuntime runtime = new ScriptRuntime(setup); // load platform assemblies so you don't need to call LoadAssembly in script code. foreach (string name in new string[] { &quot;mscorlib&quot;, &quot;System&quot;, &quot;System.Windows&quot;, &quot;System.Windows.Browser&quot;, &quot;System.Net&quot; }) { runtime.Host.PlatformAdaptationLayer.LoadAssembly(name); } // now the desktop and Silverlight are the same ... ScriptEngine engine = runtime.GetEngine(&quot;Python&quot;) ScriptSource source = engine.CreateScriptSourceFromString(&quot;System.Windows.Browser.HtmlPage.Document.Message.innerHTML = 'Hello, World'&quot;) source.Compile().Execute(); </pre> <br /><h3> VB </h3><pre> coming soon </pre> <br /> <br /><h2> Hosting the DLR from Python, Ruby, or JScript </h2>Since the DLR/Silverlight integration is a C# application and hosts the DLR itself, the above work is already done for a dynamic language. Therefore, dynamic languages only need access to the ScriptRuntime or ScriptRuntimeSetup objects.<br /> <br /><h3> Ruby </h3><pre> require 'Microsoft.Scripting' include Microsoft.Scripting.Silverlight include Microsoft.Scripting.Hosting runtime = ScriptRuntime.new(DynamicApplication.current.runtime.setup) # or, is you just want to reuse the ScriptRuntime object: runtime = DynamicApplication.current.runtime </pre> <br /> <br /><h3> Python </h3><pre> import clr clr.AddReference(&quot;Microsoft.Scripting&quot;) from Microsoft.Scripting.Hosting import ScriptRuntime, ScriptRuntimeSetup from Microsoft.Scripting.Silverlight import DynamicApplication runtime = ScriptRuntime(DynamicApplication.Current.Runtime.Setup # or, is you just want to reuse the ScriptRuntime object: runtime = DynamicApplication.Current.Runtime </pre> <br /> </div>jimmyschTue, 10 Mar 2009 20:20:46 GMTUpdated Wiki: Hosting 20090310082046P