Migrating an OS Design to Windows Embedded CE 6.0
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
In Windows Embedded CE 6.0, you can open Windows CE 5.0 OS design (.pbxml) files by in the Visual Studio environment, which automatically performs the upgrade process.
Note
After a Windows CE 5.0 OS design file has been opened and saved in Windows Embedded CE 6.0, the file will no longer function in a Windows CE 5.0 environment. To work around this issue, it is recommended that you create a copy of the file before opening it in Windows Embedded CE 6.0.
When a Windows CE 5.0 OS design file is opened, Windows Embedded CE 6.0 attempts to discover matches for the included Catalog items in the Windows Embedded CE 6.0 Catalog. If a match is found, then the metadata from the newer version of the Catalog item is used to determine which sysgen variables should be set. However, if no match is found, then the Windows CE 5.0 metadata is used to set sysgen variables. This results in the exclusion of obsolete Catalog items from the upgraded OS design.
It is recommended that you do a visual side-by-side comparison of both OS design versions after the migration to familiarize yourself with the changes that might occur as a result.
If you have a Windows CE 5.0 Catalog item (.cec) file that you want to migrate to the Windows Embedded CE 6.0 Catalog, for more information, see Migrating a Catalog Item.
For information about adding Catalog items to an OS design, see Adding Catalog Items to an OS Design.