Managed VSPackage Registration Keys

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

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. See VSPackage Load Keys for more information.

• 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 2008 for which the VSPackage is written. See VSPackage Load Keys for more information.

• MinEdition
  This value identifies the minimum edition of Visual Studio 2008 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 the Visual Studio 2008 environment 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 2008 can find the VSPackage assembly DLL. If the CodeBase value is not specified, the assembly must be located where Visual Studio 2008 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.

See Also

Concepts

Loading VSPackages

Other Resources

Managed VSPackages

Creating and Using Strong-Named Assemblies

Registering VSPackages (C#)