Modifying the Guidance Package
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies.
You can modify the existing guidance package, or create new guidance packages, to customize the Web Client Software Factory. You use Visual Studio and the Guidance Automation Toolkit to modify and create guidance packages. To download the Guidance Automation Toolkit, see Guidance Automation 2010.
This section includes development tips for modifying a guidance package.
Change the Guidance Package Identifiers for Your Custom Version
The Name and Guid attributes in the guidance package configuration file WebClientFactoryPackage.xml uniquely identify the guidance package. If you do not change these identifiers, your custom version will replace the original guidance package when you install your custom guidance package. It is recommended that you also change the Caption and Description attributes.
<GuidancePackage xmlns="http://schemas.microsoft.com/pag/gax-core" Name="CustomRecipesWebClientDevelopment" Caption="Custom Web Client Development" Description="Custom Web Client Development" Guid="1FECA063-21D2-4f54-A9B4-B79BC59E2665" BindingRecipe="BindingRecipe" SchemaVersion="1.0">
Use the Export Template Feature of Visual Studio to Create or Update Your Templates
When you create a template, create your project or item in Visual Studio and then export the project (or item) as a template. To update an existing template, you should also consider modifying the original source project in Visual Studio and then exporting it again. When you do this, you can use Visual Studio to verify your syntax.
|Note: The Build Action property for the template code in the Web Client Software Factory 2010 guidance package solution is Content. This means that the template code is not compiled, and when you build your guidance package, Visual Studio will not report syntax errors in your template code. |
If you add new template files to your guidance package, for each new file, you must set the Build Action property to Content and set the Copy to Output Directory property to Copy if newer.
Update Your Templates to Associate the Recipe Framework
The Visual Studio templates you create for use with the recipe framework contain additional information when compared with the templates normally used by Visual Studio. You must add the following XML to your project's .vstemplate file to transform the template into a Guidance Automation Toolkit solution template.
<WizardExtension> <Assembly>Microsoft.Practices.RecipeFramework.VisualStudio, Version=22.214.171.124, Culture=neutral, PublicKeyToken= 31bf3856ad364e35</Assembly> <FullClassName>Microsoft.Practices.RecipeFramework.VisualStudio.Templates.UnfoldTemplate</FullClassName> </WizardExtension>
Bind Your Guidance Package After You Modify the Binding Recipe
The Web Client Software Factory 2010 guidance package contains a binding recipe named BindingRecipe. If you change the binding recipe, you must re-execute the binding recipe in your solution. To do this for existing solutions, disable and then re-enable the guidance package. When you do this, the Guidance Automation Extensions will execute the binding recipe.
Creating and Installing a VSIX File
To distribute a guidance package, you create and distribute a VSIX file. To create a VSIX file, just build the Guidance package solution that you want to modify. Go to the \bin\Debug or \bin\Release folder (depending on configuration chosen while building) and you will find the VSIX file. Users will just need to double click the VSIX to install it.