Managing VSPackages

Note

This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, use the version selector at the top left. We recommend upgrading to Visual Studio 2019. Download it here

In most cases you don’t need to worry about managing VSPackages, since the project and item templates register and load the package automatically. However, in some circumstances you may need to learn a bit more in order to manage your package.

Using the experimental instance

To find out more about the experimental instance, see The Experimental Instance.

Registering and Unregistering VSPackages

To find out how to register and unregister VSPackages and other types of extension, see Registering and Unregistering VSPackages.

Loading a VSPackage

VSPackages can be set to autoload when a particular CMDUICONTEXT GUID is turned on. For more information, see Loading VSPackages.

Using AsyncPackage to Load VSPackages in the Background

The AsyncPackage class enables package loading on a background thread for better UI responsiveness in Visual Studio. For more information, see How to: Use AsyncPackage to Load VSPackages in the Background.

Rule-based UI Context for Extensions

Rules-based UI Contexts allows extension authors to define the precise conditions under which a UI Context is activated and associated VSPackages loaded. For more information, see How to: Use Rule-based UI Context for Visual Studio Extensions.

Troubleshooting VSPackages

Find out the techniques for troubleshooting VSPackages that don’t load or are experiencing errors: Troubleshooting VSPackages

See Also

VSPackages