AnsweredAssumed Answered

How to enable .Net strong name verification with AddIn

Question asked by mik1971 on May 21, 2020
Latest reply on May 28, 2020 by gkmieliauskas_cellexp



We have an AddIn that using some our DLL .Net libraries. The libraries are updated from time to time. To make sure AddIn uses the updated DLL's assembly version, both (AddIn and DLL) are using .Net strong name signing.


How to enable .Net strong name verification properly? 

Whatever steps to enable are, should it be

  • on developer's machine?
  • on user's machine?
  • on both?


In fact, we added "Signing" in VisualStudio.

It appears not working when updating DLL. AddIn continues to load a DLL with "wrong" version number.



VisualStudio 2017

.Net 4.7.0

ArcObjects 10.6.1