While it’s still possible to register your packages, by manually or programmatically adding the requisite registry keys and values under the HKLM\Software\Microsoft\VisualStudio\10.0 registry hive, it’s no longer the recommended way to register your packages with the integrated (or isolated) shell. VS2010...

Background: Recently one of our VSIP partners asked if it was possible to customize the default error dialog that the Isolated Shell displays when encountering an error. Let's suppose you have a package command handler that might throw an error with code that looks like the following: private...

Background: VSPackages can offer up a set of custom properties for their Tools.Options pages, by registering the pages under Visual Studio's AutomationProperties registry key, by using the ProvideOptionPageAttribute . This allows for programmatic access to the Tools.Options properties via DTE.Properties...

Background: The PcwTESample project, is a sample which illustrates how to extend the Team Explorer tool window, and upload customized Team Projects to TFS. It is installed with the Visual Studio 2008 SDK under the ...\ VisualStudioTeamSystemIntegration\Team Explorer and Project Creation subdirectory...

Background: Historically , localized resources for Visual Studio packages were located in native satellite resource DLLs, located in a codepage subdirectory. For example, if you had installed both the English and Japanese versions of Visual Studio on the same system, you would find some of these...