VSPackages and Deployment

This page is specific to Microsoft Visual Studio 2008/.NET Framework 3.5. Other versions are also available for the following: Microsoft Visual Studio 2005/.NET Framework 2.0.

VSPackages are software modules that make up and extend the Visual Studio integrated development environment (IDE) by providing UI elements, services, projects, editors, and designers. VSPackages are the principal architectural unit of Visual Studio, and are the unit of deployment, licensing, and security also. Visual Studio itself is written mostly as a collection of VSPackages.

To create a Visual Studio extensibility application, you would first create a VSPackage. You can then add menu commands, tool windows, document windows, or other code to extend the Visual Studio IDE. When the VSPackage is ready to be deployed, you must obtain and install a package load key (PLK).

• VSPackages have a state that is determined by property pages, settings, and other means.

• VSPackages can advertise on the About dialog box and splash screens of Visual Studio.

• Each VSPackage has a unique package load key (PLK). Visual Studio only loads a VSpackage that has a valid PLK.

MSDN Library Topics

• How to: Create VSPackages (C# and Visual Basic)
  
• How to: Register a VSPackage (C#)
  
• How to: Troubleshoot VSPackages
  
• How to: Write to the Activity Log (C#)
  
• Loading VSPackages
  
• How to: Autoload a VSPackage (C#)
  
• How to: Force a VSPackage to Load
  
• VSPackage Load Failure Analyzer
  
• VSPackage State
  
• VSPackage Branding
  
• Branding Overview
  
• How to: Brand a VSPackage (C#)
  
• How to: Brand a VSPackage (C++)
  
• How to: Test the Help About and Splash Screens
  
• VSPackage Load Keys
  
• How to: Obtain a PLK for a VSPackage
  
• How to: Add a PLK to a VSPackage Project (C#)
  
• How to: Troubleshoot a PLK Load Failure
  
• VSPackage Architecture
  
• Implementing the IVsPackage Interface
  
• Managed VSPackages
  
• Registering VSPackages (C#)
  
• Best Practices for Security in VSPackages