I am
trying to debug a managed package load failure - the package worked for
a while, I reinstalled VSIP (Visual Studio 2005 SDK Dec 05) and now I
cannot get it to load. The package was originally created with the same
version of the SDK that I was reinstalling (Dec 05). I am using the
experimental hive and not using a PLK.
The package appears to be
registered correctly: I have tried both using a .reg file (produced via
regpkg) and regpkg to register the package. Both succeed without
errors. The registry looks fine: my package lives where it should (in
the 8.0Exp hive). No matter what I try I cannot get it to load or find
out why it is not loading.
When I do the following:
'devenv /rootsuffix exp /setup /log'
...I at least see the following entries at the end of the ActivityLog.xml:
[#] ERROR Loading UI library
{7DB7E0F5-380E-4AAB-ACB7-3F8E55BD0145} 800a006f Microsoft Visual Studio [timestamp]
[#] ERROR Loading UI library
{FCAD544A-E623-49C0-8180-DF8554A3AA59} 800a006f Microsoft Visual Studio [timestamp]
The
{7DB7E....145} GUID is the GUID for the 'Navigation Window Package';
the other GUID is the GUID for the package I am trying to load.
I
have code in my Initialize method that logs information via
IVsActivityLog but of course this is not being executed. The package is
pretty much stock wizard goop (it was used for simple testing of
another package) so it is not doing anything except what the VSIP
managed package wizard added - Tools menu item, Tool Window, and custom
Editor Factory.
When I run 'devenv /rootsuffix exp' the
ActivityLog.xml shows no trace of my package; however, if I make a new
project using the wizard the new package loads just fine using all of the
same settings.
How can I figure out what is failing here Is there an easy way to debug this

Trying to load managed package results in error 0x800a006f in ActivityLog
Rosdol
I also tried using FUSLOGVW.exe (the Assembly Binding Log Viewer) to see if there were any relevant entries - there were not. I have 'Log all Binds to Disk' turned on.
paulorlowski
Hi Cappy,
Since your package is very similar to the one generated from the wizard, you may want to generate a new one from the wizard and diff the 2 (or transfer the functionality to the new one). This should help you detect any change that may be causing problems.
The next thing to do would be to reset the experimental hive in case left over registry entries is what is causing the problem. When installing the VS SDK, you should have an entry to do that in:
Start-->All Programs-->Visual Studio 2005 SDK-->200x-xx-->Reset The Visual Studio 2005 Experimental hive
(where x are numbers such as 2006-02)
I hope this helps
Rusty