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

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 2013.

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

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

Note that the Edition names have changed in Visual Studio 2015; you can use "Enterprise" and "Pro".

Update References

In the VSIX manifest file, you must update the references to the proper OpenGAX version (note that the Id is now "OpenGAX-VS2015" and the Version is now "1.0"):

<Vsix>
  ...snip...
    <Reference Id="OpenGAX-VS2015" MinVersion="1.0">
      <Name>Guidance Automation Extensions</Name>
    </Reference>
    ...snip...

Declare VsPackage

Because of a change in the way VSIX packages are registered in Visual Studio 2012 and above, 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 Jul 24, 2015 at 10:16 AM by jelled, version 1

Comments

No comments yet.