Wednesday, January 20, 2010
CI in .NET Chapters 3 and 4
Wow! Has it really been three months since my last post? Well, I have a good reason for it. I've been hard at work, along with Marcin, on our book, Continuous Integration in .NET. We've had some speed bumps along the way, but I think we're now working well together.
For those of you who don't know, Marcin is from Poland and I am from the US. We got to meet in person in November when I was in Germany for the German FoxPro DevCon.
So, what have we been busy doing? Writing and editing of course. The first eight chapters have been written, but not edited to the point we can MEAP them. However, earlier tonight Manning posted the first MEAP for Chapters 3 and 4. That means you now have access to 1/3 of the book!
Wondering what's new? Chapter 3 introduces MSBuild as an automation build platform for .NET Continuous Integration. The chapter begins with the basics, then takes you through the usage of community contributed functionality. By the end, you'll be developing your own custom build tasks.
Chapter 4 guides you through the process of choosing the right CI server for your needs. It covers CruiseControl.NET, TeamCity, and TFS 2010. After you finish reading Chapter 4, you should be able to navigate your way through the options of the CI world.
Keep an eye out for Chapter 5, which will look at diverse feedback mechanisms provided by CI servers.
For those of you who don't know, Marcin is from Poland and I am from the US. We got to meet in person in November when I was in Germany for the German FoxPro DevCon.
So, what have we been busy doing? Writing and editing of course. The first eight chapters have been written, but not edited to the point we can MEAP them. However, earlier tonight Manning posted the first MEAP for Chapters 3 and 4. That means you now have access to 1/3 of the book!
Wondering what's new? Chapter 3 introduces MSBuild as an automation build platform for .NET Continuous Integration. The chapter begins with the basics, then takes you through the usage of community contributed functionality. By the end, you'll be developing your own custom build tasks.
Chapter 4 guides you through the process of choosing the right CI server for your needs. It covers CruiseControl.NET, TeamCity, and TFS 2010. After you finish reading Chapter 4, you should be able to navigate your way through the options of the CI world.
Keep an eye out for Chapter 5, which will look at diverse feedback mechanisms provided by CI servers.
// posted by Craig Berntson @ 10:01:00 PM 
Comments:
Links to this post:
<< Home
Don't forget Hudson! It's got great .NET integration--we're using it for all of our .NET projects. While not as transparent as TeamCity, it's a breath of fresh air compared to CC.NET.
You may want to at least mention a few of the other build servers and a few of the strengths or intents behind each.
You may want to at least mention a few of the other build servers and a few of the strengths or intents behind each.
Hudson is a great product, but we had to draw the line somewhere on what we wanted to cover. We mention Hudson and other CI servers in the book, but don't do any comparison with them and CCNet, TeamCity, and TFS.
Post a Comment
Links to this post:
<< Home
Subscribe to Posts [Atom]
