eMbedded Visual C++ to Visual Studio Upgrade Wizard
Visual Studio features an upgrade wizard to migrate eMbedded Visual C++ 3.0 and eMbedded Visual C++ 4.0 projects to Visual Studio.
The upgrade wizard will:
Create a Visual Studio solution and project or projects with your source code, headers, and resources migrated from eMbedded Visual C++.
Migrate project settings, such as compiler switches.
Map any architectures that were supported in eMbedded Visual C++ but not in Visual Studio to architectures that are supported in Visual Studio.
Using the eMbedded Visual C++ to Visual Studio Upgrade Wizard
To use the upgrade wizard to migrate an eMbedded Visual C++ project to Visual Studio
On the File menu, click Open, and then click Project/Solution.
Navigate to the directory of your eMbedded Visual C++ project. Select the .vcp file or, if your eMbedded Visual C++ workspace has more than one project, and you want to migrate all the projects, select the .vcw file.
Click OK.
Note
The migration wizard performs an in-place migration process. For example, no copies of your source code will be created, only the Visual Studio project or projects. The Visual Studio projects created by the migration include the same source files that your original eMbedded Visual C++ project included.
Mapping Architectures
eMbedded Visual C++ supported some device architectures that are no longer supported in Visual Studio. This is because the newer platforms that Visual Studio targets support newer architectures. Fortunately, all the older architectures can be mapped to the newer device architectures. The upgrade wizard performs this mapping automatically. The table illustrates eMbedded Visual C++ supported device architectures versus Visual Studio supported device architectures:
eMbedded Visual C++ Architecture |
Compatible Visual Studio Architecture |
|---|---|
ARM |
ARMv4 |
ARMv4 |
ARMv4 |
ARMv4i |
ARMv4i |
ARMv4T |
ARMv4i |
MIPS |
MIPSII |
Mips16 |
MIPSII |
MipsII |
MipsII |
MipsII_fp |
MipsII_fp |
MipsIV |
MipsIV |
MipsIV_fp |
MipsIV_fp |
SH3 |
SH4 |
SH4 |
SH4 |
Emulator |
X86 |
X86 |
X86 |
When the eMbedded Visual C++ project is upgraded by using the wizard, the new project created in Visual Studio targets all the installed SDKs that support the architecture in the new project. Migrated architectures inherit their settings from one of the eMbedded Visual C++ architectures. The following table illustrates the mapping of eMbedded Visual C++ supported device architectures versus Visual Studio supported device architectures.
Original Architecture |
Map to |
Notes |
|---|---|---|
Not ARM/ARMV4/ARMV4I |
See table in "Mapping Architectures" |
|
ARM but no ARMV4i |
ARMV4 and ARMV4i |
ARMV4i config settings inherit from the ARM config in eMbedded Visual C++. |
ARMV4 but no ARMV4i |
ARMV4 and ARMV4i |
ARMV4i config settings inherit from the ARMV4 config in eMbedded Visual C++. |
ARM/ARMV4 and ARMV4i |
ARMV4 and ARMV4i |
ARMV4i config settings inherit from the ARMV4i config in eMbedded Visual C++. |
Embedded Visual C++ version 4.0, by default, sets dialog box style to DS_MODALFRAME for MFC Pocket PC applications. In MFC 9.0 this style is not supported.
Note
If you receive an error message that states "No platforms are available that match this project file's original platforms," you may have to install a compatible version of the SDK with which the original project was configured.