oising / strongnaming Goto Github PK

The underlying .NET APIs don't complain with an invalid password for a PFX. The resultant StrongNameKeyPair instance is just zeroed out. I should detect this and throw a terminating error.

I'm trying to sign our assemblies without doing a full rebuild but I'm running into errors when I try to submit our signed nuget package to symbol source.

Package submission failed: Incorrect hash code for Exceptionless.Console binaryHash symbolHash ED901068EDCF40AF8A33BA270CE93B861

I am trying to type the commands for the strong name by inputting the commands until "dir -rec *NET.dll | set-strongname -keypair $key -verbose". My file name is end up with the word NET.
The console shows a message
"Set-StrongName : Value does not fall within the expected range.
At line:1 char:35

• dir -rec *NET.dll | set-strongname <<<< -KeyPair $key -force
  • CategoryInfo : NotSpecified: (:) [Set-StrongName], ArgumentExceptio
    n
  • FullyQualifiedErrorId : System.ArgumentException,StrongNaming.SetStrongNameCommand"

The library I am trying to import is
ImageMagick.NET
http://imagemagick.codeplex.com/

A bad file is in the current solution.

Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations, update strongnaming package to handle this attribute.

Thanks

The StrongName module was not installed into my Powershell profile. Thus, I was not able to use the command outside of the VS shell.

The cmdlets Test-Strongname and Set-Strongname throw exceptions when they are given files which are not valid .NET assemblies. An example of this would be native DLLs.

Instead, this exception should be caught an return false or write an error, respectively.