Visual Studio Development Bookmark and Share   
 index > Visual Studio Guidance Automation Toolkit > Guidance Package versioning
 

Guidance Package versioning

Hi All,

I have created a guidance package for one of our architecture. I would like to know how do I achieve versioning this guidance pakage

Ex. if the current guidance package is based on say 1.0 version of our architecture (it will allows guidance package consumers to build solutions based on 1.0 architecture).Later on there is another release of our architecture ex. 1.1 and we need to update Guidance package for the same.

Guidance package consumers should be able tosee both v1.0 and v1.1 and depending on their requirement they would decide which version to consume... ... is therea way this can be achieved in one guidance package where unfolding template(that maybe stored indirectoriesnamed by thier versionno.)can be done depeding on which version the developer/consumer has selected OR do i need to create copy of guidance package and change all thetemplates otherthings to create new guidance package ..Can you please let me know how this can be achieved?

Thanks in advance

Sachin

Sachin Ghag  Monday, December 17, 2007 9:09 AM
Hi Sachin,

Altough there is a version attribute in the <GuidancePackage> element for your package manifest file this is only used for display purposes (in the Guidance Package Manager dialog, etc). There is no versioning history support in GAX. If you have a new incremental version of your guidance package you will need create a brand new one with its own GUIDs and names, and there is no built-in support to go from one to the other.

HTH,
-Victor.
vga  Monday, December 17, 2007 3:36 PM
Hi Sachin,

Altough there is a version attribute in the <GuidancePackage> element for your package manifest file this is only used for display purposes (in the Guidance Package Manager dialog, etc). There is no versioning history support in GAX. If you have a new incremental version of your guidance package you will need create a brand new one with its own GUIDs and names, and there is no built-in support to go from one to the other.

HTH,
-Victor.
vga  Monday, December 17, 2007 3:36 PM

Thanks! Victor

Is it possible to have solution and project templates of new version to be stored in seperate directories and have project responsibilties definedwith version numbers?

In this case when the consumer first selects the solution template, we can identify which version of solution template was selected and later refer to only those templates with specific version

In this case i need not create brand new guidance package ..is this possible ? if yes, will this increase complexity later?

Thank you! once again

Sachin

Sachin Ghag  Tuesday, December 18, 2007 10:48 AM

You can use google to search for other answers

Custom Search

More Threads

• Custom developed Guidance Automation Package not listed under VisualStudio template
• WSSF
• error installing gaxp1409.exe
• C++ in GAX
• CAB - Open a View from another view that exists in another or in the same module
• Change the solution path
• June GAT Installation Issues
• Factoring Factories :)
• Can the debugger be used to step through a guidance package?
• Windows Installer XML project for GAT Package?