IronRuby 1.1.3 is a servicing release that keeps on improving compatibility with Ruby 1.9.2 and includes IronRuby integration to Visual Studio 2010. We decided to drop 1.8.6 compatibility mode in all post-1.0 releases. We recommend using IronRuby 1.0 if you need 1.8.6 compatibility.
The main purpose of this release is to sync with IronPython 2.7 release, i.e. to keep the Dynamic Language Runtime that both these languages build on top shareable.
This release also fixes a few bugs:
5763 Use of Bewildr Gem Fails in V1.1.2 5786 Hash.each (without block) gives a syntax error. ir 1.1.2. breaks Builder 3.0.0 gem. 5787 alias :"#{var}" :name fails with SyntaxErrorException in v1.1.2. Breaks awesome_print gem.
|
I installed the IronRuby just fine and integrated with VS2010.
by
njsimha
on
Jan 27 at 3:34 AM
The most important Engine.ExecuteFile method throw NotImplemented Exception.
by
ruiyun
on
Dec 12 2011 at 4:41 AM
Just copy from program files x86/ironruby* to program files\ironruby* and it worked fine on all project types for me.
by
burker
on
Dec 9 2011 at 3:20 PM
Nice work, but I also got the installation problem. When I try to run windows form application, the error message like irw.exe not found appeared. I could fix this problem by opening the windows form project property, and set C:\Program Files (x86)\IronRuby 1.1\bin\ir.exe on "Interpreter Path". For this problem, I rated 4 not 5.
by
mura_no
on
Nov 7 2011 at 12:57 AM
Doesn't work. Tools and binaries install, but the project templates can't find the IR interpreter. I had to manually set the interpreter path in WinForms project to get it to work. However, this solution only works if you're able to create the project. For some projects, you can't even create a broken project and fix it after the fact.
by
jinushaun
on
Aug 30 2011 at 11:17 PM
1 Star only for installer problem ???????????????????????????
by
OmidID
on
Aug 29 2011 at 9:24 AM
I've been using this release for production and really works very well. There are some (minor) issues that can be overcome easily with workarounds, but 1.9.2 compatibility is quite good.
by
eblumenfeld
on
Jul 29 2011 at 9:16 PM
Unfortunatelly after installation IronRuby doesn't work on VS 2010 Prof.
I have two errors:
IronRuby installation not found. Although basic scripts should work standard libraries and gems won't be available.
and second
Interpreter "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Commom7\IDE\Extensions\Microsoft\IronRuby Tools for Visual Studio\0.1\ie.exe" does not exist.
by
lszk
on
Jul 28 2011 at 6:17 PM
1.1.3 is good-to-go! Nice!
by
Storminator16
on
Jun 15 2011 at 5:39 AM
I have not run into much I can't do. Occasionally you run into a gem or two that doesn't build right off the bat, but Google and a little bit of elbow grease will get thing up and running. I've got WPF apps, Rails, Sinatra and lots of basic shell scripts to handle administrative tasks on Windows servers. Rock on IronRuby folks.
by
wbellman
on
Jun 3 2011 at 4:32 AM
VS2010 Sp1 Ultimate, VS Web Developer 2010 Express... doesn't matter. Fresh OS install... doesn't matter. Tried uninstalling ruby first... doesn't matter. IronRuby is dead, apparently, and these releases are just illustrating the fact. Nearly 100% of all gems cannot be installed due to a NilClass to String error that has been well documented as of about a year ago. No progress? Really?
by
jbatte
on
May 28 2011 at 4:42 PM
Doesnt actually work on VS2010 SP1.
by
rzk
on
Apr 14 2011 at 1:29 AM
I have to give this one star because, well, it doesn't work. It tells me that .rbproj cannot be opened because it's for a different version of VS. I'm thinking this is because I have VS SP 1 installed and it doesn't like that.
by
burkeholland
on
Mar 29 2011 at 7:53 PM
Could you please repair statistic on the http://www.ironruby.info/ ?
by
Closer
on
Mar 13 2011 at 11:42 PM