strong-named-key

Strong Name sn.exe: Failed to install key pair — Object already exists

由 橙三吉。 提交于 2021-02-05 20:49:20
问题 I have 2 different versions of the same project on my machine. One from the code trunk, and the other from a code branch. These projects use a .pfx key to enable strong naming. When I first tried to compile the trunk version of the project I get the following error: Cannot import the following key file: sgKey.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key

Strong Name sn.exe: Failed to install key pair — Object already exists

由 有些话、适合烂在心里 提交于 2021-02-05 20:48:21
问题 I have 2 different versions of the same project on my machine. One from the code trunk, and the other from a code branch. These projects use a .pfx key to enable strong naming. When I first tried to compile the trunk version of the project I get the following error: Cannot import the following key file: sgKey.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key

same project different solution sign configuration

由 半城伤御伤魂 提交于 2020-01-07 07:43:25
问题 I am trying to find way to use the strong name sign as an configuration. My case is: I have project that it include in two different solution. For one solution I want that the project will be sign with strong name key, but for the other solution I want that the project will be without sign. Currently I declare the signing throw: project->properties->signing. 回答1: OK, I got it, just edit proj file manually <PropertyGroup Condition="'$(SolutionName)' == 'SolutionToSign' "> <snip />

same project different solution sign configuration

由 非 Y 不嫁゛ 提交于 2020-01-07 07:43:16
问题 I am trying to find way to use the strong name sign as an configuration. My case is: I have project that it include in two different solution. For one solution I want that the project will be sign with strong name key, but for the other solution I want that the project will be without sign. Currently I declare the signing throw: project->properties->signing. 回答1: OK, I got it, just edit proj file manually <PropertyGroup Condition="'$(SolutionName)' == 'SolutionToSign' "> <snip />

Enumerating container names of the strong name CSP

由 北慕城南 提交于 2019-12-21 03:42:19
问题 I'm trying to find some information about how to (if at all possible) enumerate all container names in the Strong Name CSP (Cryptographic Service Provider). Essentially, when you type sn.exe -i key.snk MyContainerName , the public and private key pairs are stored into what's called a "container". Later, within your code, you could specify the container name in the AssemblyKeyNameAttribute, e.g.: [assembly: AssemblyKeyName("MyContainerName")] This will cause the assembly to be signed at

Mono xbuild error CS1548 - key file has incorrect format

由 别说谁变了你拦得住时间么 提交于 2019-12-14 01:14:57
问题 So I'm trying to get a VS2010 C# project to go cross-platform. First goal is build it in Mono 2.10.5 for Windows. I have not touched any code yet - I'm starting with xbuild's recent ability to build sln files. (Incidentally I use Jenkins to trigger builds, not that it matters as I get the same result at the command-line.) I get " error CS1548: Error during assembly signing. The specified key file `AlphaBeta.pfx' has incorrect format ". There's not much google juice on this error. Does anyone

Strong name signature not valid for this assembly Microsoft.Practices.EnterpriseLibrary.Data.dll

由 纵然是瞬间 提交于 2019-12-11 10:19:15
问题 I am running windows form application as ClickOnce Deployment. When i debugg the solution i am not getting any error. it's working fine. But, when i publish the application using click once deployment and run the application from folder, i am getting the following error log. Can anyone help me out what exactly the problem is? The Dll's are in assemblies folder in one of the project.And they are used in other project as reference. PLATFORM VERSION INFO Windows : 6.1.7601.65536 (Win32NT) Common

Enumerating container names of the strong name CSP

由 余生长醉 提交于 2019-12-03 11:18:02
I'm trying to find some information about how to (if at all possible) enumerate all container names in the Strong Name CSP (Cryptographic Service Provider). Essentially, when you type sn.exe -i key.snk MyContainerName , the public and private key pairs are stored into what's called a "container". Later, within your code, you could specify the container name in the AssemblyKeyNameAttribute , e.g.: [assembly: AssemblyKeyName("MyContainerName")] This will cause the assembly to be signed at compile time. I am trying to find out if it's possible to somehow enumerate all container names. I'm writing
订阅 strong-named-key