Guidance packages developed using Guidance Automation Extensions (GAX) 2010 (this includes all software factories from p&p, like the Web Services Software Factory) will not run or build against the new open source GAX.

While no source code changes have been introduced in the open source GAX -meaning it is currently source code compatible with GAX 2010- the new open source GAX assemblies are not signed by Microsoft and won’t have a strong name unless you update the projects to use your own key. This means you will have to make sure your guidance package source code is modified to not include any references to GAX 2010 assemblies. You should make sure to perform the following steps:

Update Assembly References

All assembly file references to GAX 2010 assemblies must be updated to now point to the DLLs for the Open Source GAX.

If your guidance package is referencing assemblies that were previously built against the GAX 2010 assemblies, you will need to recompile these assemblies using the new open source GAX ones. An example for this is software factories using the GEL project (http://gel.codeplex.com/) which was built against GAX 2010.

Update Public Key References

All references to the Microsoft public key token “31bf3856ad364e35” must be updated to point to “null” or a new public key token if you are signing the assemblies. One place where you will find this is in .vstemplate files containing a Wizard Extension because these reference a GAX 2010 assembly using its strong name, for example:

<WizardExtension>
    <Assembly>Microsoft.Practices.RecipeFramework.VisualStudio, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35</Assembly>
    <FullClassName>Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate</FullClassName>
</WizardExtension>

This can simply be replaced by the following:

<WizardExtension>
    <Assembly>Microsoft.Practices.RecipeFramework.VisualStudio</Assembly>
    <FullClassName>Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate</FullClassName>
</WizardExtension>

Update VSIX References

In the VSIX manifest file, you must update the reference to GAX from the previous VSIX ID to the new open source ID.

Old VSIX ID New VSIX ID
Microsoft.Practices.RecipeFramework.VisualStudio OpenGAX
Microsoft.Practices.RecipeFramework.MetaGuidancePackage OpenGAT


This typically means editing your "source.extension.vsixmanifest" file to update the replace the following reference:
    <Reference Id="Microsoft.Practices.RecipeFramework.VisualStudio" MinVersion="2.0">

With the new Id "OpenGAX"
    <Reference Id="OpenGAX" MinVersion="3.0">

Last edited Oct 4, 2012 at 3:04 PM by jelled, version 4

Comments

No comments yet.