Avatar of Ingo Foerster
Ingo Foerster
 asked on

Convert VC++ Project 2010 to 2008

do someone know a tutorial or software to convert a Visual Studio 2010 C++ project to a 2008 C++ project? It is really needed for compatibility issues. Thanks

Microsoft DevelopmentC++Editors IDEs

Avatar of undefined
Last Comment

8/22/2022 - Mon

The simple way: Open the '.vcxproj' file and change

<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

to read

<Project DefaultTargets="Build" ToolsVersion="3.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">

That should do it.

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Ingo Foerster

Tried it but this do not work. VS 2008 always told me that the project is not valid.

ms doesn't provide a downgrade of projects. the problem is that some configuration keywords for the xml in the project file have been changed or added (for example the vc directories which moved to project settings) and that vs2008 stops when it detects an unknown entry in the project file.

the only way I know is to creating same project type (and name) in vs2008. then add the sources but not the project files. and finally synchronize the properties both for debug and release. if you make a (text) diff on the project files of vs2010 and vs2008, it should show only a few differences for entries which apparently are new for vs2010. you can run both versions of visual studio same time but they should not use the same sources or project trees.

This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.

To support Sara's last suggestion, sometimes, a complex project might get hosed even without change VS versions. When I attempted to fix it by editing the project files,  I was advised to just create a new solution and add all the files. Given that there were many projects to the program (i.e., solution), I was surprised how fast it actually took to do this. Since you are not destroying the original, you can always look back to see what dependencies there may be to update the new project on the new VS version.
Ingo Foerster

ok, it is not possible so I give the award to the first answer.

ok, it is not possible so I give the award to the first answer.
you can give the points to the first answer. but you should not flag it as the accepted solution cause it is not a solution.

better accept your last comment as the solution (with 0 points).

Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.