Once I had tried to setup the associations in vs.net just right so double clicking on a build file would run nant, but quickly realized I was barking up the wrong tree. Looks like someone was barking up the right tree and created a NantRunner plugin, which TestingReflections.com points out recently got an update. After installing, the plugin quickly analyzed the build file I had as a sln item, and displayed all of the public (targets with desc) and private (targets without desc) in the IDE. After telling the plugin where nant was, the plugin ran my target first try. After some quick testing, I think this plugin just became a perm tool in my toolbox.

The only complaint I would have is the mapping to nant. I currently maintain nant with my projects, so each project has its own copy of nant. The plugin uses a central install. Not a big deal while they are all on 0.85rc2, but we'll see what happens when the next version comes out. If nothing else, it will force me to check compatibility sooner. Either way, if you use nant at all, I would highly suggest this plugin. Nice and easy, and you never have to leave the IDE to run any of your targets.

[Edit] URL Updated