In this case, Zac is not trying to run the tests using .NET 4 (which can be
done using "irtests.bat --clr4"). And so the .NET 3.5 C# compiler should be
used. However, dev.bat calls vsvars32.bat which seems to add all versions of
.NET to the path, with .NET 4 (C:\Windows\Microsoft.NET\Framework\v
So I pulled the latest changes from v1.0 HEAD and still get the compile
errors in Tests\Interop. Going to run irtests again tonight and see what
I get.
-Zac
On 4/5/2010 11:19 AM, Jim Deville wrote:
Yes and no. It is expected that some of the tests will have issues on CLR4, but
I thought Toma
Filed a bug: http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=4327.
Tomas
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Shay Friedman
Sent: Tuesday, April 06, 2010 8:10 AM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core]
OK, I installed MRI and it worked. So it's a problem with IronRuby...
Shay Friedman | Microsoft Visual C#/IronRuby MVP | Author of IronRuby
Unleashed | Sela Technology Center
Blog: http://IronShay.com | Twitter: http://twitter.com/ironshay
No, I don't have MRI installed on this computer (I'm loyal to my IronRuby!
:-) )... If someone can try it, please do.
Thanks,
Shay.
Shay Friedman | Microsoft Visual C#/IronRuby MVP | Author of IronRuby
Unleashed | Sela Technology Center
Blog
I'll have to try that later.
Have you run the shoulda tests on MRI? Does it report a different number of
Tests and Assertions?
--
Will Green
http://hotgazpacho.org/
On Tue, Apr 6, 2010 at 2:54 AM, Shay Friedman wrote:
> This doesn't work for me:
>
> require 'rubygems'
> require 'shoulda'
>
> cl
Good idea; we're a little late on getting this going, but if people want to
help with ideas, feel free to update the Contribution Ideas page:
http://wiki.github.com/ironruby/ironruby/contribution-ideas. It's sparse at the
moment, so any ideas would be awesome. I can probably work on it a bit sho
