If the problem that initially caused the application to soft disable the add-in has not been fixed, the application will soft disable the add-in again. When you re-enable a soft-disabled add-in, the application immediately attempts to load the add-in. Type the value (see table below) in the Value Data box, click Decimal, and then click OK. Right-click LoadBehavior and then click Modify. For example, an application might soft disable an add-in if it throws an unhandled exception while the Right-click crmaddin.Addin, point to New, and then click DWORD Value or DWORD (32-bit) Value. Soft disabling can occur when an add-in produces an error that does not cause the application to unexpectedly close. Startup event handler in your add-in is executing.
It might also occur on your development computer if you stop the debugger while the Hard disabling can occur when an add-in causes the application to close unexpectedly. If an application does not load your add-in, the application might have hard disabled or soft disabled your add-in.
Microsoft Office applications can disable add-ins that behave unexpectedly. Thus, you will be able to find the problematic one. For example, you can log any operations or method calls.
#Microsoft word add in load behavior code#
I'd recommend using any logging mechanism to be sure that your code works as it should. Most probably the add-in fires exceptions. Uninstalled and re-installed the add-in, to no avail.
#Microsoft word add in load behavior how to#
I am lost as to how to diagnose this issue - tried to enable fusion logging, but didn't work. The add-in is working perfectly for other users within the same company. The user's Outlook is connected to an exchange server account, and they have Symantec enterprise security for the antivirus (do not know if it makes a difference). However, when I navigate to theĪdd-in registry key using regedit, the LoadBehaviour is 3! On the options>add-ins>Manage COM add-ins window, my add-in is unselected, and the load behavior is displayed as 'Unloaded'. The add-in had been working for him for a while, but it has suddenly stopped working.ĭigging in I see that the add-in is listed as 'Disabled' in the options>add-ins window. The add-in is designed to support Outlook 2003 to 2013, this user is running Outlook 2010 on an WinXP SP3 I have an Outlook managed COM add-in (not VSTO - i know, it's a pain, but requirement dictates it) that is working perfectly.except for one user.
0 kommentar(er)
