none
about word add in loading perfermance RRS feed

  • Question

  • i develop a simple addin which use seven third-part assambly, after deploy in word2013, word2013 startup procedure will be very slow, almost 14 seconds, is any idea to improve the performance?

    below is vs output info in word setup.

    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Office.Runtime\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Tools.Office.Runtime.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\mscorlib.resources\v4.0_4.0.0.0_zh-Hans_b77a5c561934e089\mscorlib.resources.dll'. Module was built without symbols.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Hosting\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Tools.Applications.Hosting.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.ServerDocument\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Tools.Applications.ServerDocument.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Office.Tools\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.Office.Tools.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Runtime\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Tools.Applications.Runtime.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Accessibility\v4.0_4.0.0.0__b03f5f7f11d50a3a\Accessibility.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Office.Runtime.resources\v4.0_10.0.0.0_zh-Hans_b03f5f7f11d50a3a\Microsoft.VisualStudio.Tools.Office.Runtime.resources.dll'. Module was built without symbols.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Deployment\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Security\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Security.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Deployment.resources\v4.0_4.0.0.0_zh-Hans_b03f5f7f11d50a3a\System.Deployment.resources.dll'. Module was built without symbols.
    A first chance exception of type 'System.Deployment.Application.DeploymentException' occurred in System.Deployment.dll
    'WINWORD.EXE' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll'. Cannot find or open the PDB file.
    The thread 0x40d8 has exited with code 259 (0x103).
    'WINWORD.EXE' (CLR v4.0.30319: Domain 2): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Office.Runtime\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Tools.Office.Runtime.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Hosting\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Tools.Applications.Hosting.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.Runtime\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Tools.Applications.Runtime.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Deployment\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Security\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Security.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.Tools.Applications.ServerDocument\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Tools.Applications.ServerDocument.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Office.Tools\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.Office.Tools.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Office.Tools.Word.Implementation\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.Office.Tools.Word.Implementation.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Office.Tools.Common.Implementation\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.Office.Tools.Common.Implementation.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Office.Tools.Common\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.Office.Tools.Common.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Office.Tools.Word\v4.0_10.0.0.0__b03f5f7f11d50a3a\Microsoft.Office.Tools.Word.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Users\洪\AppData\Local\assembly\dl3\TM8K3PEQ.P2B\VAO29J41.8VN\9fca726c\e84b48cf_4a13cf01\com.ware4u.km.connector.dll'. Symbols loaded.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Users\洪\AppData\Local\assembly\dl3\TM8K3PEQ.P2B\VAO29J41.8VN\c5deeca2\00a74ef1_658dce01\Microsoft.Office.Tools.Common.v4.0.Utilities.dll'. Cannot find or open the PDB file.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Users\洪\AppData\Local\assembly\dl3\TM8K3PEQ.P2B\VAO29J41.8VN\bffa88d0\4450cea6_4a13cf01\com.ware4u.km.word.dll'. Symbols loaded.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Users\洪\AppData\Local\assembly\dl3\TM8K3PEQ.P2B\VAO29J41.8VN\af941682\00e70525_c22ece01\Esent.Interop.dll'. Symbols loaded.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\assembly\GAC_MSIL\Microsoft.Office.Interop.Word\15.0.0.0__71e9bce111e9429c\Microsoft.Office.Interop.Word.dll'. Module was built without symbols.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Windows\assembly\GAC_MSIL\office\15.0.0.0__71e9bce111e9429c\office.dll'. Module was built without symbols.
    'WINWORD.EXE' (CLR v4.0.30319: com.ware4u.km.connector.vsto|vstolocal): Loaded 'C:\Users\洪\AppData\Local\assembly\dl3\TM8K3PEQ.P2B\VAO29J41.8VN\92629746\2c8a17ce_4a13cf01\com.ware4u.km.bridge.dll'. Symbols loaded.



    Friday, January 17, 2014 10:27 AM

