Hack the Build: Programmatically Converting Older VS .NET Projects to MSBuild

How to convert older VS .NET projects to MSBuild

.Net Adventures — Mon, 29 Nov 2004 22:50:00 GMT

re: Hack the Build: Converting Older VS .NET Projects to MSBuild

Lonnie McCullough — Mon, 29 Nov 2004 22:54:00 GMT

Since you mentioned it, could you talk a little about how you use NUnit to test. My company is looking into changing some of our methodologies and TDD has come up as the last best hope ;-). If not I'll understand, but I just think a lot of people are interested in how MSFT does the things it does.

re: Hack the Build: Converting Older VS .NET Projects to MSBuild

Lorenzo — Tue, 30 Nov 2004 11:12:00 GMT

Great! It seem to be the right way to resolve my problems. Today I'll try to code it into my project. Thank you Jomo! <br>

re: Hack the Build: Programmatically Converting Older VS .NET Projects to MSBuild

Leo Duran — Wed, 29 Dec 2004 20:47:00 GMT

This little tip saved me a helluva lot of work! Thank you!

How to convert older VS .NET projects to MSBuild

.Net Adventures — Wed, 19 Jan 2005 10:37:00 GMT

Hack the Build: Code Quality and Test Driven Development at Microsoft

Hack the Build — Mon, 16 May 2005 20:13:01 GMT

Jomo Fisher--I mentioned a while ago that MSBuild team uses Test Driven Development (TDD). Afterwards,...

Hack the Build: Use the Whole Test-First Whale

Hack the Build — Wed, 25 May 2005 21:01:26 GMT

I don’t think of Test Driven Development as just a goal in itself. I think of it as a platform for a set of code-quality drivers. What follows is a set of ideas for how to wring the maximum use out of your developer-written tests.