-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error signing output with public key from file 'x.snk' -- Assembly signing not supported #8409
Comments
This may be better reported in dotnet/sdk. not sure. |
This is strange. We do this ourselves all the time with our assemblies in the CLI repo: https://github.com/dotnet/cli/blob/release/2.0.0/src/dotnet/dotnet.csproj#L8-L10. Would it be possible for you to share a repro repo with us? Though, I see that this happens only on non-windows. if that's the case, you are probably missing this: |
Support for full signing on non-Windows in Roslyn is tracked by dotnet/roslyn#8210 |
@livarcocc if i set the Unfortunately, I can only provide the csproj file, so i am not sure it will be a big help. |
@livarcocc my bad, the public sign does the trick. I had kept the
could you please explain what will this PublicSign does? (or does not do) |
Awesome. Glad it worked. Closing this for now. if anything else comes up, just re-activate. |
@livarcocc yes no problem, do you mind explaining what this thanks |
@Jonathan34 Excellent question. There are consequences. Public signing is like delay signing: only the public key is needed and the binary is not actually signed with the private key. The only difference is a bit in the PE that allows most scenarios to run without registering for skip verification. However, since the binary is not actually fully signed, it cannot be installed to the GAC, cannot be used with shadow copying, and cannot be loaded in a partial trust context on full framework. See https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/public-signing.md There are plans to support full signing on non-Windows (dotnet/roslyn#8210), but the work has not been completed. |
Reason explained in this issue: https://github.com/dotnet/cli/issues/6911
GAC is the Global Assembly Cache for those who may not know. |
…ble VSTS build to succeed, else it fails with 'PFX signing not supported on .NET Core', per: https://github.com/dotnet/cli/issues/6911. Note, PFX signing is successful locally with VS2017, but unseccessful via VSTS netcore build; .NetCore projects are still very frail.
Reason explained in this issue: dotnet/cli#6911
Reason explained in this issue: dotnet/cli#6911
Since dotnet/roslyn#8210 is now completed, I assume this works now? |
I am moving a .net full project to .net standard 2.0 with a.netcore 2.0 unit test projects.
They both use a snk to strongly sign the binaries.
When building the .net standard 2.0 project, i get:
Any idea?
Environment data
dotnet --info
output:The text was updated successfully, but these errors were encountered: