If you need it for "in production" testing definitely use the MSI. That's the
way how users will install it.
Tomas
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Orion Edwards
Sent: Wednesday, May 25, 2011 1:04 PM
To: ironruby-core@rubyforge.
The experimental instance works well for development.
After making a change to the VS tools I'd like to use it "in anger" in the
production instance working on real code, and rebuilding/reinstalling the
release MSI is just an extra step requiring more time.
If it's difficult to resolve or likely
Orion,
I'll review this change shortly and let you know if I have any feedback.
~Jimmy
On May 24, 2011, at 11:51 PM, Orion Edwards wrote:
> As mentioned in the bug http://ironruby.codeplex.com/workitem/6118 ,
> IronRuby .rbproj files have some severe problems when working with
> source-con
Orion, what can't you accomplish with the experimental hive which you think you
can do by installing a non-MSI'd IronRuby tools?
The non-MSI installation is not supported as we use the GAC for resolving
dependencies of "IronStudio" components between Ruby and Python. A non-MSI
installation usin
