our months ago, Microsoft publicized a list of features that could cause existing Visual C++ apps to break
when migrated to Visual Studio 2005. Many of these features are core C++ updates that are meant to bring Visual C++ to full compliance with ISO C++. There's no doubt that these changes are a major improvement over the non-compliant hacks that have been in use since the mid-1990s. The downside is that migrating to Visual Studio 2005 requires a thorough code reviewand possibly some repairs. The following sections show some of the code changes required for porting existing C++ apps to Visual Studio 2005.
Your Visual C++ 6.0 apps will not compile when migrated to Visual Studio 2005 unless you fix them. How do you go about it?
Use this check list to locate incompliant code spots and repair them according the following guidelines.