Extending Views

  • Article

View extensions, introduced in MMC 2.0, enable a snap-in to add user interface elements to an existing view or to create new views. View extensions use HTML to provide the user interface elements. The HTML can include script to use the MMC 2.0 Automation Object Model.

A snap-in developer can create new view extensions or use the Extended View extension to add view extensions to a snap-in. MMC 2.0 includes the Extended View as an extension that snap-in developers can use to provide a web-folder look and feel to their snap-ins.

A primary snap-in registers a view extension for any node type that is to contain view extensions. Be aware that this is different from the registration that takes place by other (non-view) extensions, which register themselves for the node types extended. Register the view extension entry in the following form:

HKEY_LOCAL_MACHINE\Software\Microsoft\MMC\NodeTypes\ {nodetypeGUID} Extensions View {viewextensionsnapinCLSID}

  • The {nodetypeGUID} key specifies the string representation of the globally unique identifier (GUID) of the node type that is extended. The string must begin with an open brace ({) and end with a close brace (}). There must also be a corresponding {nodetypeGUID} value in the primary snap-in HKEY_LOCAL_MACHINE\Software\Microsoft\MMC\SnapIns\{snapinCLSID}\NodeTypes key, where {snapinCLSID} is the string representation of the snap-in class identifier (CLSID).
  • The View key contains values that represent the CLSIDs of snap-ins that can extend the view of items with this node type.
  • The {viewextensionsnapinCLSID} key specifies the string representation of the CLSID of a view extension snap-in. The string must begin with an open brace ({) and end with a close brace (}).

For more information about extension registration, see Registration Requirements for Extension Snap-ins.

The following list contains topics that provide more information about view extensions and the Extended View extension:

View object