The result can be anything from using an appropriate default to displaying a message about an exception.Įither of these symptoms can be caused by one or more of the issues listed below.

Your Visual Studio extension tries to retrieve a registry value it expected to be included in the install and does not find it.

All or part of a Visual Studio extension, such as a VS Package, simply fails to load or an error message is displayed about needing to reinstall Visual Studio.

pkgdef file usually manifests itself in one of two ways:

What Could Go Wrong?įirst of all, how do you know if something goes wrong? A problem with a. For other cases, substitute the appropriate file locations and names and registry root key. All of the examples assume the case of VS 2010 running on 32-bit Windows 7. Please note that these techniques apply not only to the Visual Studio 2010 IDE, but also to applications built using the Visual Studio 2010 Shell (Isolated) (or Integrated). pkgdef files and provides techniques for discovering what’s wrong and correcting them. This article illustrates some possible issues with.

However, like anything involving computers and software, there are occasions that require manual intervention because they aren’t covered by the automatic settings or things can go wrong. pkgdef files to be mostly automatic (see What’s a PkgDef and Why?). For those using the Visual Studio 2010 SDK to create extensions for Visual Studio, you should find the creation and use of.

Reinstall visual studio 2010 shell