diff options
| author | Kirill Osenkov <github@osenkov.com> | 2024-03-01 18:18:18 -0800 |
|---|---|---|
| committer | Kirill Osenkov <github@osenkov.com> | 2024-03-01 18:18:18 -0800 |
| commit | af7a50a8726b7e964805391f9a32f71da2d3f244 (patch) | |
| tree | afccd89304ab1e02b4788a186763bb42cffe2d8f | |
| parent | 9071e7a1322d05c51238c1c02148aa3c3f288736 (diff) | |
Add missing angle bracketdev/kirillo/public-sign-legacy
| -rw-r--r-- | docs/project/public-signing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/project/public-signing.md b/docs/project/public-signing.md index 3d2b6ca1b04d..c9482e79d532 100644 --- a/docs/project/public-signing.md +++ b/docs/project/public-signing.md @@ -17,7 +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 may not be able to load the assembly if the `app.config` file specifies `<configuration`/`<runtime>`/`<NetFx40_LegacySecurityPolicy enabled="true" />` +- You may not be able to load the assembly if the `app.config` file specifies `<configuration>`/`<runtime>`/`<NetFx40_LegacySecurityPolicy enabled="true" />` 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: |