Export (0) Print
Expand All

eMbedded Visual C++ to Visual Studio 2005 Upgrade Wizard 

Visual Studio 2005 features an upgrade wizard to migrate eMbedded Visual C++ 3.0 and eMbedded Visual C++ 4.0 projects to Visual Studio 2005.

The upgrade wizard will:

  • Create a Visual Studio 2005 solution and project or projects with your source code, headers, and resources migrated from eMbedded VC++.

  • Add MFC dll to deploy list for migrated MFC projects.

  • Migrate project settings, such as compiler switches.

  • Map any architectures that were supported in eVC but not in Visual Studio 2005 to architectures that are supported in Visual Studio 2005.

Using the eVC to Visual Studio 2005 Upgrade Wizard

To use the upgrade wizard to migrate an eVC project to Visual Studio 2005

  1. On the File menu, click Open, and then click Project/Solution.

  2. Navigate to the directory your eVC project is in. If your eVC workspace only has one project, you can select either the .vcw or the .vcp file If your eVC workspace has more than one project, and you wish to migrate all the projects, select the .vcw file.

  3. Click OK.

NoteNote

The migration wizard performs an in-place migration process; for example, no copies of your source code will be created, only the Visual Studio 2005 project or projects. The Visual Studio 2005 projects created as a result of the migration will include the same source files that your original eVC project included.

Mapping Architectures

eMbedded Visual C++ supported some device architectures that are no longer supported in Visual Studio 2005. This is because the newer platforms that Visual Studio 2005 targets support newer architectures. Fortunately, all the older architectures can be mapped to the newer device architectures. The upgrade wizard performs this mapping automatically for you. The table illustrates eMbedded Visual C++ supported device architectures versus Visual Studio 2005 supported device architectures:

eVC Architecture Compatible Visual Studio 2005 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 eVC project is upgraded using the wizard, the new project created in Visual Studio 2005 targets all the installed SDKs that support the architecture in the new project. Migrated architectures inherit their settings from one of the eVC architectures. The following table illustrates the mapping of eMbedded Visual C++ supported device architectures versus Visual Studio 2005 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 eVC.

ARMV4 but no ARMV4i

ARMV4 and ARMV4i

ARMV4i config settings inherit from the ARMV4 config in eVC.

ARM/ARMV4 and ARMV4i

ARMV4 and ARMV4i

ARMV4i config settings inherit from the ARMV4i config in eVC.

Embedded Visual C++ version 4.0, by default, sets dialog box style to DS_MODALFRAME for MFC Pocket PC applications. In MFC 8.0 this style is not supported.

NoteNote

If you receive an error message that says "No platforms are available that match this project file's original platforms," you may need to install a compatible version of the SDK with which the original project was configured.

See Also

Community Additions

ADD
Show:
© 2014 Microsoft