Your VS Package may not load after porting it to VS 2012

With VS 2010, the IDE recreates the user’s 10.0_Config registry hive and remerges menu resources when it detects a change under HKLM\Software\Microsoft\VisualStudio\10.0. For VS 2012, the IDE team felt this had too much of a negative effect on startup performance, and the feature was removed. Consequently, if you deploy your VS Package(s) with a custom…

0

Sample Browser Extension for Visual Studio 2010/2012

3500+ samples at your fingertips. The new Sample Browser Extension allows you to quickly search, download, and experiment with sample code covering just about anything you can think of. And if you can’t find what you’re looking for, you can submit a sample request. The latest version, which supports both VS 2010 and VS 2012,…

0

Visual Studio 2010 Professional Upgrade Pre-Order

Microsoft Visual Studio 2010 Professional will launch on April 12 but you can beat the rush and secure your copy today by pre-ordering at the affordable estimated retail price of $549, a saving of $250. If you use a previous version of Visual Studio or any other development tool then you are eligible for this…

0

How to register existing packages to run under VS 2010 Experimental Instance

Aaron Marten’s blog “Pkgdef and the Experimental Instance in VS 2010” points out that when devenv.exe is invoked with the ‘/rootsuffix Exp’ switch, the VS Shell no longer uses the experimental registry hive. Instead, the shell merges the HKLM\Software\Microsoft\VisualStudio\10.0 registry settings and the .pkgdef files in the user’s …AppData\Local\Microsoft\VisualStudio\10.0Exp\Extensions folder. If you have an existing…

2

How to create a pkgdef file for your Visual Studio Package

The .pkgdef file was first introduced with VS 2008, to allow for easily registering packages targeting the VS 2008 isolated shell. Bill Wienberger details the rationale behind this change in the following blog entry: What’s A PkgDef? And Why? There are a couple of ways .pkgdef files can be created. For a managed package, the…

0

Dissecting VS 2010 Package Registration

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 now uses pkgdef and vsixmanifest files to integrate custom packages into the shell. For…

0

Hotfix posted for VS 2010 RC1 Intellisense crash

On systems where an application or device is actively using UIAutomation (Tablet, Multi-touch, etc), the IDE may crash if the user is typing while intellisense is being displayed or dismissed. KB article describing this problem will be posted to http://support.microsoft.com/default.aspx?scid=kb;EN-US;980615 in the next few days. A hotfix that addresses this problem can be downloaded from…

0

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