Welcome to MSDN Blogs Sign in | Join | Help

December 2005 - Posts

Working with multiple team projects in Team Build

Building solutions that reference to assemblies belonging to different team project Scenario Assume that we two projects (ConsoleApplication1 and ConsoleApplication2) under team project (TP1) and they are using the assembly (commonlibrary.dll) that is

Easy way of doing customization for all build types in Team Build

What is the best way to override the properties, items and targets defined in Tfsbuild.proj and Microsoft.TeamFoundation.Build.targets file? Additional how to pull all the customizations out of specific build type (Tfsbuild.proj) and make it available

Defining common fxcop ruleset for all projects/solutions/configurations

User wants to configure a common set of fxcop rules and use them for all projects/solutions. Does he need to configure the common set for every new project/solution/configuration? No. User need to override the "CodeAnalysisRules" property to include the

Interesting behavior in desktop build ...

Desktop build not stopping immediately on build break ... Details If I am building two solutions sln1 and sln2 for two configuration debug|x86 and release|x86 and there is a compiler error in sln1. The build process tries to build sln1 (for debug|x86)

MSbuild tasks to integrate/customize Team Foundation Version Control functionality with Team Build

You can use MSbuild exec task to execute any system command. The task also gives you option to specify the working folder from where to execute the command. This is useful for the scenarios where you want to run a tool from specific location. Do note

Workspaces in Team Build

Workspace represents the client side view of the source control repository. When you create new build type using wizard, you have the option of selecting the template workspace. This implies that you want to have the same view of repository as defined
 
Page view tracker