The Snap-In wizard consists of two pages. The first page allows the user to enter the common name of the snap-in object. From this string, the remaining names of the various objects and files are generated. It is recommended that you use the default naming convention.
The second page is more complex because there are a variety of optional elements that can be included in a snap-in object. The page is divided into three parts:
Determines if the new snap-in will be an extension of an existing snap-in and, if so, the name of the snap-in to be extended. Snap-in extensions can be of many types, from additional commands or buttons to a new node type. The extended snap-in must exist on the development machine. By default, the snap-in is not an extension.
Determines the interfaces supported by the snap-in object. These interfaces include:
Allows communication between the MMC console and items in the scope pane. Supported by default.
Allows communication between the MMC console and items in the result pane. Supported by default.
Enables the MMC console to get version and copyright information from the snap-in object. Supported by default.
Allows extension (customization) of the snap-in context menu. Not supported by default.
Allows extension (customization) of the snap-in property sheet (or sheets). Not supported by default.
Allows extension (customization) of the snap-in control bar. Not supported by default.
Determines the type of persistence used by the snap-in object: storage, stream, or an initialized stream. By default, the snap-in uses storage persistence.
For more information on the effects of various options on the generated snap-in object, see Effects of Options on the Generated Files.