If you want to deploy easily, then you can include the needed files in the same directory as the DLL. Every programming system I have ever used requires setup, it's not hard to script setting up ENV variables and copying files. We do this kind of thing on 20+ machines for testing for IronRuby and IronPython. Using the installer does install to a common location, %ProgramFiles%.
JD -----Original Message----- From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Mohammad Azam Sent: Monday, January 25, 2010 10:51 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] Did Something Changed Again in Spec... The problem is that every person has their own IronRuby folder. It has to work same for everyone. Kind of like libraries in GAC. You are NOT thinking throughly about the problem! This is not regarding putting the path in ENV variables and copying couple of files. This is about doing the same thing for 10 servers. I don't think you will be comfortable doing the same for 10 servers. This also adds extra work for writing build scripts that will do this work. Maybe the IronRuby installation should add the IronRuby folder to a common path which is same for all the machines. Kind of like when installing the .NET framework which is usually on a common place. -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
