From MSDN: A strong name consists of the assembly’s identity — its simple text name, version number, and culture information (if provided) — plus a public key and a digital signature. You can use strong naming to ensure that when you load a DLL you get exactly the DLL you were expecting and not some … Read more
You can use the Strong Name tool to determine if the assembly is strongly named. In command prompt you can do this to verify it is a strong named assembly. sn -v “C:\MyAssemblyPath” and to get the public token, you can do this sn -T “C:\MyAssemblyPath” You can also use Reflector or ILSpy to find … Read more
This is a shameless copy-paste from I Note It Down and is a simple way to get the FQN for the project output: Open Visual Studio Go to Tools –> External Tools –> Add Title: Get Qualified Assembly Name Command: Powershell.exe Arguments: -command “[System.Reflection.AssemblyName]::GetAssemblyName(\”$(TargetPath)\”).FullName” Check “Use Output Window”. The new tool appears under Tools –> … Read more
I’ve taken advantage of non-signed assemblies to get around issues before and in academic settings shown people why it’s important. I replaced a DLL file that was unsigned (again in an academic setting) with one I made with the same name, same signatures, and used .NET Reflector to copy and paste the original code, but … Read more
The .snk file is used to apply a strong name to a .NET assembly. such a strong name consists of a simple text name, version number, and culture information (if provided)—plus a public key and a digital signature. The SNK contains a unique key pair – a private and public key that can be used … Read more
I’ve finally found the solution. Edit the .csproj file for the project in question. Delete the following lines of code: <PropertyGroup> <ManifestCertificateThumbprint>………..</ManifestCertificateThumbprint> </PropertyGroup> <PropertyGroup> <ManifestKeyFile>xxxxxxxx.pfx</ManifestKeyFile> </PropertyGroup> <PropertyGroup> <GenerateManifests>true</GenerateManifests> </PropertyGroup> <PropertyGroup> <SignManifests>false</SignManifests> </PropertyGroup>
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 Assemblies The basic principle to sign a thirp-party is to Disassemble the assembly using ildasm.exe and save the intermediate language … Read more