Hi Gishu,

Glad that you were able to get things to work. Couple of comments about your 
blog (couldn't see a way to post a comment there):

*         You do not need .NET 4.0 at all. The binaries are built for .NET 2.0, 
and building with VS will also build for .NET 4.0. Even if you install .NET 
4.0, it will not be used

*         If you are building from source, you should just run ir.exe from 
where it is build Merlin\bin\Debug. That way you do not need to mess with 
ir.exe.config.

Shri

From: Gishu Pillai [mailto:gi...@hotmail.com]
Sent: Wednesday, September 23, 2009 6:54 PM
To: Shri Borde
Subject: RE: IronRuby Cucumber failures

Hi Shri,

I managed to workaround this... steps detailed here - 
http://madcoderspeak.blogspot.com/2009/09/testing-net-code-with-cucumber-and.html

Other issues that I ran into were

  *   inability to build the IronRuby solution on Visual C# Express Edition.

  *   also how does IronRuby resolve the Ruby convention of methods like blank? 
- method names that end with a question_mark and return a boolean value. e.g. 
Cucumber translates "should be_over" to a call on a method called over? on the 
Ruby test subject. If I'm using a C# class as the test subject via IronRuby, 
what would be the corresponding method ... Links to wikis (in case this has 
already been discussed would also suffice)

Thanks for responding...
Gishu

________________________________
From: notificati...@codeplex.com
To: gi...@hotmail.com
Date: Tue, 8 Sep 2009 11:50:08 -0700
Subject: IronRuby Cucumber failures

User sborde has contacted you through CodePlex using the Contact User form. 
Replying to this email will reply directly to the user. If you do not wish to 
allow being contacted, you may indicate so on your profile page.

The following is the message from sborde:

Hi,

Thanks for the detailed info about your problems.

The GUID in the zip files must be created by github.com, and must be the SHA1 
hash of the latest commit. There is not much we can do there.

People do not usually build and copy the files to an older release. It might 
work, but its not really recommended. My guess is that the error you are 
getting (cannot find rubygems) could be because you copied ir.exe.config from 
bin\debug in addition to ir.exe. The ir.exe.config file in bin\debug points to 
paths that are in the GIT source repo, but not in the binary releases. You 
could try reverting back to the original ir.exe.config from the binary release 
so that it points to the right path in the binary release from where to pick up 
rubygems.

A better option is to run bin\debug\ir.exe itself. Did you try doing that?

If you want to build from source, the best way to do it is to get the sources 
using GIT as described at http://wiki.github.com/ironruby/ironruby. If you run 
dev.bat, your environment will be set to a good state so that you can run the 
binaries you build in bin\debug.

I dont think there is an older release of IronRuby that you could use to 
workaround the problem. If you want, I will be happy to work with you to enable 
you to be able to build IronRuby and run your scenario. 
http://wiki.github.com/ironruby/ironruby has a lot of info to get you started. 
This will also be useful if we need to fix any additional bugs you run into.

Regards,
Shri
________________________________
Get easy photo sharing with Windows LiveT Photos. Drag n' 
drop<http://www.microsoft.com/india/windows/windowslive/photos.aspx>
_______________________________________________
Ironruby-core mailing list
Ironruby-core@rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core

Reply via email to