Thursday, March 08, 2012 9:13 PM
We have a need to compile a bunch of VS 2003 code using TFS 2010 which were working great with TFS 2008...now, after TFS 2010 upgrade, apparently we got into this tangle of wrong build order discovery process change introduced in MSBuild 4.0 (something similar to this)
Obviously, backward compatibility seems to be not working for all the cases...really unsure whether breaking the build process and forcing it to use MSBuild 3.5 is the best possible solution without changing the project reference or source code as such or upgrading the solution to next VS versions...
Please share your thoughts..
--SS | Microsoft Certified Technology Specialist (TFS 2010)
Monday, March 12, 2012 9:02 AMModerator
I personally think that the solutions either to upgrade the solution to the VS2010 or to use the MSBuild 3.5 in the build process template should work for you. And if you choose to use the second option to force to use the MSbuild 3.5 in the build process template, you can achieve that by using the following approach:Please open the UpgradeTemplate.xml file->Process->Sequence->Run on Agent->Try Compile, Test, and Associate Changesets and Work Items->Try to Compile the Project.
Right-click theRun MSBuild for Project activity and click Properties, select ToolPath, and target the path to the appropriate one which contains the correct version of msbuild.exe.
Vicky Song [MSFT]
MSDN Community Support | Feedback to us
- Marked As Answer by Vicky SongModerator Monday, March 19, 2012 4:01 AM