Welcome to MSDN Blogs Sign in | Join | Help

September 2005 - Posts

Resolving file references in team build ( Part -2 )

Salient points about file references File reference is used to reference outer system assemblies (i.e .NET framework assemblies, third party assemblies or assemblies that are not generated by the current solution). File reference is defined by the reference

Example on how to resolve project to project reference (for single solution) in team build.

Consider a simple solution (OfficeSolution.sln) that has one main project (OfficeSolution.csproj). The main project has dependency (project to project reference) on two independent sub projects (WordApplication.csproj and ExcelApplication.csproj). Note

Resolving assembly references in Team Build ( Part - 1 )

In this entry I will be discussing about project to project references. I will be enumerating about different scenarios and mentioning workarounds to get them to build in Team Build. Scenario 1 - Single solution containing multiple projects. Projects

Guidelines on structuring solutions and projects in team build

Single solution is best for small size projects. The most scalable and efficient way for managing and building large applications is team build is to have multiple independent solutions. Always avoid solution to solution references. They are not supported

How to running multiple tests in team build?

In beta3 you have better control on the way tests are executed. Some common scenarios are:- To run tests of different categories :- You need to modify tfsbuild.proj file to introduce additional test category. For example if your metadata item is defined

Team build reported successful build but still some assemblies are missing at drop site?

Question :- I was building 3 projects. The sln and csproj files of the first and thirld project supported building for configuration (“Debug|x86”) but second project didn’t supported it in its build scripts. I build these projects using Team Build for
 
Page view tracker