Meta Data Services Programming
Invoking MergeVersion
When you invoke MergeVersion, the object version you will use as predecessor of the merge must already be frozen. The object version to be modified, the successor of the merge, cannot be frozen.
Briefly, the merge operation has these results:
- The object's version graph is updated to indicate that the merge operation occurred.
- The successor object can have different property values or collections.
You invoke MergeVersion on the successor version of the merge; you pass a reference to the predecessor as an input parameter. You also pass an indication of which version is to be considered the primary version. The primary version is the version whose member values are given priority when there are merge conflicts between the two versions.
See Also
IRepositoryObjectVersion::MergeVersion
Resolving Merge Conflicts for Collections