Registers internal data in a cloned control.
Assembly: System.Design (in System.Design.dll)
Public Sub RegisterClone ( _ original As [%$TOPIC/ms153755_en-us_VS_110_1_0_0_0_0%], _ clone As [%$TOPIC/ms153755_en-us_VS_110_1_0_0_0_1%] _ )
public void RegisterClone( [%$TOPIC/ms153755_en-us_VS_110_1_0_1_0_0%] original, [%$TOPIC/ms153755_en-us_VS_110_1_0_1_0_1%] clone )
public: void RegisterClone( [%$TOPIC/ms153755_en-us_VS_110_1_0_2_0_0%]^ original, [%$TOPIC/ms153755_en-us_VS_110_1_0_2_0_1%]^ clone )
member RegisterClone : original:[%$TOPIC/ms153755_en-us_VS_110_1_0_3_0_0%] * clone:[%$TOPIC/ms153755_en-us_VS_110_1_0_3_0_1%] -> unit
public function RegisterClone( original : [%$TOPIC/ms153755_en-us_VS_110_1_0_4_0_0%], clone : [%$TOPIC/ms153755_en-us_VS_110_1_0_4_0_1%] )
Whenever an item is cloned, there might be some internal data structures, such as meta: attributes, that should be included in the cloned control by the control designer. A page developer might add meta: attributes to the markup of a control and there is no way, nor is there a reason, for the control to distinguish what those tags might be. Therefore, if your control designer provides a way to edit complex properties or formats before applying changes to a page, you would create a clone of the control, pass both the original control and the clone to this method, and then, when the changes are persisted to the tag, all meta: attributes are also persisted.