D
David Thielen
You know, whoever designed the Word COM API really did a lousy job. It's
amazing that this is still a major problem.
Ok, it's been 3 weeks so time for this problem again. This time it's on my
development machine. It was running my Add-In 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
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm
amazing that this is still a major problem.
Ok, it's been 3 weeks so time for this problem again. This time it's on my
development machine. It was running my Add-In 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
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htm