Migration from VC 6.0 to Visual studio 2005

[VC_RYK]

Hi experts I have to migrate some projects from VC 6.0 to visual studio 2005. Is Anything required to achieve it and what waht kind of problem i can face? As far as my knowledge is concerned, All upper version products automatically converts the project from older version to new one. With regards R Y K

[Chris Losinger]

you will probably have to fix a lot of these:

for (int x=0...)
{
}

for (x=0;...)
{
}

the scope of the first x is limited to the first for loop, after VC6.

image processing toolkits | batch image processing

[David Crow]

VC_RYK wrote:

Is Anything required to achieve it and what waht kind of problem i can face?

You will likely run into Unicode-related issues. That and variable scope are the two biggest issues I've faced when porting one to the other.

VC_RYK wrote:

As far as my knowledge is concerned, All upper version products automatically converts the project from older version to new one.

Yes, it converts the project, not the code.

"One man's wage rise is another man's price increase." - Harold Wilson

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

"Man who follows car will be exhausted." - Confucius

[peterchen]

Why VS2005? Consider VS2008 or VS 2010 (though the latter is a bit of a moving target still). The step from VC6 to VS2005 is the big one though. Upgrade Wizard will (try to) port your project files - this usually works ok - but you are alon wiht changes requried to your source code. Compiler: VS 2005 provides improved standard compatibility, the most common issues being for scope, more rigorous checking of templates, and other minor things. For a list of breaking changes, see here[^] and here[^]. Unicode: Project settings now default to unicode. Moving from ANSI/MBCS to Unicode is a completely different story, you may want to take this as a separate step. "Safe" CRT functions - many functions of the C/C++ Runtime will now generate a warnign that they should be replaced by safe counterparts - mostly to avoid potential buffer overflows and encourage more rigorous error checking. This is often a barrage of warnings, burying everything else under it. For more information, see here[^]. IDE + Build Performance - Get a really good computer. I mean it. Windows Headers - we had some problems with some of the more arcane windows library headers moving some declarations around, requiring ugly include reordering and supressing some declarations being made / imported. That's unlikely to bite you, but can be an immense time sink.

Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server.