Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Another "hiccup" this week after upgrading my Team Foundation Server (TFS) 2008 environment to TFS 2010...
This morning I discovered that when you upgrade a managed C++ project from Visual Studio 2008 to Visual Studio 2010, the project is updated automatically to target .NET Framework 4. Unlike most other project types, you can't just quickly change a project setting in order to target an earlier version of the .NET Framework.
Note that you can force a managed C++ project to continue to target one of the older versions of the .NET Framework, as described in the following:
Visual Studio 2010 C++ Project Upgrade Guide
https://blogs.msdn.com/vcblog/archive/2010/03/02/visual-studio-2010-c-project-upgrade-guide.aspx
However, you'll need to have Visual Studio 2008 installed on your build server -- or, presumably, you could choose to install the Microsoft Windows SDK for Windows Server 2008 and .NET Framework 3.5 instead (as I described in one of my blog posts last year).
Instead of tweaking the build (and having to re-install the SDK or Visual Studio 2008 on the build server), I chose instead to upgrade the other projects (that reference the managed C++ project) to .NET Framework 4.
As I've mentioned in the past, I'm not doing very much in C++ these days, and my primary objective was to get my "Toolbox" solution to build in my upgraded environment.
For lots more useful information on upgrading C++ projects to Visual Studio 2010, refer to the "Project Upgrade Guide" post referenced above.