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 #92] [Bug]: Getting Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'mscorlib, Version=4.0.0.0 for x86 project #73

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

Originally created by @Smurf-IV on GitHub (Jan 20, 2023).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/92

image

Originally created by @Smurf-IV on GitHub (Jan 20, 2023). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/92 ![image](https://user-images.githubusercontent.com/2418812/213686174-918a0dd8-5c22-4b8d-a084-3ae35631fcb6.png)
kerem closed this issue 2026-02-25 21:30:36 +03:00
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@Smurf-IV commented on GitHub (Jan 20, 2023):

Info on those dll's
image
image
image
image

image

<!-- gh-comment-id:1398262649 --> @Smurf-IV commented on GitHub (Jan 20, 2023): Info on those dll's ![image](https://user-images.githubusercontent.com/2418812/213686494-eda05a27-609f-42a8-9fa0-7298a0cf092b.png) ![image](https://user-images.githubusercontent.com/2418812/213686560-40f0f6ef-099e-4c80-8b6e-6db428dd0362.png) ![image](https://user-images.githubusercontent.com/2418812/213686653-6df7fa80-da39-477e-92d7-db7ef4ddb45b.png) ![image](https://user-images.githubusercontent.com/2418812/213686711-e20adb5f-bd6c-4c3b-9f98-b03282720089.png) ![image](https://user-images.githubusercontent.com/2418812/213686911-2fb9ca7f-88ef-4bd0-afd5-3e1767b50c00.png)
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@Smurf-IV commented on GitHub (Jan 20, 2023):

Prior to applying strongNaming:
image

And the Log file:
image

<!-- gh-comment-id:1398268202 --> @Smurf-IV commented on GitHub (Jan 20, 2023): Prior to applying strongNaming: ![image](https://user-images.githubusercontent.com/2418812/213687625-a506647a-c7a1-4d0e-8d5e-bf75f7efa2e5.png) And the Log file: ![image](https://user-images.githubusercontent.com/2418812/213687994-b841c41a-f545-4534-9396-34d66d4b7160.png)
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@Chaoses-Ib commented on GitHub (Jan 20, 2023):

I have the same problem:

5. Fix CustomAttributes with Type references...
6. Cleanup...
Error strong-name signing: Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'

If it's caused by cleanup, can I force this error to be ignored and use the signed assemblies?

<!-- gh-comment-id:1398998925 --> @Chaoses-Ib commented on GitHub (Jan 20, 2023): I have the same problem: ``` 5. Fix CustomAttributes with Type references... 6. Cleanup... Error strong-name signing: Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' ``` If it's caused by cleanup, can I force this error to be ignored and use the signed assemblies?
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@brutaldev commented on GitHub (Jan 21, 2023):

It's actually happening in Fix CustomAttributes with Type references...

Some strange types get resolved there and this is a new feature from @nickrandolph
If someone can provide a reproducible sample I will attempt to fix this or can just change the code to ignore these errors and potentially miss fixing from custom attributes.

<!-- gh-comment-id:1399297570 --> @brutaldev commented on GitHub (Jan 21, 2023): It's actually happening in `Fix CustomAttributes with Type references...` Some strange types get resolved there and this is a new feature from @nickrandolph If someone can provide a reproducible sample I will attempt to fix this or can just change the code to ignore these errors and potentially miss fixing from custom attributes.
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@Smurf-IV commented on GitHub (Jan 22, 2023):

@brutaldev If you want help, then do not close the issue(s)

<!-- gh-comment-id:1399421993 --> @Smurf-IV commented on GitHub (Jan 22, 2023): @brutaldev If you want help, then do not close the issue(s)
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@Chaoses-Ib commented on GitHub (Jan 22, 2023):

Here is my output log after updating to v3.3.3:

5. Fix CustomAttributes with Type references...
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Windows.ThemeInfoAttribute': Failed to resolve assembly: 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Windows.ThemeInfoAttribute': Failed to resolve assembly: 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Resources.NeutralResourcesLanguageAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Security.SecurityRulesAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Windows.ThemeInfoAttribute': Failed to resolve assembly: 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Runtime.InteropServices.DefaultDllImportSearchPathsAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Runtime.InteropServices.DefaultDllImportSearchPathsAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Runtime.InteropServices.DefaultDllImportSearchPathsAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
6. Fix BAML references...
7. Save assembly changes...
   ...
   Failed to save assembly 'C:\...\build\Debug\DynamicExpresso.Core.dll': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
<!-- gh-comment-id:1399431047 --> @Chaoses-Ib commented on GitHub (Jan 22, 2023): Here is my output log after updating to v3.3.3: ``` 5. Fix CustomAttributes with Type references... Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Windows.ThemeInfoAttribute': Failed to resolve assembly: 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Windows.ThemeInfoAttribute': Failed to resolve assembly: 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Resources.NeutralResourcesLanguageAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Security.SecurityRulesAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Windows.ThemeInfoAttribute': Failed to resolve assembly: 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Runtime.InteropServices.DefaultDllImportSearchPathsAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Runtime.InteropServices.DefaultDllImportSearchPathsAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Runtime.InteropServices.DefaultDllImportSearchPathsAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' Failed to check custom attribute 'System.Diagnostics.DebuggableAttribute': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' 6. Fix BAML references... 7. Save assembly changes... ... Failed to save assembly 'C:\...\build\Debug\DynamicExpresso.Core.dll': Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' ```
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@brutaldev commented on GitHub (Jan 22, 2023):

Do the final signed files will still work though? I need a sample to test and fix this with, when it was first reported no-one could provide a sample since it always works when using a simple project. https://github.com/brutaldev/StrongNameSigner/issues/82

Provide a project/solution that reproduces this and I will be able to fix it.

<!-- gh-comment-id:1399471444 --> @brutaldev commented on GitHub (Jan 22, 2023): Do the final signed files will still work though? I need a sample to test and fix this with, when it was first reported no-one could provide a sample since it always works when using a simple project. https://github.com/brutaldev/StrongNameSigner/issues/82 Provide a project/solution that reproduces this and I will be able to fix it.
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@Smurf-IV commented on GitHub (Jan 23, 2023):

@brutaldev I can supply the files privately, as they belong to a commercial product

<!-- gh-comment-id:1399923606 --> @Smurf-IV commented on GitHub (Jan 23, 2023): @brutaldev I can supply the files privately, as they belong to a commercial product
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@brutaldev commented on GitHub (Jan 23, 2023):

@Smurf-IV Thanks, email me a link to the package or files that fail to werner@brutaldev.com
You do not need to include all files, just the ones that cause this issue to occur.

I've spent the morning looking into adding additional probing paths and creating assemblies with DebuggableAttribute and ThemeInfoAttribute attrbutes, x86 and Any CPU builds etc etc and cannot reproduce this.

<!-- gh-comment-id:1399926991 --> @brutaldev commented on GitHub (Jan 23, 2023): @Smurf-IV Thanks, email me a link to the package or files that fail to werner@brutaldev.com You do not need to include all files, just the ones that cause this issue to occur. I've spent the morning looking into adding additional probing paths and creating assemblies with `DebuggableAttribute` and `ThemeInfoAttribute` attrbutes, x86 and Any CPU builds etc etc and cannot reproduce this.
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@Smurf-IV commented on GitHub (Jan 23, 2023):

3.3.3 no longer "Goes boom" but it just fails to save instead:
image

<!-- gh-comment-id:1400304086 --> @Smurf-IV commented on GitHub (Jan 23, 2023): 3.3.3 no longer "Goes boom" but it just fails to save instead: ![image](https://user-images.githubusercontent.com/2418812/214046534-2c307ecc-4db6-4dc0-b04f-29340dad9235.png)
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@brutaldev commented on GitHub (Jan 23, 2023):

@Smurf-IV You're using a faulty SNK file there. The error is Keyset does not exist that prevents the saving and I can only imagine it's something wrong with your DelaySign.snk file that is used for the signing.

https://improveandrepeat.com/2018/12/how-to-fix-the-keyset-does-not-exist-cryptographicexception/

<!-- gh-comment-id:1400515293 --> @brutaldev commented on GitHub (Jan 23, 2023): @Smurf-IV You're using a faulty SNK file there. The error is `Keyset does not exist` that prevents the saving and I can only imagine it's something wrong with your DelaySign.snk file that is used for the signing. https://improveandrepeat.com/2018/12/how-to-fix-the-keyset-does-not-exist-cryptographicexception/
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@Smurf-IV commented on GitHub (Jan 24, 2023):

That file is generated via the following:

  • In a "Visual Studio command line", type

sn -p "########.pfx" DelaySign.snk

  • It will ask for the "CERT_PASSWORD" to be typed in

i.e. the ###.pfx file is not installed in either the developers machine or the build agent.

When running a clean build - only the Step 5 Failed ... error is displayed.
So I assume Step 7 is due to the files already being signed (by this tool)

<!-- gh-comment-id:1401526093 --> @Smurf-IV commented on GitHub (Jan 24, 2023): That file is generated via the following: - In a "Visual Studio command line", type > `sn -p "########.pfx" DelaySign.snk` - It will ask for the "CERT_PASSWORD" to be typed in i.e. the ###.pfx file is not installed in either the developers machine or the build agent. When running a clean build - only the Step 5 `Failed ...` error is displayed. So I assume Step 7 is due to the files already being signed (by this tool)
kerem commented 2026-02-25 21:30:36 +03:00
Author
Owner
Copy link

@brutaldev commented on GitHub (Jan 24, 2023):

@Smurf-IV What you are reporting now is a completely different issue to this one about resolving dependencies.
I've created a new issue for this: https://github.com/brutaldev/StrongNameSigner/issues/93

<!-- gh-comment-id:1401572818 --> @brutaldev commented on GitHub (Jan 24, 2023): @Smurf-IV What you are reporting now is a completely different issue to this one about resolving dependencies. I've created a new issue for this: https://github.com/brutaldev/StrongNameSigner/issues/93
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#73
No description provided.