As we've talked about before, you only need dev.bat if you are developing IronRuby. If you are developing with IronRuby, you only need to use the installer. If you are embedding IronRuby, then there are app.config issues that need to be worked out, some of those can be handled by better tooling down the road, some of those can't be helped. Even those that can't be helped have alternate API's.
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 9:32 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] Did Something Changed Again in Spec... I don't like to execute dev.bat each time I need to work with IronRuby. Why can't it just work out of the box like PowerShell. This is a big defect in the IronRuby. Too many configurations will scare developers away. People are not interested in setting paths in ENV variables, performing configuration settings in App.config to make sure that IronRuby is pointing to correct lib paths. Not many people are willing to try out IronRuby because of configuration issues. -- 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
