Migrating VSPackages to Visual Studio 2005

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

If you have to develop for multiple versions of Visual Studio, you need side-by-side installations of each version of Visual Studio on your workstation. After you install the Visual Studio SDK for each version of Visual Studio, you will have additional experimental registry hives.

NoteNote

Be aware of which registry hive is being used when you work with VSPackages. You can use the VsRegEx tool to copy information from one registry hive to another. For more information, see Experimental Build.

This topic discusses compatibility of existing VSPackages with Visual Studio 2005 and the Visual Studio 2005 SDK. There are four facets. 

  • Binary compatibility for managed VSPackages.

  • Binary compatibility for unmanaged VSPackages.

  • Source-code compatibility for managed VSPackages.

  • Source-code compatibility for unmanaged VSPackages.

    NoteNote

    Any Package Load Key (PLK) created for Visual Studio .NET 2003 is also valid for Visual Studio 2005.

Binary Compatibility

Unmanaged VSPackages are binary-compatible with Visual Studio 2005. If your VSPackage installer uses self-registration, you must recompile your VSPackage to register itself under the HKLM\Software\Microsoft\VisualStudio\8.0 registry root.

Managed VSPackages are also binary-compatible with Visual Studio 2005, but additional deployment work is required because support for managed VSPackages is included with Visual Studio 2005. Previously, it required the redistributable interop assemblies supplied with VSIP SDK Extras 2003.

  • As with unmanaged VSPackages, you must register your managed VSPackages under the HKLM\Software\Microsoft\VisualStudio\8.0 registry root.

  • If your managed VSPackages use the VSIP helper classes, you must continue to release Microsoft.VisualStudio.VSIP.Helper.dll. The .dll file should be installed in the same directory as your VSPackage. The managed package framework (MPF) in Visual Studio 2005 SDK replaces the VSIP helper classes.

Source Compatibility

Unmanaged VSPackages are highly source-compatible with Visual Studio 2005 SDK.

  • Changes to the C++ compiler and libraries might require code changes.

  • When you link with HierUtil7.lib, you must also link with unilibS.lib.

  • If your VSPackage installer uses self-registration, you must recompile your VSPackage to register itself under the HKLM\Software\Microsoft\VisualStudio\8.0 registry root.

Managed VSPackages that use the VSIP helper classes in VSIP SDK Extras 2003 require modification so that they can be recompiled by using MPF in Visual Studio 2005 SDK.

NoteNote

The required modifications are not backward compatible with the VSIP helper classes.

For more information, see How to: Migrate Managed VSPackage Source Code.

See Also

Community Additions

ADD
Show: