strongname

问题 I have been reading the proper article in MSDN, Strong-Named Assemblies and a related Stack Overflow question, Checking an assembly for a strong name . To which extent can a strong-named assembly be verified to avoid tampering? Is it possible to use strong-naming to verify an assembly author? The first question arises after reading the CSharp411 article .NET Assembly FAQ – Part 3 – Strong Names and Signing , which mentions this, among other problems of using strong names: \" Cannot Stop Full

问题 How do I find out the fully qualified name of my assembly such as: MyNamespace.MyAssembly, version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 I\'ve managed to get my PublicKeyToken using the sn.exe in the SDK, but I\'ld like to easily get the full qualified name. 回答1: If you can load the assembly into a .NET application, you can do: typeof(SomeTypeInTheAssembly).Assembly.FullName If you cannot then you can use ildasm.exe and it will be in there somewhere: ildasm.exe

问题 I\'ve added a weakly named assembly to my Visual Studio 2005 project (which is strongly named). I\'m now getting the error: \"Referenced assembly \'xxxxxxxx\' does not have a strong name\" Do I need to sign this third-party assembly? 回答1: To avoid this error you could either: Load the assembly dynamically, or Sign the third-party assembly. You will find instructions on signing third-party assemblies in .NET-fu: Signing an Unsigned Assembly (Without Delay Signing) . Signing Third-Party