|                                 css@factset.com                				   
 Guest
 
 
 
 | 
                | We are making initial server connection on AddinModule_AddinInitialize method. I observed the time taken for the initialization(700ms) is completely independent of the Outlook RMS add-in boot time(157ms). 
 I delayed the server response for 10 sec, to check the add-in boot time. [added WAITFOR DELAY '00:00:10'; on the login proc]
 1) Outlook installation takes 10 sec. (we can see outlook displed to the user after 10 sec)
 2) But the Outlook RMS add-in boot time is still 157ms.
 
 Unfortunately for some customers/users, Boot time is more than 1000 ms, so add-in is disabled.
 
 ------------------------------------------------------
 Name: FactSet RMS MSOutlook Save Add-In
 Description: AddinModule
 ProgID: RedAlertsMSOutlookAddinX.AddinModule
 GUID:
 
 {294DED6A-4680-41BE-A2A7-0178D45C869C}
 Load Behavior: 3
 HKLM: 1
 Location: c:\branches\6.2.7\redalerts\bin\adxloader64.dll
 Boot Time (Milliseconds): 157
 
 
 There was a similar issue with add-in express support ticket https://www.add-in-express.com/forum/read.php?FID=1&TID=14331
 
 How is this add-in boot time calculated? Same add-in load time is different for each user?
 I'm getting boot time 157 ms and another user is getting 900 ms/ 1090 ms, why is it having a huge difference?
 
 Thanks
 Raj
 | 
 | 
  
        |                                 Andrei Smolin                				   
 Add-in Express team
 
 
 Posts: 19177
 Joined: 2006-05-11
 
 | 
                | Hello Raj, 
 
 css@factset.com writes:
How is this add-in boot time calculated? Same add-in load time is different for each user? I'm getting boot time 157 ms and another user is getting 900 ms/ 1090 ms, why is it having a huge difference?
 
 These are determined by Outlook and the load of the current computer at that moment. Please refer to section Preventing an add-in from being disabled at https://msdn.microsoft.com/en-us/library/office/jj228679.aspx.
 
 An Add-in Express based add-in isn't affected by the Outlook 2013 and 2016's resiliency logic. You can create a test add-in showing a message box in the AddinInitialize event and you'll see how Outlook doesn't disable this add-in if you keep the message box shown for minutes.
 
 If you have a reproducible scenario in which an Add-in Express for Office and .NET based add-in gets disabled, we are interested. We would like to get more details about the issue and how we can reproduce it.
 
 
 Andrei Smolin
 Add-in Express Team Leader
 | 
 | 
  
        |                                 css@factset.com                				   
 Guest
 
 
 
 | 
                | Thanks Andrei.  Are there other ways we can force an Add-in Express Add-in to be affected by the resiliency logic performance criteria?  Along with startup resiliency, there are four other areas that can cause an add-in to be disabled: 
 Shutdown, Folder Switch, Item open, Invoke Frequency
 
 https://msdn.microsoft.com/en-us/library/office/jj228679.aspx#Anchor_7
 | 
 | 
  
        |                                 Andrei Smolin                				   
 Add-in Express team
 
 
 Posts: 19177
 Joined: 2006-05-11
 
 | 
                | Hello Raj, 
 Of all the criteria in that table, an Add-in Express add-in isn't affected by the Startup criterion. All other criteria can't be bypassed.
 
 
 Andrei Smolin
 Add-in Express Team Leader
 | 
 |