After you have coded and tested your snap-in, you are ready to deliver it to your end users. This means that you need to:
- Gather the files required for your snap-in (create a package).
- Save the files to some medium for distribution (deploy the snap-in).
- Provide some way for end users to install the snap-in on their local systems.
There are three primary setup technologies you can use to distribute your snap-ins to end users:
- Microsoft Windows Installer
Prepares and deploys packages for computers running Windows 95 or later and Windows NT 4.0 or later. It includes the ability to create installer-based setups on any 32-bit Windows operating system.
- Microsoft Visual Basic Package and Deployment Wizard
Prepares packages and deploys packages for application programs using the Visual Basic programming system. It includes the creation of installer programs to copy application programs including the Visual Basic programming system—in this case snap-ins—onto the users' computers.
- Proprietary or third-party installation package
You may choose to use a third-party installation program or write your own scripts to package, deploy, and install snap-ins.
The following sections provide details about using these methods with snap-ins as well as special concerns about distributing saved console files.
- Using Windows Installer
- Using the Package and Deployment Wizard
- Using a Proprietary or Third-Party Installation Package