Concepts in the Platform Builder IDE
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
The integration of Platform Builder into Visual Studio brings changes to terminology and concepts for Windows Embedded CE.
For information about Windows Embedded CE terms and concepts not specific to the transition to Visual Studio, see Terminology in Windows Embedded CE.
Terminology Related to the Transition to Visual Studio
- solution
A container that a user can open in Visual Studio. This term is a standard Visual Studio term. A solution can contain more than one project, and it can contain more than one Windows Embedded CE OS design and corresponding subprojects.
- project
A container that a user can open in Visual Studio from within a solution. This term is a standard Visual Studio term. In previous versions of Windows Embedded CE, the term project had a different meaning.
- OS design
For a definition, see Terminology in Windows Embedded CE. In Windows Embedded CE 6.0, a Windows Embedded CE OS design is a Visual Studio project.
- subproject
A container that is the Windows Embedded CE 6.0 counterpart to a Windows CE 5.0 project.
File Name Extensions
- .pbxml
File format for the metadata that defines a Windows Embedded CE OS design.
- .pbpxml
File format for the metadata that defines a Windows Embedded CE subproject. For more information, see Subprojects.
- .pbcxml
File format for the metadata that defines a Windows Embedded CE Catalog item. For more information, see Migrating to the Windows Embedded CE 6.0 Catalog.
See Also
Other Resources
Migrating to the Windows Embedded CE 6.0 IDE
Terminology in Windows Embedded CE