We have a solution which contains some 200 projects. Most of them are VC++ projects. We have been hit with rebuild issues for some projects. In some cases MSBuild process is still running in the background after the build is complete causing VS 2010 to crash.
After troubleshooting the issue further, i noticed that MSBuild complains of command line change and rebuilds cpp files.
The issue is reproducable almost all the time, after building the project from the master solution if i rebuild the project separetly from another VS 2010 instance, it claims that the command line has changed and it rebuilds it.
Forcing rebuild of all source files due to a change in the command line since the last build. (TaskId:22)
After comparing both the command lines, the only difference I find is the /b argument that has been specified for the tracker.exe
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools\Tracker.exe /d C:\Windows\Microsoft.NET\Framework\v4.0.30319\FileTracker.dll /i C:\Src\trunk\tempBuild\x64\Debug\WinTools /r C:\SRC\TRUNK\LIBS\WINTOOLS\STDAFX.CPP /b MSBuildConsole_CancelEventbc42312c663c4b3fbf7ad9c0d03688e2
/c "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\CL.exe" /c /IC:\Src\trunk\commonProperties\..\PrecompiledHeader /IC:\Src\trunk\commonProperties\..\com /IC:\Src\trunk\commonProperties\..\libs /IC:\Src\trunk\commonProperties\..\libs\Imports\x64\Debug\
/Zi /nologo /W3 /WX- /MP /Od /D OEMRESOURCE /D WINTOOLS_BUILD /D WIN32 /D _WINDOWS /D WINVER=0x0502 /D _CRT_SECURE_NO_DEPRECATE /D _WINDLL /D _AFXDLL /D _AFXEXT /D _DEBUG /D _WINDLL /GF /Gm- /EHsc /RTC1 /MDd /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Yc"StdAfx.h"
/Fp"C:\Src\trunk\commonProperties\..\tempBuild\x64\Debug\WinTools\PrecompiledHeader.pch" /Fo"C:\Src\trunk\commonProperties\..\tempBuild\x64\Debug\WinTools\\" /Fd"C:\Src\trunk\commonProperties\..\tempBuild\x64\Debug\WinTools\ProgramDatabase.pdb" /Gd /TP /errorReport:prompt
StdAfx.cpp (TaskId:22)
Especially the part which is highlighted below:
/b MSBuildConsole_CancelEventbc42312c663c4b3fbf7ad9c0d03688e2
Any thoughts on why would that part be different when executing the same project from two different instances of VS 2010 or is just by design? Am I troubleshooting the issue in an incorrect manner?
Please remember to mark the replies as answers if they help Thanks, --Kuldeep