starred/StrongNameSigner
1
0
Fork 0
mirror of https://github.com/brutaldev/StrongNameSigner.git synced 2026-04-25 03:16:10 +03:00
Code Issues Projects Releases Packages Wiki Activity

[GH-ISSUE #72] Writing mixed-mode assemblies is not supported #62

New issue
Closed
opened 2026-02-25 21:30:35 +03:00 by kerem · 3 comments
kerem commented 2026-02-25 21:30:35 +03:00
Owner
Copy link

Originally created by @kuhnboy on GitHub (Sep 27, 2022).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/72

Originally assigned to: @brutaldev on GitHub.

Running into this error with mixed-mode assemblies with 3.1.0.

1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error : NotSupportedException: Writing mixed-mode assemblies is not supported
1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error :    at Mono.Cecil.ModuleWriter.Write(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters)
1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error :    at Mono.Cecil.ModuleWriter.WriteModule(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters)
1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error :    at Mono.Cecil.ModuleDefinition.Write(String fileName, WriterParameters parameters)
1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error :    at Brutal.Dev.StrongNameSigner.AssemblyInfo.Save(String assemblyPath, Byte[] keyPair)
1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error :    at Brutal.Dev.StrongNameSigner.SigningHelper.SignAssemblies(IEnumerable`1 assemblyInputOutputPaths, String keyFilePath, String keyFilePassword, String[] probingPaths)
1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error :    at Brutal.Dev.StrongNameSigner.AutomaticBuildTask.Execute()
1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error :

It is implied that this is fixed in 3.1.0 (https://github.com/brutaldev/StrongNameSigner/pull/67)

Originally created by @kuhnboy on GitHub (Sep 27, 2022). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/72 Originally assigned to: @brutaldev on GitHub. Running into this error with mixed-mode assemblies with 3.1.0. ``` 1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error : NotSupportedException: Writing mixed-mode assemblies is not supported 1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error : at Mono.Cecil.ModuleWriter.Write(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters) 1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error : at Mono.Cecil.ModuleWriter.WriteModule(ModuleDefinition module, Disposable`1 stream, WriterParameters parameters) 1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error : at Mono.Cecil.ModuleDefinition.Write(String fileName, WriterParameters parameters) 1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error : at Brutal.Dev.StrongNameSigner.AssemblyInfo.Save(String assemblyPath, Byte[] keyPair) 1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error : at Brutal.Dev.StrongNameSigner.SigningHelper.SignAssemblies(IEnumerable`1 assemblyInputOutputPaths, String keyFilePath, String keyFilePassword, String[] probingPaths) 1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error : at Brutal.Dev.StrongNameSigner.AutomaticBuildTask.Execute() 1> <<redacted>>\packages\Brutal.Dev.StrongNameSigner.3.1.0\build\Brutal.Dev.StrongNameSigner.targets(6,5): error : ``` It is implied that this is fixed in 3.1.0 (https://github.com/brutaldev/StrongNameSigner/pull/67)
kerem 2026-02-25 21:30:35 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-25 21:30:35 +03:00
Author
Owner
Copy link

@brutaldev commented on GitHub (Sep 27, 2022):

@kuhnboy Mono.Cecil is clearly not happy about the assembly you are using.
You will need to provide me with the assembly you are trying to sign that causes that exception so I can reproduce and attempt to fix it.

The issue you refer to was the detection of mixed-mode and skipping them. Signing will not be supported for them, but if it can be detected they can be skipped and the error can be avoided. Whatever assembly you are trying to sign there clearly fails to identify as being mixed-mode so it attempts to sign it and fails.

<!-- gh-comment-id:1260023928 --> @brutaldev commented on GitHub (Sep 27, 2022): @kuhnboy Mono.Cecil is clearly not happy about the assembly you are using. You will need to provide me with the assembly you are trying to sign that causes that exception so I can reproduce and attempt to fix it. The issue you refer to was the detection of mixed-mode and skipping them. Signing will not be supported for them, but if it can be detected they can be skipped and the error can be avoided. Whatever assembly you are trying to sign there clearly fails to identify as being mixed-mode so it attempts to sign it and fails.
kerem commented 2026-02-25 21:30:35 +03:00
Author
Owner
Copy link

@kuhnboy commented on GitHub (Sep 27, 2022):

Ok thanks. So the correct answer is:

  • Skipping mixed mode assemblies was broken but should be fixed in 3.1.1.
  • There is no support for mixed mode assembly signing due to Cecil not supporting it.
<!-- gh-comment-id:1260178381 --> @kuhnboy commented on GitHub (Sep 27, 2022): Ok thanks. So the correct answer is: - Skipping mixed mode assemblies was broken but should be fixed in 3.1.1. - There is no support for mixed mode assembly signing due to Cecil not supporting it.
kerem commented 2026-02-25 21:30:35 +03:00
Author
Owner
Copy link

@brutaldev commented on GitHub (Oct 17, 2022):

Fixed and deployed to NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.1.1

<!-- gh-comment-id:1280769547 --> @brutaldev commented on GitHub (Oct 17, 2022): Fixed and deployed to NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.1.1
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v3.6.5
v3.6.4
v3.6.3
v3.6.2
v3.6.1
v3.6.0
v3.5.1
v3.5.0
v3.4.0
v3.3.3
v3.3.2
v3.3.1
v3.3.0
v3.2.1
v3.2.0
v3.1.1
v3.1.0
v2.9.1
v2.9.0
2.7.1
2.7.0
2.6.0
2.4.0
v2.3.0
v2.2.0
v2.1.4
v2.1.3
v2.1.2
v2.1.0
v2.0.0
v1.8.0
v1.7.0
v1.6.1
v1.5.1-2
v1.5.0
v1.5.1
v1.4.9
v1.4.8
v1.4.7
v1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4
v1.3.0.0
1.2
Labels
Clear labels   
bug

   
duplicate

   
duplicate

   
enhancement

   
invalid

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
wontfix
No labels
bug
duplicate
duplicate
enhancement
invalid
pull-request
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/StrongNameSigner#62
No description provided.