Manually unregistering a guidance package

The other day I was experimenting with the guidance automation toolkit to build a new guidance package for visual studio. It all works kind of good, however if you change the name of the guidance package you got some real problems on your hands.

After renaming the guidance package you are no longer able to unregister or register the package in visual studio and you need to manually remove the packge from the registry. It's messy, but it does the job. Pablo Galiano wrote an excellent post on how to do this:

http://www.clariusconsulting.net/blogs/pga/archive/2006/10/13/4522.aspx