Partager via

Versioning

  • Article

5/10/2007

The Windows XP Embedded product version is provided by a registry key.

All components, groups, and repositories are subject to a versioning scheme. This scheme allows different versions of an item to co-exist in the database. In addition, each version can be revised, and only the latest revision of a version can exist in the database at any given time.

Versioning ensures that configuration builds remain both consistent and repeatable, regardless of changes made to the database. For example, when a service pack ships with a new version of a component, that version can be imported into the database without displacing the existing version. Existing configurations that rely on the previous version continue to use the version of the component that they were authored against, while new configurations can use the new version. At a convenient time, a configuration that uses the old version can be upgraded in Target Designer to use the new version of the component.

To revise or upgrade an item, you must edit it in Component Designer and re-import into the database using Component Database Manager. In general, revisions occur during the development process and upgrades occur between releases.

In This Section

  • Revisions
    Describes how and when objects are revised.
  • Versions
    Describes how and when objects are upgraded.
  • About Windows XP Embedded
    Describes components, groups, repositories, and other concepts fundamental to Windows XP Embedded.
  • Components
    Describes the individual units of functionality that make up a run-time image and the benefits of creating and using them.
  • Groups
    Describes the different groups to which components and repositories can belong and the ways in which groups are used.
  • Repositories
    Describes the archives that are used as a source of binary and other files during the construction of a run-time image.