Why stdole.dll in VSTO is not strong name signed? RRS feed

  • Question

  • While struggling with some exceptions about strong signing of stdole.dll, I found that stdole.dll is NOT actually strong name signed, which was copied from "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Visual Studio Tools for Office\PIA\Common\stdole.dll". I solved this problem by replacing stdole.dll with assembly from GAC ("C:\WINDOWS\assembly\GAC\stdole\7.0.3300.0__b03f5f7f1150a2a\stdole.dll"), which is properly strong name signed.

    Now I curious about why stdole.dll in VSTO is not strong name signed. sn says stdole.dll is delay-signed or test-signed, but why?

    • Edited by Harnel Wednesday, January 30, 2019 6:22 AM
    Wednesday, January 30, 2019 6:20 AM