I have a project that I manage that as a development team we decided to upgrade to VS2010 from VS2008. There was not a huge reason for this, but was interested in trying out the beefed up testing, coverage and profiling tools in VS2010.
The upgrade of the project went pretty well, except for some problems with PostSharp, that were able to be resolved by upgrading to a CTP version of PostSharp 2.0. The reasoning for that and the list of struggles will have to be another post.
After getting things to compile and run on my local machine, decided that it was time to commit back to SVN for the rest of the team to use. I expected to have problems with the build server, which runs CCNet, but was not sure what it would be. So for the sake of documenting this for myself, here is what I had to do.
Steps:
- Install the 4.0 Framework.
- Build error for missing import: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets
- I copied the entire C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0 folder to my build server
- Could not load assembly Microsoft.ReportViewer.WebForms
- Copied C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\ReportViewer\ReportViewer.exe to build server and ran the installer.
- error MSB3454: Tracker.exe is required to correctly incrementally generate resources in some circumstances, such as when building on a 64-bit OS using 32-bit MSBuild. This build requires Tracker.exe, but it could not be found.
- Added a new PropertyGroup with property for TrackFileAccess to false.
- Needed to do this because SDK is not yet available.
- figured this out from: http://bradwilson.typepad.com/blog/2010/05/working-around-build-error-msb3454.html
- error MSB3086: Task could not find "LC.exe" using the SdkToolsPath
- OK – I seem to be stuck here until there is an SDK to support 4.0.
At this point, I changed my build process to call MSBuild from the 3.5 framework instead (which we were still targeting despite using VS2010). This created some warnings about referencing a 4.0 ToolsVersion (Project file contains ToolsVersion=4.0, which is not supported by this version of MSBuild. Treating the project as if it had ToolsVersion=3.5.), but got me past the issues I was having until the Windows 7.1 SDK is released.
