KB suggestion - how to debug shim/start issues

[David Thielen]

I strongly encourage that someonw rite a KB article on the following:

Give user’s a way to debug problems when an add-in won’t start, both
directly and using the COM shim. Presently there appears to be no way
to find out why starting an add-in fails. For one example, my nant
script wasn’t successfully strong naming my assemblies. So they didn’t
load. After 4 hours of very carefully going over everything several
times I found it. But it would have been trivial if somewhere I got an
error message that the failure was due to the assemblies not being
strong named. Just some method to expose the errors.

thanks - dave

 

[Mark Bower [MSFT]]

Not exactly an answer David, but the Smart Tag toolkit may be interesting
for you to look at. This is a toolkit developed with the guys at
OfficeZealot which provides a way to debug common smart tag problems. Now
the interesting thing from your point of view is that many of the problems
that can afflict managed smart tags (unsigned DLL, full trust not applied)
can also affect other managed code. The source code is available on
GotDotNet if you want to go investigate and see if you can adapt it to your
scenario.


http://www.microsoft.com/downloads/...e2-85e4-42e0-a57c-12a3f93f5c63&DisplayLang=en

http://msdn.microsoft.com/office/un...2k3ta/html/odc_managed_smarttag_utilities.asp

http://www.gotdotnet.com/workspaces/workspace.aspx?id=9d3aed42-f82b-4b7b-8c84-254a0ee2fe81


--
Mark Bower
Microsoft
http://blogs.msdn.com/bowerm

This post is provided 'as-is' without warranty and confers no rights.

 

[David Thielen]

Wow - this is exactly what they need for add-ins! I tried it but it
wants the recognizer interface and a Word add-in doesn't have that.

Hopefully they'll do one of these for add-ins someday.

thanks - dave