|
#1
|
|||
|
|||
The first step would be to reproduce your msbuild call within Visual Build via a Run Program action (starting Visual Build from the VS 2008 command prompt to replicate the environment it initializes).
The second step would be to convert this to a MSBuild step in Visual Build, preceded by a Set Current Dir step to set the working folder (still starting from the VS 2008 command prompt). The third step would be to call the vcvarsall.bat (what the Visual Studio 2008 Command Prompt does) in the MSBuild step's Command to run before main command field on the Advanced tab, to setup the environment within the build instead of relying on the VS command prompt. |
#2
|
|||
|
|||
Quote:
|
#3
|
|||
|
|||
Visual Build itself doesn't call or use any Tracker.exe. Maybe its path is not in the PATH environment of the Visual Build process and it can't be located?
|
#4
|
|||
|
|||
Quote:
describe the need for it but I dont wanna update my build machine to vs 2010. Please help. |
#5
|
|||
|
|||
Looks like you would need to disable tracking as mentioned in that article, or maybe install the Windows SDK.
|
#6
|
|||
|
|||
Hi,
I totally appreciate your prompt and useful inputs, however the problem was not with Tracker.exe (infact there is NO TRACKER.EXE that is being shipped with VS 2008) but it turned out that VisualBuld by default was using MSBUILD.EXE in .net framework v4.0 which LOOKS FOR TRACKER.EXE for incremental compilation. The simplest solution that I figured out was to OVERRIDE MSBUILD.EXE with .net framework v3.5 and wallah...it all worked great.. I just wanted to share the closure on this issue so if someone else is facing the same issue, this solution could help em. Thanks again for the wonderful work and keep up the good work! VisualBUild is much appreciated in my part of the world. |
|
|