Cancelling Outlook/Word/Excel startup show the disabled warning popup

Add-in Express™ Support Service
That's what is more important than anything else

Cancelling Outlook/Word/Excel startup show the disabled warning popup
 
Fabrice Durieu


Guest


Hello ADX team,

I've this behavior:

User start Outlook or Excel or Word (2010).
In the splash screen, user click on the "cancel" button (2010) or close the splash screen.
User restart the application, and get the message:

Outlook experienced a serious problem with the 'my add-in name' add-in. If you have seen this message multiple times, you should disable this add-in and check to see if an update is available. Do you want to disable this add-in?



Of course some users click YES and then call our support :D

Do you know how I could avoid this popup ?

Thank you
Posted 26 Jun, 2015 04:15:07 Top
Dmitry Kostochko


Add-in Express team


Posts: 2875
 Joined: 2004-04-05
Hi Fabrice,

I can assume the code of your add-in throws an unhandled exception in this scenario and that is why Microsoft Office applications suggest to disable your add-in at next start. I would suggest that you debug your code and fix this issue.
Posted 26 Jun, 2015 05:12:29 Top
Fabrice Durieu


Guest


Do you know what Outlook does in this situation ? it just kill the thread ? Or call the shutdown method differently ?
Because otherwise if the app is closed "normally" I don't have any error
Posted 26 Jun, 2015 05:16:11 Top
Dmitry Kostochko


Add-in Express team


Posts: 2875
 Joined: 2004-04-05
Hi Fabrice,

Do you know what Outlook does in this situation ?


I think it closes.

it just kill the thread ?


I don't think so.

Or call the shutdown method differently ?


As you probably know, Outlook 2010 (as well as 2013) does not raise either the AddinBeginShutdown or AddinFinalize event by default. The Quit event of the ADXOutlookAppEvents component can be raised.

Because otherwise if the app is closed "normally" I don't have any error


Pay attention to the "asynchronous" code if there is such in your solution. I mean timers, additional threads, background workers and the like. Their code may try to execute when Outlook is closing and probably this causes the issue.
Posted 26 Jun, 2015 08:49:41 Top