I have an application that allows the user to choose between Ruby and Python scripting. In order to make this work, I had to rebuild IronRuby with all the Microsoft.Scripting.* assemblies renamed, because the versions are different for the current versions of IronPython and IronRuby. What are the plans for making these projects reference the same Microsoft.Scripting.* dlls, so that I don''t have to do this? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20090313/4ea2663f/attachment.html>
You can build python out of github today. It lives is merlin\main \languages\ironpython. Then you can share the same DLR assemblies. ~Jimmy Sent from my phone On Mar 13, 2009, at 6:27 PM, "Bruce Pierson" <bpierson at connexatools.com> wrote:> I have an application that allows the user to choose between Ruby > and Python scripting. In order to make this work, I had to rebuild > IronRuby with all the Microsoft.Scripting.* assemblies renamed, > because the versions are different for the current versions of > IronPython and IronRuby. > > > > What are the plans for making these projects reference the same > Microsoft.Scripting.* dlls, so that I don?t have to do this? > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core
You can get the latest builds from http://nightlybuilds.cloudapp.net/Project.aspx?project=dlr or build both languages from GIT or CodePlex source code (see my blog http://blog.tomasm.net/2009/02/20/multilingual-repl). Tomas From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Bruce Pierson Sent: Friday, March 13, 2009 3:11 PM To: ironruby-core at rubyforge.org Subject: [Ironruby-core] Microsoft.Scripting dll versions I have an application that allows the user to choose between Ruby and Python scripting. In order to make this work, I had to rebuild IronRuby with all the Microsoft.Scripting.* assemblies renamed, because the versions are different for the current versions of IronPython and IronRuby. What are the plans for making these projects reference the same Microsoft.Scripting.* dlls, so that I don''t have to do this? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20090313/829d84c0/attachment.html>
Thanks, that did the trick. From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Tomas Matousek Sent: Friday, March 13, 2009 4:42 PM To: ironruby-core at rubyforge.org Subject: Re: [Ironruby-core] Microsoft.Scripting dll versions You can get the latest builds from http://nightlybuilds.cloudapp.net/Project.aspx?project=dlr or build both languages from GIT or CodePlex source code (see my blog http://blog.tomasm.net/2009/02/20/multilingual-repl). Tomas From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Bruce Pierson Sent: Friday, March 13, 2009 3:11 PM To: ironruby-core at rubyforge.org Subject: [Ironruby-core] Microsoft.Scripting dll versions I have an application that allows the user to choose between Ruby and Python scripting. In order to make this work, I had to rebuild IronRuby with all the Microsoft.Scripting.* assemblies renamed, because the versions are different for the current versions of IronPython and IronRuby. What are the plans for making these projects reference the same Microsoft.Scripting.* dlls, so that I don''t have to do this? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20090313/f0d6efbc/attachment-0001.html>