Upgrade Previous 32-Bit Versions of Visual C++
In Visual C++ .NET 2003, the Visual C++ compiler is significantly more conformant with the C++ standard. See Standard Compliance Issues in Visual C++ for more information.
Projects built in Visual C++ since version 4.x can be opened and saved as projects in Visual C++ .NET 2003.
When a Visual C++ project from Visual Studio .NET 2002 is opened in Visual C++ .NET 2003, a backup copy of the Visual Studio .NET project file is made. Note that any change to the new project file will cause the old project file to become obsolete. Also, note that attempting to rename the old project file so it can be opened in Visual C++ .NET will cause you to lose the changes that were made to the project file in Visual C++ .NET 2003.
If you have many projects that you would like to convert in a batch process, see Upgrading Visual C++ Projects to Visual Studio .NET in Batch Mode.
You may want or need to modify the new project:
- To fix WINVER-related compilation errors
- To use the Standard C++ iostream library instead of a previous version of the iostream library
- To work with the current MFC library
Changes from MFC Version 4.21 covers issues related to upgrading MFC projects.
Upgrade Previous Visual C++ Enterprise Edition Projects
Data sources have their own project in Visual C++. You do not need a C++ project; your project can consist solely of data sources, and you can edit and debug the stored procedures within the data sources.
The data sources appear as a separate database project in Server Explorer. You can switch to Server Explorer by clicking the Server Explorer tab. When you open a project built in a previous version of Visual C++ Enterprise Edition, a database project is automatically created for the data sources. This project appears in Solution Explorer, along with the C++ project that once contained the data sources.
