Project / Code conversion from old VS to VS2008+
-
I've got a relatively large project (400K lines) that was developed in Embedded Visual C++. For all intensive purposes, you can consider EVC++ pretty close to VS6. We're migrating to a new OS that requires the use of at least VS2008. Needless to say, the much older compiler allowed us to commit a multitude of sins that the new compiler tosses it's cookies on. I'm pretty sure I could pragma myself to death, but that's "cheating". I'd like to lift the code to a more modern state. Does anyone know of any tools or approaches that can be applied to a set of code that would do most of the heavy lifting? For example, the older compiler allowed methods with no return type. Most of these will be void returns, but at something like 8K errors, it's going to be a lot of $hit shoveling. Appreciate any ideas.
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
I've got a relatively large project (400K lines) that was developed in Embedded Visual C++. For all intensive purposes, you can consider EVC++ pretty close to VS6. We're migrating to a new OS that requires the use of at least VS2008. Needless to say, the much older compiler allowed us to commit a multitude of sins that the new compiler tosses it's cookies on. I'm pretty sure I could pragma myself to death, but that's "cheating". I'd like to lift the code to a more modern state. Does anyone know of any tools or approaches that can be applied to a set of code that would do most of the heavy lifting? For example, the older compiler allowed methods with no return type. Most of these will be void returns, but at something like 8K errors, it's going to be a lot of $hit shoveling. Appreciate any ideas.
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Set the compiler to report Level 4 warnings. Compile, Fix the issues manually, Compile, the issues manually, ... , Make certain it works. After, if you have time (and money, as time==money), then you can start to "lift" the code to a more modern state. Other than that, good luck.
I'd rather be phishing!
-
Set the compiler to report Level 4 warnings. Compile, Fix the issues manually, Compile, the issues manually, ... , Make certain it works. After, if you have time (and money, as time==money), then you can start to "lift" the code to a more modern state. Other than that, good luck.
I'd rather be phishing!
:) yeah, that's what we're looking at... reaching for shovel.
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
:) yeah, that's what we're looking at... reaching for shovel.
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
been there, done that. The hard part is actually not doing refactoring while doing the updgrade and cleaning compilation warnings
I'd rather be phishing!
-
been there, done that. The hard part is actually not doing refactoring while doing the updgrade and cleaning compilation warnings
I'd rather be phishing!
Agree. Somewhen switched the "treat warnings as errors" property in C# projects on. A lot of problems showed up, and you find so much more bad code waiting for refactoring...