Along a lot of these ideas, I have written a small app which I use to
file bugs on Codeplex. The source is at
GitHub - jredville/cp_bugger: A repl for working with Codeplex bugs.. I bring it up now because it
fills some of these points:
a custom toom
more friendly and adjust the complexities of TFS to the relative
simplicity of Codeplex.
plan on adding a repl mode to this, and I might make IRB the base of
that repl.
relatively easy
This app would have been possible via screen scraping or Ruby.NET, but
it was amazingly simple to build using IronRuby. It’s also really
useful, and has very little todo with testing.
JD
From: [email protected]
[mailto:[email protected]] On Behalf Of Shay F.
Sent: Tuesday, January 26, 2010 8:35 AM
To: [email protected]
Subject: Re: [Ironruby-core] Why IronRuby?
This question keeps coming back
Testing is a great use of IronRuby, maybe even the top reason for .NET
guys to use it. However, there are more reasons for .NET guys to adopt
IronRuby like:
- Writing internal tools.
- Make it possible to extend .NET applications using IronRuby.
- Using IronRuby’s REPL capabilities for quick POCs or to enhance
current .NET applications.
- Silverlight and Gestalt development
- Writing DSLs
- Running Ruby on Rails on IIS “natively” (this one is not so much for
the .NET developer, but it’s a great reason too ).
All in all, it will be tremendously hard to convince C#/VB.Net guys to
work with IronRuby. Moreover, it’ll be twice as hard until VS fully
supports the language.
Having said that, I do believe that as time goes by the walls will
collapse and IronRuby will become a common tool among .NET devs.
Shay.
Shay F. | .NET Technologies Expert | Author of IronRuby Unleashed
| Sela Technology Center
Blog: http://IronShay.com | Twitter: http://twitter.com/ironshay
On Tue, Jan 26, 2010 at 6:13 PM, Mohammad A.
<[email protected]mailto:[email protected]> wrote:
Hi,
I was thinking about why to use IronRuby and one of the things that came
to my mind is because of better gems like spec, cucumber etc. Mostly my
use of IronRuby is around unit testing .NET CLR frameworks. But then
.NET CLR implementations is catching up with all these tools like
specflow and (.NET implementation for cucumber not sure about the name).
RAKE is awesome but usually I just use sh to execute shell scripts and
perform the build. Currently, I am not interacting RAKE with .NET
assemblies so it is pure Ruby implementation.
So, what do you think? Where would you use IronRuby?
Posted via http://www.ruby-forum.com/.