When you use a try...catch block in your managed code you'll be catching
both .NET errors as well as COM exceptions.
Depending on what your code is doing you might also cause unhandleable
exceptions that won't come to your error handling and in some cases might
only fire after your addin is disconnected or Outlook is closed. I've seen
that with some errors that were seen with WordMail where after exit you see
a kernel32 error.
Outlook itself isn't going to catch any errors for you, but it will fire
errors up through the CLR and those would be COM exceptions since Outlook is
unmanaged code.
--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm
"Craig Buchanan" <Cr***********@discussions.microsoft.comwrote in message
news:A0**********************************@microsof t.com...
There was an exception in the form's constructor that being thrown but not
caught by Outlook, so the code hung. I've corrected the code and the form
works as expected.
Incidentally, is there a type of exception that I can be caught by
Outlook?
Probably a COM-type exception, I'll wager.
Thanks for your time, Ken.