You can set the following in your project file to change the URI’s in the generated code: <PropertyGroup> <AssemblyVersion>1.0.0.0</AssemblyVersion> <AssemblyPublicKeyToken>[YOUR_PUBLIC_KEY_TOKEN]</AssemblyPublicKeyToken> </PropertyGroup>
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
When you sign an assembly with a strong name based on a private key that you create, this has the following benefits: A strong name guarantees the uniqueness of an assembly’s identity by adding a public key token and a digital signature to the assembly. A strong name can be matched to a public key … 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
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