VC7 to VC6 project files

I remember reading awhile back in the forums about some VC6 people being upset that eventually TSE might be focused more on VC7 project files, and not worry about updating the VC6 project files. Never fear! :) while surfing around looking for a cheap CodeBlocks solution for a tutorial series I ran into this link in a C::B forum thread.

Quote:
What is this ?

This tool automatically converts Visual C++ 7.0 projects back to Visual C++ 6.0 projects. In other words, .sln/.vcproj file pairs are translated to .dsw/.dsp file pairs.

Important note, there is no loss during the conversion: source code is left unchanged; only .dsw/.dsp are created (or overwritten).
Why?

First of all because MS doesn't provide it. It's easy to become cynical against MS when you feel how bad it is to sell developer tools without all the necessary "moulinettes" (converters in ugly English) to go backward.

Without this tool, you end up recreating your projects from scratch: a total waste of time, and prone to errors. Actually there are several scenarios where this tool is useful:

* Someone gives you a VC++ 7 project, and you only have VC++ 6 installed.
* You have upgraded your project(s) from VC++ 6 to VC++ 7, and you have both .dsw/.dsp and .sln/.vcproj files on your local system drive, but you are willing to keep those files synchronized so any time you need to open the project, you need not bother the VC++ version you work with.
* Provide both versions of projects (for instance when you share code on CodeProject), so your audience does not need to bother with knowing which devtool is required.

How to use it

The tool is a command line of the form:

prjconverter [.sln]

For instance,

prjconverter c:\tmp\betterxml\betterxml.sln

For info, type prjconverter.exe alone in the console.
What is converted

A few steps to let you know how the work gets done. The .sln solution file is opened and translated to the .dsw file format, along with all project declarations, dependencies, and source control tags.

Then all .vcproj project files are translated to .dsp files. I use MSXML to parse the .vcproj file format, and build the meta-model out of it. Then what's left to do is serialize all those XML thingies into the standard .dsp symbol lines.

Of course we care about project configurations (debug, release, ...), and custom file configuration settings.
Technical details

In the code provided, slnprocess.cpp does the .sln =>.dsw conversion. vcprojprocess.cpp does the .vcproj => .dsp conversion. And vcprojconfiguration.cpp holds the project meta-model (all project setting tabs). In VC++ 7, the meta-model is now programmable. Let's check out this link. In fact, vcprojconfiguration.cpp reflects exactly this meta-model (as if it was internal MS code).
Disclaimer...

...

About Stephane Rodriguez.

Addicted to reverse engineering. At work, I am developing business intelligence software in a team of smart people (independent software vendor).

Looking for a native Excel generator (rich, fast, comprehensive)? Look no further.

France, Paris.

Click here to view Stephane Rodriguez.'s online profile.

The link requires free reg, but has done nothing wierd to me since I filled it out.

www.codeproject.com/tools/prjconverter.asp

Rejoice VC6 users, and if you use it, let everyone know if it actually works.

B--