Managed VSPackage Registration Keys
The registry keys and values described in the table below are required to load a managed VSPackage.
Note
|
|---|
|
The CompanyName, ProductName, ProductVersion, and MinEdition values should match the values specified when you requested your Package Load Key. |
- Registry Key
-
The registry key is deprecated.
- InprocServer32
-
All managed packages are registered as a fully qualified path to mscoree.dll.
- CompanyName
-
This string value identifies the developer of the VSPackage. See VSPackage Load Keys for more information.
- ProductName
-
This string value identifies the VSPackage. See VSPackage Load Keys for more information.
- ProductVersion
-
This string value identifies the version of Visual Studio for which the VSPackage is written. See VSPackage Load Keys for more information.
- MinEdition
-
This value identifies the minimum edition of Visual Studio required to load the VSPackage. See VSPackage Load Keys for more information.
- Class
-
This value names the class that the VSPackage implements. The class name must be fully qualified. When Visual Studio loads the assembly, this is the class that it will try to invoke.
- CodeBase
-
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.)
- Assembly
-
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.
Note
Your package should be registered with a CodeBase key or an Assembly key, but not with both.