Answers

  • Hi sendreams,

    You need to measure the performance using the release build (not debug). Please let know your results after utilizing the NGEN utility.

    • Marked as answer by sendreams Tuesday, March 11, 2014 9:27 AM
    Thursday, February 6, 2014 11:32 AM
  • hi, Eugene

    i sorry for delay reply

    I have got two message, the bad one is my computer has been broken for several days, the good one is  i have been restored entire develop environment with vs2013 sp1 + office2013 64 yesterday, now the slow startup problem has gone. 

    thank you very much.

    Monday, March 3, 2014 1:26 PM

All replies

  • Hello sendreams,

    First of all, I didn't notice any time marker in the log. Why did you decide that loading of assemblies takes much time?

    If the debug build is used for testing, I'd recommend using System.Diagnostics.Debug.WriteLine method for measuring the speed. For example, thus you can find the code which requires a lot of time for initializing (classes ctors and their initializers, etc.).

    Finally, I have noticed the following string in near your assemblies: Symbols loaded. It looks like you need to choose the Release configuration instead of Debug for measuring the real time. 

    Friday, January 17, 2014 12:19 PM
  • hi, Eugene

    i record a video to show the real experience,

    you can see in below video

    loading poor performance

    Friday, January 17, 2014 1:22 PM
  • i also use vistual studio's "performace and Diagnostics" analysis tool to measure the startup time, 

    see below picture

    analysis report

    but i don't think the number is accurate, in real experience the startup time at least 14 second. ( the startup time in the video is more longer, just because record the video making the computer slower)



    • Edited by sendreams Friday, January 17, 2014 1:37 PM
    Friday, January 17, 2014 1:35 PM
  • Some updated info:

    my environment:

    vs2013, office2013 64 bit

    Friday, January 17, 2014 1:39 PM
  • Hi sendreams,

    Where do the assemblies shown on the screenshot come from?

    Note, you can initialize all the required classes right after the add-in's started. For example, you can run a second thread for initializing the required components.

    Friday, January 17, 2014 4:15 PM
  • Did you try to debug the code and located the slow methods or classes?

    Please take a look at the How Office Performs Certificate Revocation article. Is certificate revocation enabled on the PC?

    Friday, January 17, 2014 4:37 PM
  • exactly, i do nothing in my add-in's startup event or documentopen event, in my design, the add-in is keep slient unless user push the command from ribbon ui.

    i found other thread in this forum, some of people talk about this problem,  i want to use NGen for a testing.

    Saturday, January 18, 2014 2:59 AM
  • Hi sendreams,

    Did you have a chance to look at the certificate revocation settings on problematic machine?

    Sunday, January 19, 2014 9:44 AM
  • hi, Eugene

    i sorry for delay reply, i have tested  the "the certificate revocation" setting, but it didn't useful for performance

    thank you for your suggestion.

    Saturday, January 25, 2014 5:39 AM
  • Hi sendreams,

    Did you try to test a newly created clean add-in project without any third-party libraries included?

    It looks like the issue is related to the libraries you are using at the moment.

    Saturday, January 25, 2014 11:55 AM
  • hi, Eugene

    i create a empty word addin project, and also have poor performance.

    you have reminded me something, i have changed vs2012 to vs2013 for some days, just because i want to using the "edit and continue" feature in 64 bit develop environment,  may be it is the behind reason. could it be said that i should return to vs2012. 

    Monday, January 27, 2014 8:56 AM
  • Hi sendreams,

    What do you mean saying "poor performance"? Did you try to profile a newly created sample add-in? Do you get any delay?

    Finally, I'd recommend installing Update 1 for Visual Studio 2013.

    Monday, January 27, 2014 2:05 PM
  • hi, Eugene

    i now using vs2013 update 1 already, and i use it creating a empty word-addin project, but the word startup time also up than 10 seconds. so i called it "poor performance", if closing this add-in, the startup time will smaller than 2 seconds. so i don't think the low performance caused by third-part libraries.


    my environment:

    vs2013 with update 1

    office2013 x64 with latest update

    win8 enterprise with latest update

    thanks


    • Edited by sendreams Tuesday, January 28, 2014 2:47 AM
    Tuesday, January 28, 2014 2:46 AM
  • Hello sendreams,

    Could you please take a screenshot of the certificate revocation settings on the problematic machine?

    Please take a look at the similar forum thread - slow load time for VSTO AddIn in Word 2013 64-bit . Also please see the How to troubleshoot problems that occur when you start or use Word article.

    The following links may be useful too:

    Resolving performance issues with loading Office add-ins (VSTO add-ins or Shared add-ins)

    Improving the Performance of an Application-Level Add-in

    Tuesday, January 28, 2014 3:07 PM
  • hi,Eugene

    sorry for delay reply, we have celebrated chinese new year recently days.

    the snapshot please look below picture:


    thank you for your topic link.


    • Edited by sendreams Tuesday, February 4, 2014 3:20 PM
    Tuesday, February 4, 2014 2:35 PM
  • Thank you for publishing a screenshot. Could you please translate options shown on the image?
    Tuesday, February 4, 2014 7:45 PM
  • hi, Eugene

    检查发行商的证书是否已吊销 — — "Check for publisher's certificate revocation"

    检查服务器证书是否已吊销 — — "Check for server certificate revocation"


    • Edited by sendreams Wednesday, February 5, 2014 3:46 AM
    Wednesday, February 5, 2014 3:45 AM
  • Hi sendreams,

    Thank you. Now I see that options are not selected.

    What is the target framework of your sample add-in? Did you try to use the NGEN for preparing native images before running a host application?

    Do you still measure the Debug build? Or do you run the Release configuration?

    Wednesday, February 5, 2014 7:19 PM
  • hi, Eugene

    i run in debug mode, NGen have not used yet but in my schedule, i will testing NGen within the next few days.

    then my target framework is 4.5.

    thanks


    • Edited by sendreams Thursday, February 6, 2014 8:08 AM
    Thursday, February 6, 2014 8:07 AM
  • Hi sendreams,

    You need to measure the performance using the release build (not debug). Please let know your results after utilizing the NGEN utility.

    • Marked as answer by sendreams Tuesday, March 11, 2014 9:27 AM
    Thursday, February 6, 2014 11:32 AM
  • hi, Eugene

    release mode almost has no effect on performance. NGen i will be try later.

    thanks

    Monday, February 10, 2014 2:28 PM
  • Hi sendreams,

    You should always test the release edition. Please let me know whether NGen helps.

    Monday, February 10, 2014 6:45 PM
  • Hi sendreams,

    I failed to reproduce your issue on my test environment (Office 2013 64-bit + Visual Studio 2013). It is possible that encountering the performance issue at the first time loading add-ins (should be far less than 10s) due to JIT compiling process.

    By the way, did it make any difference after using NGen?


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, February 26, 2014 2:05 AM
    Moderator
  • Jeffrey,

    I couldn't reproduce the issue on my machine too.

    Wednesday, February 26, 2014 9:05 AM
  • hi, Eugene

    i sorry for delay reply

    I have got two message, the bad one is my computer has been broken for several days, the good one is  i have been restored entire develop environment with vs2013 sp1 + office2013 64 yesterday, now the slow startup problem has gone. 

    thank you very much.

    Monday, March 3, 2014 1:26 PM
  •  a bit diff from old environment: i installed office2013 english version instead of Chinese version. i will be testing chinese version later.
    Monday, March 3, 2014 1:29 PM
  • Good news!

    Thank you for letting me know.

    Monday, March 3, 2014 2:06 PM
  • I hope all will be good and you will not encounter any delay any longer. Anyway, please keep me notified.
    Monday, March 3, 2014 2:07 PM
  • hi, Eugene

    in yesterday, my office startup time going to slowly again after installed the windows8 sdk.

    i think this is a potential reason, because i also install the win8 sdk at before but i miss it.

    just let you know, thanks

    Friday, April 11, 2014 2:06 AM
  • hi, Eugene

    maybe something else, i don't find the really reason yet. after reinstall addin the speed return to normal.

    Friday, April 11, 2014 2:30 PM