Problems building VS 2008 SDKSample

Recently, one of our partners had a question pertaining to Help 2.0 integration, and I wanted to use the SDKSample to try a few things out with filters and help content. Apparently, it’s been a while since I last played with that particular sample. Upon attempting to build it, I was confronted with the following…

0

Replacing the Default Error Dialog in the Isolated Shell

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 void OnTestErrorDialog(object sender, EventArgs e)        …

0

Macro that tests for proper implementation of AutomationProperties

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(<categoryName>, <pageName>). The Example.OptionsPage sample in the Visual Studio SDK is missing the following attributes on its…

0

PcwTESample for VS 2008

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. The PcwTESample that currently ships with the Visual Studio SDK for VS 2008…

0

Useful Macros

Background: I always have a difficult time remembering the various properties that can be set on an EnvDTE.Project object, and I never seem to find the right documentation, to jog my memory.  Over the years the documentation has improved quite a bit. However, I still found that certain aspects of the VS automation model are…

0

How to push F1 context keywords for property pages in the project designer?

Background: IPropertyPage.Help is not invoked on property pages integrated with the Application Designer. Consequently, you need to push an F1 keyword by calling IHelpService.AddContextAttribute, similar to what the VB .NET and C# project property pages do. Solution: Using the IronPython Integration sample as a test bed for illustration purposes, you can push an F1 context…

1

How to localize a managed VS Package

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 native satellite DLLs under C:\Program Files\Microsoft\Visual Studio 9.0\Common7\Packages\1033 and C:\Program…

3

Where can I get assistance with my Visual Studio Extensibility issue?

There are a good number of support options available for developers with questions and/or problems pertaining to extending or automating the Visual Studio development environment. Be it macro programming, COM automation, Add-in development, custom project and item wizards, or authoring packages with the Visual Studio SDK. First the free stuff: The MSDN Visual Studio Extensibility…

0