This page is specific to

Microsoft Visual Studio 2005/.NET Framework 2.0

Other versions are also available for the following:

Visual Studio SDK

VSPackage Load Keys

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

To prevent unauthenticated VSPackages from running in Visual Studio, each VSPackage to be loaded in a deployed application must have a valid package load key (PLK).

The Visual Studio SDK provides a developer load key (DLK) that makes it possible for VSPackages to load without a PLK during development.

In This Section

PLKs and the DLK: Introduces PLKs and discusses security issues.

How to: Obtain a PLK: Explains how to obtain a PLK for VSPackages that you want to deploy.

How to: Install a PLK (C#): Explains how to install a PLK in a VSPackage that you want to deploy.

How to: Troubleshoot a PLK Load Failure: Contains guidance about how to resolve PLK load failures.

Related Sections

Reference.Package Sample (C#): Shows how to use managed code to attach a PLK to a VSPackage.

Reference.Package Sample (C++): Shows how to use unmanaged code to attach a PLK to a VSPackage.

Releasing a Visual Studio Integration Product: Discusses how to prepare a VSPackage for final deployment.

VSPackages: VSPackages extend the IDE by providing UI elements, services, projects, editors, and designers.