Welcome to MSDN Blogs Sign in | Join | Help

January 2006 - Posts

Confusing behavior of MSBuild logger on raising LogError event

Today I found that raising the error message was not enough for the msbuild to stop and invoke the targets specified by OnError tag. For example in the given sample - Custom task:- MSBuildTask.dll namespace MSBuildTask { public class MSBuildTask : Task

AT degradation when multiple instances of GenCheckinNotesUpdateWortItem task are happening concurrently ...

Investigation for the observation made in post . " CPU consumption on AT went up to the maximum of 38% (w3wp.exe) while the GenCheckinNotesUpdateWorkitem task was executing on the build machine." Case 1 - 3 msbuild processes in separate window - running

Why GenCheckinNotesUpdateWorkitem task is expensive !!!

Performance data for GenCheckinNotesUpdateWortItem task (all times in ms) 1. For MSTV project (~ 17 MB) a. Failed 1 st build - Time in Task – 110848 QueryLabel – 990 AnalyzeChangeset – 105870 QueryHistory – 105800 UpdateWorkItem – 3737 Get_WorkItem -

GenCheckinNotesUpdateWorkitem task is expensive !!!

GenCheckinNotesUpdateWorkitem task is the most expensive and takes most of the build time. The problem is worst when you launched the build for the first time for a new build type. Why? What can be done about it? Some statistics related to builds in Team

What is GenCheckinNotesUpdateWorkitem task?

As a part of the standard build process, we first get the latest sources from the repository, apply the label, build, get the checkin details between last successful build and current build (change sets) and the work items that were resolved by these

Status@2006.01.22

Now I am a Clockwork Orange

AdditionalReferencePath in Team Build

In Team Build, AdditionalReferencePath items (defined in the tfsbuild.proj) are used to specify the reference paths for resolving the external references. They are similar to HintPath. For example you can specify the lookup folder (C:\Common\Binaries)
 
Page view tracker