IronRuby - path's format is not supported.

[mickdelaney]

hi,

i'n trying to use RIS to execute scripts against the ironruby interpreter (ir.exe). i've changed my interpreter to point at ir but i get this error:
unknown: The given path's format is not supported. (System::NotSupportedException)
has anyone else seen/fixed this issue?

regards,
mick

[Huw Collingbourne]

Are you in fact creating IronRuby projects? That is, are you selecting IronRuby as the project type in the Developer edition or, if not, are you using our free IronRuby personal edition? IronRuby is not sufficiently similar to the standard Ruby interpreter merely to substitute it into a standard Ruby project so you will need to use one of the options mentioned above.

best wishes

Huw

[mickdelaney]

no, i'd installed the non ironruby version.
i'm installing now....

i'm not sure if this would work but have u seen this post: http://flanders.co.nz/2009/05/02/using-ironruby-with-rubymine/

[mickdelaney]

i've set my interpreter to C:\ironruby\Merlin\Main\Bin\debug\ir.exe but it keeps asking for C:\ironruby\Merlin\Main\Bin\debug\rbx.exe....

is it hardcoded?

[Huw Collingbourne]

It's been a long time since we did any work on IronRuby support so it's quite possible that this may be an issue. Just to give you a bit of background... We always said that we wouldn't be updating our IronRuby support until after the release of IronRuby 1.0. Initially the IronRuby team were expecting to ship the finished product fairly rapidly. John Lam, for example, predicted in June 2007 that it be fully Rails-compatible (and, we sort of assumed, at version 1.0) in "under 18 months": http://www.iunknown.com/2007/06/ironruby_and_ru.html

We produced our IronRuby IDE in early 2008 in the expectaion that the final release of IronRuby would appear later that year. As the challenge to get to IronRuby 1.0 has clearly proven to be greater than was originally expected, we are still waiting for the final solid implementation to appear (I see IronRuby is currently at 0.5). Which explains why we haven't yet updated our IronRuby IDE.

In the meantime, I'll take a look to see if there is any simple fix from Ruby In Steel. As an interim measure might it not be possible to rename the IronRuby executable?

best wishes

Huw

[Barry Carr]

I've have just this minute ran into the same problem. I tried the simplest thing I thought would work, that is, rename ir.exe and ir.exe.config to rbx.exe and rbx.exe.config. It seems to work.

Cheers
Barry

[Huw Collingbourne]

Always nice to find a simple solution. 

We'll look again at IronRuby after MS releases a solid version 1.x.

best wishes
Huw