Can someone please tell me why Word does not tell you why an AddIn fails to load I can understand that Word 97 when it was new might have missed something so critically obvious to anyone who ever wrote an AddIn. But Word 2003 This strikes me as totally brain dead.

Yes I know VSTO eliminates some/all of this - but we have to support back to Word 2000 so that doesn't help us. Plus based on what a couple of people on the VSTO team told me, it should not be used for a commercial AddIn.

Ok, it's been about 3 weeks so time for this problem again. This time it's on my development machine. It was running my AddIn fine when I launched the debugger and now it doesn't. How do I figure out what is wrong

  1. It is not in the disabled items list.
  2. I set security to medium so even if the signing is off it should run.
  3. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Word\Addins\AutoTag2003.Connect has LoadBehavior = 2
  4. HKEY_CLASSES_ROOT\AutoTag2003.Connect = AutoTag2003.Connect and has a CLSID subkey (see item 5)
  5. HKEY_CLASSES_ROOT\CLSID\{C40E71F6-B50C-45F8-ACC9-97C9A8CB3BB6} = AutoTag2003.Connect
  6. HKEY_CLASSES_ROOT\CLSID\{C40E71F6-B50C-45F8-ACC9-97C9A8CB3BB6}\InprocServer32 CodeBase=file:///C:/src/wr/AutoTag/AutoTag2003/bin/Debug/AutoTag2003.dll (this is correct).

Any ideas

thanks - dave

ps - I don't mean to denigrate whoever designed the AddIn API and they might be a really nice person. But providing no information about why an AddIn doesn't load so everyone is left guessing when they have a problem - that really is poor design. And it costs developers like me days over the course of a year because of that poor design.

Re: Visual Studio Tools for Office Why does Word not tell you why an AddIn won't load


Fixed - LoadBehavior needs to be 3. No idea why as 2 worked before AFAIK. From reading the docs it seems 0x02 should cause a load before 0x01.

- thanks - dave