Udostępnij za pośrednictwem

Deploying Applications That Reference Power Packs Controls

  • Artykuł

If you want to deploy an application that references the Power Packs controls (LineShape, OvalShape, RectangleShape, or DataRepeater), the controls must be installed on the destination computer.

Installing the Power Packs Controls as a Prerequisite

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

When Visual Studio is installed on your development computer, a 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.

Note

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 Power Packs controls if they are not present on the destination computer.

As an alternative to bootstrapping, you can pre-deploy the Power Packs controls by using an electronic software distribution system such as Microsoft Systems Management Server.

See Also

Tasks

How to: Install Prerequisites in Windows Installer Deployment

How to: Install Prerequisites with a ClickOnce Application

Concepts

Choosing a Deployment Strategy

Other Resources

Visual Basic Power Packs Controls

Change History

Date

History

Reason

July 2008

Added topic.

SP1 feature change.