Jul 7 2011

Neovolve.BuildTaskExecutor 1.0 Released

Category: .Net | My Software — Rory Primrose @ 10:43

Over the last week I have posted a series of entries about how to execute custom tasks as part of a build process without TFS. The result of this process is the Neovolve.BuildTaskExecutor 1.0 application which is now available on CodePlex.

The following posts document how BuildTaskExecutor has come about:

You can download Neovolve.BuildTaskExecutor from here.

Enjoy.

Tags:

Comments (2) -

1.
Steve Steve United States says:
Saturday, July 09, 2011 at 11:45 PM

Reading over the series of posts, I'm still left wondering the following question.  What does your Build Task Executor get you that can't already be solved using existing MSBuild tasks (both Microsoft-defined and 3rd Party-defined tasks) cannot solve?  Your entire list of requirements in the Design post can be done via MSBuild tasks (albeit some are just calling the appropriate command line executables).

Don't get me wrong, what you wrote is pretty cool.  But it seems like a solution to a problem that's already been solved...

2.
Rory Primrose Rory Primrose Australia says:
Sunday, July 10, 2011 at 8:17 AM

Steve, you are absolutely correct that this could also be achieved using MSBuild tasks. There were a couple of reasons for doing it this way.

The first reason is audience reach. Most developers haven't gotten their hands dirty in MSBuild and this implementation provides a path of least resistance to achieve the same outcome. Additionally, of the developers who have done MSBuild, I suspect that very few actually enjoy it. Smile

The second reason is ease of use. Using MSBuild tasks means that developers have to manually open up the proj files to edit them. Doable, especially with plugins like PowerCommands, but it is not a very smooth editing experience. Changes to proj files also doesn't lend itself to easily reuse the same changes across multiple solutions. Copying build event scripts is much easier although you do need to copy across the BTE program as well.

Oh, third reason, because it was fun Tong

Add comment

  Country flag

biuquote
  • Comment
  • Preview
Loading