## Synchronizing versions

### Automatic synchronization at build time (Recommended)

If the plug-in version changes frequently and/or developers do not have access to the feature, the versions of plug-ins, fragments and included features can be set to the special value 0.0.0 that will be replaced when exporting the feature. This is especially convenient when plug-in version are automatically upgraded using the qualifier tag.

### UI driven synchronization

The versions of plug-ins and fragments should be synchronized with the version of the packaged feature so that you can manage plug-in, fragment, and feature versions consistently. Developers typically ignore individual manifest versions until it is time to deploy their features. The Update Manager uses feature versions to determine whether a plug-in is older or newer than one already installed. Plug-ins and fragments need to follow the same version number conventions so there is no confusion about which plug-in version belongs to which feature version.

The most convenient way to synchronize versions is to pick the version of the feature and force it into all the plug-ins and fragments that the feature references. This operation updates manifest files, so you are required to close all the manifest editors before proceeding.

#### Example: Synchronizing versions in the feature editor

We will take our ongoing example and force the feature version (1.2.2) into "XYZ Plug-in" and "German Fragment."

1. Open the component manifest editor.
2. Select Synchronize versions... from the popup menu. A wizard will open.
3. Select the first radio button ("Force feature version..."). Press Finish.
4. Switch to the Content page verify that the versions are now 1.2.2.
5. Double-click on "XYZ Plug-in" and "German Fragment" objects and verify versions in their corresponding manifest editors.

###