This document is archived and information here might be outdated.  Recommended version.

IVersionedObject3.RegisterAsVersioned3 Method (ArcObjects .NET 10.8 SDK)
ArcObjects Help for .NET developers > ArcObjects Help for .NET developers > ArcObjects namespaces > Geodatabase > ESRI.ArcGIS.GeoDatabase > Interfaces > IV > IVersionedObject3 Interface > IVersionedObject3.RegisterAsVersioned3 Method
ArcGIS Developer Help

IVersionedObject3.RegisterAsVersioned3 Method

Register this object as versioned with the option to move edits to base.

[Visual Basic .NET]
Public Sub RegisterAsVersioned3 ( _
    ByVal moveEditsToBase As Boolean _
public void RegisterAsVersioned3 (
    bool moveEditsToBase
HRESULT RegisterAsVersioned3(
  VARIANT_BOOL moveEditsToBase
moveEditsToBase [in]

moveEditsToBase is a parameter of type bool

Product Availability

Available with ArcGIS Engine, ArcGIS Desktop, and ArcGIS Server.


The RegisterAsVersioned3 method allows one to register an object as versioned with the ability of editing the data in both multiuser edit session modes. The MoveEditsToBase property can be set to true if the desire is push all saved edits to the base table when save is called. Whenever you save edits to the DEFAULT version, either by editing it directly or merging in changes from another version, the edits apply directly to the data source. With the MoveEditsToBase set to true the database is edited directly. The edits do not remain in delta tables as is the case when the data is registered as versioned with this property set to false. This allows for easy integration between ESRI applications and non-ESRI applications.

If it is the desire to enable archiving on the versioned object class it must be registered with the MoveEditsToBase property set to false. For more information on this see IArchivableObject::EnableArchiving.

Complex data such as Geometric Networks and Topologies do not support the moving of edits to base and for this reason they cannot be registered as versioned with the moving of edits to base.

Only the owner can register or unregister the object.

By programmatically registering a class participating in a geometric network as versioned it does not guarantee the entire geometric network including other participating classes will also be registered. It is then recommended the registration take place at the feature dataset level rather than on the individual feature class. This workflow is exposed by default through the user interface in ArcCatalog. If there is a need to register individual classes as versioned within a feature dataset without registering the entire dataset it is crucial the every class participating in a geometric network, including the geometric network itself, is explicitly registered individually.   

See Also

IVersionedObject3 Interface