Everything worked great migrating VS2008 resolution to VS2010 option … didn’t it?,
microsoft office 2010 pro keygen!?
TFS2008 had a word, because of a reference: unit test projects have reference to Microsoft.VisualStudio.QualityTools.UnitTestFramew ork.dll,
windows 7 professional 32 bit, version 10.0.0.0 .
Of course!!!
TFS machine didn’t have .Net4.0 (or VS2010,
microsoft office 2007 activation!!!) installed on…done!
Note: VS2010 doesn’t permit change target framework unit test projects, stuck to .Net 4.0, so installing .Net 4.0 is a must!
Again,
windows 7 ultimate activation key, TFS2008 wasn’t able find that .Net 4.0 assembly … MSBuild build path isn’t updated … yeah!
In order to add new libraries path, you have to updated build service config file (C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\TfsBuildService. exe.config) and update MSBuildPath value with assemblies path.
full guide here: How To Build VS2010 Solutions Using TFS2008 Team Build
Technorati tags: TFS,
microsoft office Ultimate 2007 key, Visual Studio, MSBuild, Unit Test