Guidance Automation Extensions and Toolkit: June 2006 Release  
Author Message
Tom Hollander





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

The patterns & practices team is please to announce the availability of the June 2006 CTP of the Guidance Automation Extensions (GAX) and Guidance Automation Toolkit (GAT)! As reported previously, this is a relatively minor update to the previous December 2005 CTP which includes some important bug fixes and usability improvements.

For more details on this release, please read the announcement on my blog.

Enjoy!

Tom Hollander
Product Manager
Microsoft patterns & practices



Visual Studio7  
 
 
envguy





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

I cannot install the extensions in Windows Vista Beta 2. It says Acess denied for the RecipieFramework assembly.

Does any body know how to fix that.


 
 
Tom Hollander





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Yes - we found the same problem. A solution for now is to start a command prompt as admin (i.e. choosing the "Run as Admin" option), and run the installer from the command prompt. The privilege escalation doesn't seem to work if you launch the installer from Explorer, even if your account is an admin account.

We're following up with the Vista team to figure out why this workaround is necessary - it may be a problem in Vista or it may be something to do with how our installer works.

Hope this helps

Tom


 
 
Tim Mercer





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Just wanted to say that I really like the new "Quick Register" ... _SO_ much faster (well, faster than deregister and register). Thanks to the dev team!

 
 
envguy





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

sorry for the late reply.

It fixed the problem with the installer. With Admin Command Line I'm able to fix the issues with CAB Installer also.

thanks


 
 
rbedard





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Might be "the obvious", but it caused problems for me...

Don't forget to delete all references to the old GAX/GAT DLLs in your Guidance Packages and their Installers, and re-reference the new DLLs... or you'll get some strange type-loading exceptions when trying to register the guidance package!


 
 
Tom Hollander





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

If you are having trouble unregistering any existing guidance packages (which must be done before you can uninstall the old GAX and install the new one), here are some tips that may help:

First try to uninstall all guidance packages cleanly:

  1. If they were installed through an MSI, try to remove it using Add/Remove Programs.
  2. If they were installed using code, open the solution and run GAT’s Unregister recipe

Make sure you do not uninstall GAT until all code-registered packages have been removed!

If there are packages that cannot be removed, here is how to remove them manually:

  1. Open C:\Documents and Settings\All Users\Application Data\Microsoft\Recipe Framework\ReceipeFramework.xml
  2. Remove any or all of the <GuidancePackage> elements from the file (actually it’s a good idea to paste them into another window so you know which packages you have to clean out of the registry), and save the file
  3. Open the registry and look for the following keys under HKLM\Software\Microsoft\VisualStudio\8.0
    • Packages\{77d93a80-73fc-40f8-87db-acd3482964b2}\Templates : Delete all subkeys that refer to guidance packages you don’t want any more (they will have GUIDs as their key names)
    • Languages\CodeExpansions\CSharp\Paths : Delete all values that refer to guidance packages you don’t want any more
    • Menus : Delete all values that refer to guidance packages you don’t want any more (they will probably be at the bottom after all the ones named after GUIDs)
    • NewProjectTemplates\TemplateDirs : Expand each of the subkeys (they will have GUIDs as names) and expand the /1 key below that. If you find one whose (Default) value is named after an unwanted guidance package, delete the entire GUID key and the /1 key below that.
  4. If any of the guidance packages you removed manually were installed from an MSI, run msizap to clean up the MSI-related registry settings.

 
 
yenpei





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Hi Tom, by the way, how do I run the GAT unregister recipe When I registered GAT SmartClientDevelopment package, I remember it was done by right-clicking the solution and "Register", but now, in the solution I don't see "Unregister" menu item.
 
 
vga





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Hi yenpei,

do you see a "Register" but not an "Unregister" one Make sure GAT is enabled for the solution you're trying to register/unregister a package (go to Tools->Guidance Package Manager and enable GAT).



 
 
cvalstonzzz





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Hi there,


I am having install problems. To download the webservices software factory (WSF) you need to download the june 2006 CTP GAX which you can find here:

http://go.microsoft.com/fwlink/ LinkId=47181

When I download the msi and run it even as an admin on my Vista box, the screen says its a February 2007 CTP. It installs fine but, when I run the WSF Decememer 2006 CTP I get an error that says,

"This installer requires the GAX June 2006 CTP which is not present on the computer. Please install it and try again."

Any idea whats going on

Thanks!

Carlos


 
 
Tom Hollander





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Hi Carlos -

I just answered the same question at http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1267386&SiteID=1

The short answer is that you will need to redownload the Service Factory from MSDN to get it working with the February CTP of GAX, since we made a fix to the MSI.

Tom


 
 
Manuel5





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Hi,

after uninstall guidance automation extensions and toolkit and web service software factory december refresh and install new versions of these packages, I open a wcf guidace package proyect and it doesnt find some references like

Microsoft.Practices.Common;

Microsoft.Practices.RecipeFramework.Services;

Microsoft.Practices.RecipeFramework.Configuration;

Microsoft.Practices.ComponentModel;

why

Thanks


 
 
Tom Hollander





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Your code may be referencing the older version of the assemblies. You can fix this by deleting the references and adding them to point to the new assemblies.

Tom


 
 
Manuel5





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

Hi, thanks
now it compiles fine but when I try to register the WCF Guidance Package it
fails with this message:
An exception ocurred during the binding of reference or execution of recipe Register.
Error was: Action Register failed to execute: Failed to process package.


 
 
Manuel5





PostPosted: Visual Studio Guidance Automation Toolkit, Guidance Automation Extensions and Toolkit: June 2006 Release Top

I try now to make a setup file (register fails) to install de package and fails with this error:
Package configuration file c:\programa files\......\WCFTooling.xml doesn’t existe.
WCFTooling is the name of the hol buy I dont use this name.