Pierre-Emmanuel Dautreppe

So you have setup your continuous integration and every time you are doing a checkin, a new automated build is launched on your build server. Nice !

You have also launched the Team Foundation Build Notification tool to have a small popup alert every time a build finishes and starts. Nice !

But you would like to go a bit further and receive a mail with the build result every time a build fails (or let's say do not succeed).

Let's see here how we can take advantage of the TFS alert tool to received emails, and let's see also how we can customize these emails, using the XSL and XSD the TFS offers us. [Plus]

What happens if you create a new Bug in Team Foundation Server, and if you see afterwards that this is not a bug ? Usually, you would like to reject it. But... you can't! Indeed, by default Team Foundation Server allows you to resolve a bug with one of the following reasons :
- As Designed
- Cannot Reproduce
- Deferred
- Duplicate
- Fixed
- Obsolete
In some cases, none of these values can do the job. So if this does not suit your need, let's see together how can we update the normal workflow to include this new value. [Plus]

I just published a second article on www.developpez.com about "Continous Integration in the Microsoft.NET World".
Here I will present this article and the full summay of these two articles.
Some of the key part of this article are about :
- Writing a basic project file using MsBuild
- How to use Properties and PropertyGroup
- How to use Items and ItemGroup
- How to execute a project file in command line
- How to use the .NET 3.5 tasks
- How to control targets
- Refactoring the project file
- Creating custom tasks
- Some information about TFS (Team Foundation Server)

Just two must-read tutorials about MsTest, Static Code Analysis, MsBuild and TfsBuild. [Plus]

I just published a long article (in french) on www.developpez.com about continuous integration in the Microsoft.NET world. You will find here the table of content of this article :
- Quick introduction to continuous integration
- Quick presentation of the tools needed for Continuous Integration (in the Microsoft.NET world)
- Unit Test : Writing unit tests with MsTest
- Unit Test : Executing tests with MsTest
- Unit Test : Configuring tests
- Unit Test : Managing the tests
- Unit Test : Additional attributes
- Static Code Analysis : Presentation
- Static Code Analysis : Correcting the errors
- Static Code Analysis : Limitations

I will soon publish a second article that will focus that time on MsBuild and TfsBuild. You will see also a first insight on the table of content of this second article. [Plus]

Between TFS (Team Foundation Server) 2005 and 2008, there has been a modification in the default parameter value for the verbosity of the build process. It was set to "normal" before and is now set to "diagnostic" by default.
We'll see here how we can change this parameter for builds using the ".rsp" file and the parameter "/fileloggerparameters". I will also recall the different verbosity levels that exist in MsBuild. [Plus]