Migrating from MSVC 6.0 to Studio 2005?

greywar asks: "While the preferred method would be simply use Linux, unfortunately my company is using Microsoft Visual Studio 6.0 with C++. I have been asked to recomend if we should upgrade to the new upcoming visual studio 2005. Has anyone got any real life experience with moving a project of about 220,000 lines of code, 60,000 lines of comments from the old MSVC to the new Studio 2005 which is currently in Beta? What benefits are there, and what things do we lose? What problems will occur?"

Comments

VB.Net is NOT VB 7

[RingDev]

Okay, I preach on this at http://www.tek-tips.com/ way too much.

VB.Net (any version) IS NOT the next version of VB.

VB.Net is a fully object oriented language, it is fundamentally different then VB6. Your best option is to document the heck out of the current app's functionality and behavior, and then look into developing a .Net app from scratch to match those behaviors.

The built in porting tool will not work. It's kind of like an san script to english translator. It can replace old words with new words, and guess at what the code means, but since the two are fundamentally different, it can not effectively convert everything appropriatly. If your entire VB6 app was writen perfectly in an object oriented manor (as best as was possible in VB6), then the converter might work acceptably. But realisticly, running the converter is going to leave you with a uncompilable piece of crap.

-Rick