Geeks With Blogs


Google My Blog

Catch me at: The List!

My InstallScript Utility Belt My Amazon Wishlist
My Standard Disclaimer

Chris G. Williams Beware: I mix tech and personal interests here.
(sorry for the corny title... I haven't had much sleep)

ok, I gotta play with this:

Starting with the Visual Studio 2005 release, the Microsoft build engine black box is extracted from Visual Studio. The new build engine, MSBuild, becomes extensible and available for all since it will ship with the .NET Framework.

How will this affect me? I work with a small team (part of a larger whole) and I'm the guy responsible for the build. We have an in-house build automation tool, XML driven of course. Currently our build tool consists of pre- and post-build steps. It fetches the latest code (or whatever we specify) builds whatever pieces we specify, in the order we specify. Of course, there's no control over "how" a build happens. No flexibility in the build environment. Having said that, all in all it works pretty well...

So, apparently MS Build provides an "extensible build framework"... Naturally I'm curious to see if this will have an impact on the way we do things. Posted on Saturday, June 4, 2005 9:05 AM General Interest | Back to top

Comments on this post: (that's) MS Build (if you're nasty)

# re: (that's) MS Build (if you're nasty)
Requesting Gravatar...
At first I was also very excited with MSBuild and tried to use it on our current project. But after a while it turned out that any additional action was so darn hard to implement that I gave up and switched back to NAnt for scripting everyting besides the actual compilation. However thanks to MSBuild I don't need to install VS on my build server. I'm using it with CruiseControl.NET and I wrote a XML Logger to capture the build output (you can find it on my blog).
Left by Szymon on Jun 04, 2005 9:55 AM

Your comment:
 (will show your gravatar)

Copyright © Chris G. Williams | Powered by: