This documentation is archived and is not being maintained.

Managed VSPackage Registration Keys

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

The registry keys and values described in the table below are required to load a managed VSPackage.


The CompanyName, ProductName, ProductVersion, and MinEdition values should match the values specified when you requested your Package Load Key.

Registry Keys

Registry Key

The registry key should be the resource identifier of the Package Load Key (PLK). The resource identifier should be the same as the one specified in the resource DLL.


All managed packages are registered as a fully qualified path to mscoree.dll.


This string value identifies the developer of the VSPackage.


This string value identifies the VSPackage.


This value identifies the version of Visual Studio for which the VSPackage is written. For Microsoft Visual Studio 2005, the ProductVersion is "8.0".


This value identifies the minimum edition of Visual Studio required to load the VSPackage. Acceptable values are "standard" and "professional". With any other value, the VSPackage will install on all editions of Visual Studio.


This value names the class that the VSPackage implements. The class name must be fully qualified. When the Visual Studio environment loads the assembly, this is the class that it will try to invoke.


This optional value specifies the fully qualified file path in which Visual Studio can find the VSPackage assembly DLL. If the CodeBase value is not specified, the assembly must be located where Visual Studio can find it (see Managed VSPackage File Location Keys.)


This optional value specifies a strong-named assembly. A strong name consists of the assembly's identity—its simple text name, version number, and culture information (if provided)—plus a public key and a digital signature.


Your package should be registered with a CodeBase key or an Assembly key, but not with both.

See Also