Deploying Applications That Reference the Printer Compatibility Library

If you want to deploy an application that references the Printer compatibility library, the assembly that contains it must be installed on the destination computer.

Deploying the Printer Compatibility Library as a Prerequisite

To successfully deploy an application, you must also deploy all components or assemblies that are referenced by the application. The process of installing prerequisite components is known as bootstrapping.

When the Printer compatibility library is installed on your development computer, a Microsoft Visual Basic Power Packs bootstrapper package is added to the Visual Studio bootstrapper directory. This package is then available when you follow the procedures for adding prerequisites for either ClickOnce or Windows Installer deployment.

By default, bootstrapped components are deployed from the same location as the installation package. Alternatively, you can choose to deploy the components from a URL or file share location from which users can download them as necessary.


To install bootstrapped components, the user might need administrative or similar user permissions on the computer. For ClickOnce applications, this means that the user will need administrative permissions to install the application, regardless of the security level specified by the application. After the application is installed, the user can run the application without administrative permissions.

During installation, users will be prompted to install the Microsoft.VisualBasic.PowerPacks.Vs assembly if it is not present on the destination computer.

As an alternative to bootstrapping, you can pre-deploy the Microsoft.VisualBasic.PowerPacks.Vs assembly by using an electronic software distribution system like Microsoft Systems Management Server.

See Also


How to: Install Prerequisites in Windows Installer Deployment

How to: Install Prerequisites with a ClickOnce Application


Choosing a Deployment Strategy

Printer Compatibility Library