Comments (13)
from strongnamesigner.
Prior to applying strongNaming:
from strongnamesigner.
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?
from strongnamesigner.
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.
from strongnamesigner.
@brutaldev If you want help, then do not close the issue(s)
from strongnamesigner.
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'
from strongnamesigner.
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. #82
Provide a project/solution that reproduces this and I will be able to fix it.
from strongnamesigner.
@brutaldev I can supply the files privately, as they belong to a commercial product
from strongnamesigner.
@Smurf-IV Thanks, email me a link to the package or files that fail to [email protected]
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.
from strongnamesigner.
3.3.3 no longer "Goes boom" but it just fails to save instead:
from strongnamesigner.
@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/
from strongnamesigner.
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)
from strongnamesigner.
@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: #93
from strongnamesigner.
Related Issues (20)
- Writing mixed-mode assemblies is not supported HOT 3
- Transitive dependencies from PackageReferences are not investigated/signed HOT 3
- Use NuGet package, but no automatic signing of assemblies HOT 2
- Use NuGet package, but no automatic signing of assemblies HOT 2
- Virus Detected on Chrome when downloading StrongNameSigner_Setup.exe HOT 1
- SDK style probjects supported? HOT 4
- Failed to resolve assembly: 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' HOT 12
- Fixing unsigned references in signed assemblies when signing unsigned assemblies - unhandled case? HOT 5
- [Bug]: When the GUI comes across a "Unsupported PDB deleted bitset is not empty" it stops processing HOT 1
- [Feature Request]: convert the "Unsupported PDB deleted bitset is not empty" Error to a warning, so that the commandline app does not report errors HOT 2
- [Feature Request]: Can the Gui state what file has been used to sign a binary HOT 1
- [Bug]: If strongnamer is already processing a file, then do not throw an error when it tries to open it again due to parallel builds
- [Change Request]: Please change the column named `Signed` to be `StrongNamed` HOT 1
- [Feature Request]: Have a column called `DigCert` to show if this binary also has been digitally signed HOT 2
- Keyset does not exist error when using custom SNK generated from PFX file HOT 3
- Does not work with VS 2022 started with Admin rights targeting .net 4.8 framework HOT 9
- Can not get it to work with .NET Standard 2.0 Project and Nuget Packages Scrypt.NET and CSVTextFieldParser HOT 2
- Fails to ignore package dlls if %NUGET_PACKAGES% is set to a different format of path. HOT 2
- Failed to resolve System.IO.FileAccess HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from strongnamesigner.