Here are the results when running against a strongly named assembly, then one that is not strongly named. You tell whether an Assembly/DLL has been successfully strong-named using the Strong Name Tool ( sn.exe) (which can be found somewhere like here: C:\Program Files\Microsoft SDKs\Windows\v7.0A\bin\sn.exe) by running the following at the command line: sn -vf NET Assembly is Strongly Named.Īpproach #1: Testing for Strong Name on Command Line or in a Script Then in the final section of this post the often confusing – though very important – differences between Strongly Named assemblies and Digitally Signed assemblies are clarified.īut first, here are three approaches for telling whether a. Towards the end, this post discusses use of Strong Names with Silverlight. (English language note: I assume the form “strongly named” is preferred over “strong named” since that’s the form used in the output of the sn.exe tool shown immediately below.) Here are several convenient ways to tell whether a. NET Assembly is Strongly Named (or has Strong Name)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |