[GH-ISSUE #107] Problem signing assembly #86

New issue

Closed

opened 2026-02-25 21:30:38 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 21:30:38 +03:00

Owner

Originally created by @TDS-NO on GitHub (Sep 1, 2025).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/107

Originally assigned to: @brutaldev on GitHub.

Get the following error trying to sign assemblies ( already signed ) ...

Microsoft Windows [Version 10.0.26100.4946]
(c) Microsoft Corporation. Med enerett.

C:\Users\rhh>"C:\Program Files\BrutalDev.NET Assembly Strong-Name Signer\StrongNameSigner.Console.exe" -in "C:\Users\rhh.nuget\packages\fastendpoints.security"

---- Brutal Developer .NET Assembly Strong-Name Signer 3.6.1.0 ----

Console application to sign .NET assemblies with a strong-name key and fix assembly references.

Loading assemblies...
Checking assembly references...
Checking assembly references in 'C:\Users\rhh.nuget\packages\fastendpoints.security\6.1.0\lib\net10.0\FastEndpoints.Security.dll'.
Checking assembly references in 'C:\Users\rhh.nuget\packages\fastendpoints.security\6.1.0\lib\net8.0\FastEndpoints.Security.dll'.
Checking assembly references in 'C:\Users\rhh.nuget\packages\fastendpoints.security\6.1.0\lib\net9.0\FastEndpoints.Security.dll'.
Checking assembly references in 'C:\Users\rhh.nuget\packages\fastendpoints.security\6.2.0\lib\net10.0\FastEndpoints.Security.dll'.
Checking assembly references in 'C:\Users\rhh.nuget\packages\fastendpoints.security\6.2.0\lib\net8.0\FastEndpoints.Security.dll'.
Checking assembly references in 'C:\Users\rhh.nuget\packages\fastendpoints.security\6.2.0\lib\net9.0\FastEndpoints.Security.dll'.
Strong-name unsigned assemblies...
Fix InternalVisibleToAttribute references...
Fix CustomAttributes with Type references...
Cleanup...
System.ArgumentException: An item with the same key has already been added.
ved System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
ved System.Collections.Generic.Dictionary2.Insert(TKey key, TValue value, Boolean add) ved System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer) ved Brutal.Dev.StrongNameSigner.SigningHelper.FixCustomAttributes(HashSet1 allAssemblies, Dictionary2 tempFilePathToInputOutputFilePairMap, Boolean& hasErrors) ved Brutal.Dev.StrongNameSigner.SigningHelper.SignAssemblies(IEnumerable1 assemblyInputOutputPaths, String keyFilePath, String keyFilePassword, String[] probingPaths)
ved Brutal.Dev.StrongNameSigner.Console.Program.SignAssemblies(Options options)
ved Brutal.Dev.StrongNameSigner.Console.Program.Main(String[] args)

C:\Users\rhh>

Originally created by @TDS-NO on GitHub (Sep 1, 2025). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/107 Originally assigned to: @brutaldev on GitHub. Hi Get the following error trying to sign assemblies ( already signed ) ... Microsoft Windows [Version 10.0.26100.4946] (c) Microsoft Corporation. Med enerett. C:\Users\rhh>"C:\Program Files\BrutalDev\.NET Assembly Strong-Name Signer\StrongNameSigner.Console.exe" -in "C:\Users\rhh\.nuget\packages\fastendpoints.security" ------------------------------------------------------------------- ---- Brutal Developer .NET Assembly Strong-Name Signer 3.6.1.0 ---- ------------------------------------------------------------------- Console application to sign .NET assemblies with a strong-name key and fix assembly references. 1. Loading assemblies... 2. Checking assembly references... Checking assembly references in 'C:\Users\rhh\.nuget\packages\fastendpoints.security\6.1.0\lib\net10.0\FastEndpoints.Security.dll'. Checking assembly references in 'C:\Users\rhh\.nuget\packages\fastendpoints.security\6.1.0\lib\net8.0\FastEndpoints.Security.dll'. Checking assembly references in 'C:\Users\rhh\.nuget\packages\fastendpoints.security\6.1.0\lib\net9.0\FastEndpoints.Security.dll'. Checking assembly references in 'C:\Users\rhh\.nuget\packages\fastendpoints.security\6.2.0\lib\net10.0\FastEndpoints.Security.dll'. Checking assembly references in 'C:\Users\rhh\.nuget\packages\fastendpoints.security\6.2.0\lib\net8.0\FastEndpoints.Security.dll'. Checking assembly references in 'C:\Users\rhh\.nuget\packages\fastendpoints.security\6.2.0\lib\net9.0\FastEndpoints.Security.dll'. 3. Strong-name unsigned assemblies... 4. Fix InternalVisibleToAttribute references... 5. Fix CustomAttributes with Type references... 6. Cleanup... System.ArgumentException: An item with the same key has already been added. ved System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) ved System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) ved System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer) ved Brutal.Dev.StrongNameSigner.SigningHelper.FixCustomAttributes(HashSet`1 allAssemblies, Dictionary`2 tempFilePathToInputOutputFilePairMap, Boolean& hasErrors) ved Brutal.Dev.StrongNameSigner.SigningHelper.SignAssemblies(IEnumerable`1 assemblyInputOutputPaths, String keyFilePath, String keyFilePassword, String[] probingPaths) ved Brutal.Dev.StrongNameSigner.Console.Program.SignAssemblies(Options options) ved Brutal.Dev.StrongNameSigner.Console.Program.Main(String[] args) C:\Users\rhh>

kerem

2026-02-25 21:30:38 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 21:30:38 +03:00

Author

Owner

@brutaldev commented on GitHub (Sep 1, 2025):

Fixed in version 3.6.2

@brutaldev commented on GitHub (Sep 1, 2025): Fixed in version [3.6.2](https://github.com/brutaldev/StrongNameSigner/releases/tag/v3.6.2)