The cynical side of my wants to say “intellisense is a crutch”, and I do think that this is true, to an extend. But then, the honest side of me says “damn right I miss intellisense!”

The good news is editors like e text editor, jetbrains rubymine, maybe textmate?, and probably others do offer some intellisense capabilities.

Plus, you can always check the documentation on the wiki.

You can clone it to your local box, or just install the gem and see if it works on IronRuby. If you find issues and want to fix them, or if you see the need to add options that I haven’t included on the object models (i’m only including what I need, when I need it… ), then a fork would be the best way to go about doing that.

Well played with the Markdown file, I think any GitHub project looks lost without one :)

I’m using IronRuby for my own Rake stuff, and enjoying being able to write rake tasks that work with domain stuff such as NHibernate entities directly.

Mono is a direction I’m really interested in, I don’t know why, but everything is so damned fast when I’m building/testing on Mono + OSX. I’ve really used Mono in anger yet, but hope to. I also pray that JetBrains will pull their finger out and make a cross platform IDE for .NET. This might never happen due to their comfort zone with R# :(

Will grab your stuff next time I’m near an IronRuby Rake file. How do we do this, shall I fork?

Like everything else that i tend to put off, the readme markdown was easier than i thought! especially using the e text editor and it’s markdown preview. :)

readme has been added to the github page, to include installation instructions!

thanks for volunteering to do that markdown! :)

seriously, though… i’ve been meaning to create one, but haven’t got around to it. you can get all the install instructions on the Albacore wiki, though:

http://wiki.github.com/derickbailey/Albacore

mono / ironruby: are you using these platforms? If so, i’d love to work with you on getting these support in albacore.

Here’s a few ideas (don’t worry, just food for thought, I know some of this might be off piste right now).

1) Add a readme.markdown file explaining the project installation, usage, purpose and vision.

2) Make it mono compatible.

3) Test it on IronRuby

Look forward to watching this project :)

awesome

and i’m going to hold you go that fresh baked cookie… one of these days we’ll end up meeting IRL, and you better have a cookie with you. :)

NAnt is horrible. HORRIBLE. I mean it’s genuinely bad. I can’t begin to fathom why people continue to use it. Thinking about it makes my face twitch.

I’m recommending Albacore to every single person asking me anything about an automated build.

Another reason for using Albacore over Nant: copying files. Every build has to copy files, but an XML syntax for copying a file is just moronic.

Down with angle brackets!