I have been working on a GAT (Dec 2005 CTP) package for the last month and have gone through many interations of register, test, repeat. Now I am at the point of testing the setup msi. The developers that are testing the package have VS.NET 2005 and GAX Dec 2005 CTP installed. Is there anything else that needs to be installed on their machines? The install finishes and I can enable the package. The recipes show in the Guidance Package Manager (GPM). The are unbound and set to appear when

<CommandBar Name="Folder" />

The manifest is read correctly as I see the Caption and Description in the GPM and the UnboundRecipeReference-derived class' AppliesTo property is called as this shows up in GPM as well. When I right-click on a folder in my project, no menu items appear. I have set a breakpoint in the IsEnabledFor method of the UnboundRecipeReference-derived class but it doesn't get called. I also set the debugger to break on all exceptions thrown, but nothing. It appears to be a bug in the GAX code that is called before the UnboundRecipeReference-derived class is called. I can successfully execute the recipe from GPM, but not get the menu items to appear.

What else can be done to debug this issue? What is required for a GAT package to execute when installed my the msi and not registered in VS?

Mark

I figured out what it was: a comma. Both the Register and the msi call installutil.exe on the MyPackageInstaller.dll. When done in VS.NET, the path is that of the project. When done from the msi, it uses the install path. When the Guidance Package solution and the Setup project were created it autofilled the Manufacturer name as my company's name with ", Inc". That then became the default path for the installer. When the msi calls installutil.exe and a comma is in the path then the installation continues without indication of a problem but in actuality a part of the install does not finish. The result is a package that shows up in GPM, but no menu items.

Thanks for your willingness to help out.

Mark

Can you post the reference code and the binding recipe too?
Are you clicking on a project folder and NOT on a solution folder? 'cause the two have different command bars.

The package does not need anything other than GAX and GAT to run when installed with the MSI. Are you seeing a problem there too?

On my box, I have both GAX and GAT. Other developers consuming the package only have GAX. What is needed to run a Guidance Package? Just GAX or both GAX and GAT?

I know that my recipes are working for project folders as I have tested them on my box using "Register Guidance Package". The problem is that when the package is installed from the msi, the menu items don't appear. Other boxes with just GAX, don't show the menu items but the recipe can still be executed from GPM. On my box, if I "Unregister Guidance Package" and then install the package with the msi then the menus don't appear, but I can execute the recipe from GPM.

Apparently, "Register Guidance Package" does something that the msi fails to do so that the menus don't show.

Mark

I figured out what it was: a comma. Both the Register and the msi call installutil.exe on the MyPackageInstaller.dll. When done in VS.NET, the path is that of the project. When done from the msi, it uses the install path. When the Guidance Package solution and the Setup project were created it autofilled the Manufacturer name as my company's name with ", Inc". That then became the default path for the installer. When the msi calls installutil.exe and a comma is in the path then the installation continues without indication of a problem but in actuality a part of the install does not finish. The result is a package that shows up in GPM, but no menu items.

Thanks for your willingness to help out.

Mark