Manually Unregistering a Guidance package

For manually unregister a guidance package we need to know two things:

1. PackageName
2. PackageGUID

This information is located at the guidance package manifest file:

 

 

Once we know this information, these are the steps that we need to perform:

 

• Remove the guidance package entry from the recipe framework manifest
  • Go to C:\Documents and Settings\All Users\Application Data\Microsoft\Recipe Framework\RecipeFramework.xml
  • Delete the guidance package entry from the manifest using the PackageName

 

• Remove registry entries
  • Open windows registry editor
  • Delete the following keys:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\AutoLoadPackages\<PackageGUID>
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Menus\<PackageName>
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\NewProjectTemplates\PseudoFolders\<PackageGUID>
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\NewProjectTemplates\TemplateDirs\<PackageGUID>
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Languages\CodeExpansions\<LANGUAGE>\Paths\<PackageName>
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Packages\<PackageGUID>
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Projects\<PackageGUID>

 

Pablo

posted Friday, October 13, 2006 11:05 AM by pga with 4 Comments

VS Custom Tool file’s association

Kzu has an excellent post o how to create a custom tool. One thing that I want to add to that post is that there is a new feature of Visual Studio 2005 that allows us to associate a file extension to a custom tool.

This means that every time we add a new item to a solution with a particular extension the custom tool will be automatically associated with the item, instead of manually adding the association via the properties window.

 

Steps:

• Open the window registry
• Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Generators\<Language>

Where <Language> is:

{164b10b9-b200-11d0-8c61-00a0c91e29d5} for VBnet

{e6fdf8b0-f3d1-11d4-8576-0002a516ece8} for J#

{fae04ec1-301f-11d3-bf4b-00c04f79efbc} for C#

 

• Define a new Key with extension to associate (you must prefix the extension with a “.”)

Example: “.foo”

 

• Specify the data for the default value of that key to the name of the key of the custom tool

When we add a New Item with the ".foo" extension Visual Studio automatically associates the custom tool with it.

 

Pablo

posted Friday, October 13, 2006 8:17 AM by pga with 0 Comments

Recipe CommandBar icons

If we take a look at the xsd schema for the recipe definition (located at C:\Program Files\Microsoft Visual Studio 8\Xml\Schemas\ GuidancePackageConfig.xml), the icon element of the HostData section consists of a GUID or an ID or a File.

The xsd schema documentation for the ID saids:

“The ID number of the icon in a DLL specified by the Guid attribute, if present. If no GUID is supplied, the ID attribute specifies an icon in the Microsoft Office library by default.”

 

The question is how we can browse icons and the corresponding ids.

 

The answer is FaceId Browser :

 

 

 

Using this tool or a similar one you can browse the icon and the corresponding id for the entire Microsoft Office library.

 

 

Pablo

posted Friday, October 13, 2006 7:47 AM by pga with 1 Comments