assembly-signing

How I do a sign an assembly that has already been built into a dll specifically flute.dll

若如初见. 提交于 2019-11-29 20:11:57
The reason I want to sign the dll is because I want to add it to the Global Assembly Cache. The assembly is a css parsing engine written in Java and ported to J#. I use VS2008 so I can't make J# projects. It doesn't have a strong name key assigned to it and I have no idea how to do it now that it's built. Anyone have any ideas? After a little searching, I found this post that explains one way of doing it. Exerpt: From a VS.NET command prompt, enter the following: Generate a KeyFile: sn -k keyPair.snk Obtain the MSIL for the provided assembly: ildasm providedAssembly.dll /out:providedAssembly

Is there an easy way to sign a C++ CLI assembly in VS 2010?

无人久伴 提交于 2019-11-29 05:49:06
问题 Right now I am setting the Linker/Advanced/KeyFile option. I am getting the "mt.exe : general warning 810100b3: is a strong-name signed assembly and embedding a manifest invalidates the signature. You will need to re-sign this file to make it a valid assembly." . Reading from the web, it sounds like I have to set the delay signing option, download the SDK, and run sn.exe as a post build event. Surely there must be an easier way to do this common operation in VS2010? 回答1: There's a fair amount

Signing of .NET Assemblies

岁酱吖の 提交于 2019-11-28 17:54:10
What does digital signature have to do with strong named assemblies. I read that a strongly named assembly has public key and digital signature with it. From the Wikipedia article "Assembly (CLI)" : "Signing the assembly involves taking a hash of important parts of the assembly and then encrypting the hash with the private key. The signed hash is stored in the assembly along with the public key. The public key will decrypt the signed hash. When the CLR loads a strongly named assembly it will generate a hash from the assembly and then compare this with the decrypted hash. If the comparison

How to declare a friend assembly?

我的未来我决定 提交于 2019-11-27 05:56:06
I have 2 projects in my solution: Assembly (Basic Library) Test Assembly (NUnit) I had declared the test assembly as friends assembly in first project: [assembly: InternalsVisibleTo ("Company.Product.Tests")] Everything was working fine till I realised that I have forgot to setup the solution to sign my assemblies. So created a snk file and setup the visual studio project to sign the first assembly (Basic Library). Now when I compile the first project, I get following error: Friend assembly reference 'Company.Product.Tests' is invalid. Strong-name signed assemblies must specify a public key in