Closed thudugala closed 6 years ago
We don't think strong name signing is still a good thing to do as it breaks assembly binding redirects when updating dependencies or using different but semantically compatible versions.
If this prevents you from shipping your code you may find some help in the FAQ:
Otherwise i would recommend suppressing the warnings CS8002/CA2210
.
Thanks for the quick response. 👍
Ok, closing this then. Thx.
Warning CS8002 Referenced assembly 'FontAwesome.Sharp, Version=4.7.1.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.