There are a couple of things you need to in order to port an existing Guidance Package to work in Visual Studio 2012.

Upgrade Projects To .NET 4.5

Because the Guidance Automation Extensions rely on .NET 4.5, you must also change the target framework of your project(s) to .NET 4.5.

Update Supported Products

In the VSIX manifest file, you must update the supported products to target Visual Studio 2012.

This typically means editing your "source.extension.vsixmanifest" file to update the VisualStudio version from 10.0 to 11.0 as follows:

<Vsix>
  ...snip...
  <SupportedProducts>
    <VisualStudio Version="11.0">
    ...snip...

Declare VsPackage

Because of a change in the way VSIX packages are registered in Visual Studio 2012, you must explicitly mention the fact that there is a Visual Studio Package inside the VSIX by including it as a Content element in the VSIX manifest file. Otherwise, the VSIX will install just fine but appear not to work or simply doesn't show up anywhere inside Visual Studio.

This typically means editing your "source.extension.vsixmanifest" file to include the <VsPackage> element as follows:

<Vsix>
  ...snip...
  <Content>
    <VsPackage>|%CurrentProject%;PkgdefProjectOutputGroup|</VsPackage>
  </Content>
</Vsix>

Last edited Oct 4, 2012 at 1:38 PM by jelled, version 2

Comments

No comments yet.