Versions
5/10/2007
Groups, repositories, and released components are upgradeable. When an item is upgraded, a new version is generated that can coexist with earlier versions of that item in the database.
Upgrading is done with the use of a version-specific globally unique identifier (VSGUID). Each item has a VSGUID and a revision number. When an item is upgraded, its revision number is incremented and it is assigned a new VSGUID. Items with different VSGUIDs are allowed to coexist in the database.
Note
The Version property that is displayed for an object is not incremented when a new VSGUID is assigned. This value must be incremented manually in Component Designer.
For components, a second GUID is also used. A version-independent globally unique identifier (VIGUID) is shared by all versions of a component. When a component is upgraded, the VIGUID remains the same. This binds the versions together.
Unreleased components are revised rather than upgraded. For more information, see Revisions.
In This Section
- Upgrade Process
Describes what happens when a component is upgraded.
- Versions and Cross-Component References
Describes how VIGUIDs and VSGUIDs are used to ensure that the right component versions are specified in cross-component references.
- Versioning of Components in Configurations
Describes how component versions are managed within configurations.
Related Sections
- Versioning
Describes the versioning scheme that is used to revise and upgrade components and other objects.