Skip to content
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

Mention NetFx40_LegacySecurityPolicy for PublicSign #99184

Merged
merged 3 commits into from
Mar 8, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Update public-signing.md
KirillOsenkov authored Mar 2, 2024
commit f47526ff3906527153f5cdab9b964f553fc7a338
1 change: 1 addition & 0 deletions docs/project/public-signing.md
Original file line number Diff line number Diff line change
@@ -17,6 +17,7 @@ Known issues when debugging and testing public signed assemblies on .NET Framewo
- You will not be able to load the assembly in an AppDomain where shadow copying is turned on.
- You will not be able to load the assembly in a partially trusted AppDomain
- You will not be able to pre-compile ASP.NET applications
- You will not be able to load the assembly if the `app.config` file specifies `<configuration`/`<runtime>`/`<NetFx40_LegacySecurityPolicy enabled="true" />`
KirillOsenkov marked this conversation as resolved.
Show resolved Hide resolved

The `corflags.exe` tool that ships with the .NET Framework SDK can show whether a binary is delay-signed or strong-named. For a delay-signed assembly it may show: