By defaul, the CCNet can monitor only changes in one project folder and its subfolders in the Source Control system. Starting from from v1.3 the CCNet can monitor multiple projects in the Source Control systems. You can use the ‘Multi’ Source Control block to check for modifications from any number of source control repositories. Here is a description of the ‘Multi’ Source Control block in the CCNet configuration file.
Read the rest of this entry

In VS2005 running Unit Tests with Code Coverage enabled and having the Assembly signed all unit tests fail. You may see then an error message “Strong name validation failed“. The reason is simple.
Read the rest of this entry

The problem is not really obvious as it might seem. Once you get the version of the project from the Team Foundatin Server to a specific folder on your local machine, you cannot easily change the working folder of the project. In the Visual Source Safe it’s easy to define the working folder in the VSS Client. But in the Team Explorer (a Visual Studion tool to access the Team Foundation Server) this functionality is a bit hidden.
Read the rest of this entry

Recently, I’ve faced with a problem when suddenly I started getting error messages loading a project from the Team Foundation Server. The solution consists of 5 projects, and during loading of the solution one of the project was not loaded and I received the error message “The project file ‘ ‘ has been moved, renamed or is not on your computer“. It took me a while to solve the problem. It seems to be a bug in the Visual Studio / Team Foundation Server. The problem is that the binding information was not correctly saved in the .suo file.
Read the rest of this entry

In Visual Studio 2005 / 2008 you can enable Code Analysis of your Unmanaged C++ project. The Code Analysis gives useful information of what part of your code does not meet the quality criteria. However, the Code Analysis also performs analysis of all system header files, which are used in the project. As it’s least likely that system header files will be modified by developers, this behavior is undesirable. For instance, Code Analysis will display a lot of messages compiling WTL header files.
Read the rest of this entry

The process of migration of source code to Team Foundation Server from Visual Source Safe databases is described in details here.

However, this Manual contains some discrepancies and I would like to mention here some of them and also to give some recommendations.
Read the rest of this entry