Skip to content

Remove inaccurate .NET Framework 4 note from generatePublisherEvidence documentation #51521

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.

Sign up for GitHub

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

Merged
meaghanlewis merged 2 commits into from
Feb 6, 2026
Merged

Remove inaccurate .NET Framework 4 note from generatePublisherEvidence documentation #51521

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c1d64a2
Initial plan
Copilot Feb 5, 2026
386cf1c
Remove inaccurate .NET Framework 4 note from generatePublisherEvidenc…
Copilot Feb 5, 2026
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
5 changes: 1 addition & 4 deletions ...amework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,10 +54,7 @@ Specifies whether the runtime creates <xref:System.Security.Policy.Publisher> ev

## Remarks

> [!NOTE]
> In the .NET Framework 4 and later, this element has no effect on assembly load times.

The common language runtime (CLR) tries to verify the Authenticode signature at load time to create <xref:System.Security.Policy.Publisher> evidence for the assembly. However, by default, most applications do not need <xref:System.Security.Policy.Publisher> evidence. Standard CAS policy does not rely on the <xref:System.Security.Policy.PublisherMembershipCondition>. You should avoid the unnecessary startup cost associated with verifying the publisher signature unless your application executes on a computer with custom CAS policy, or is intending to satisfy demands for <xref:System.Security.Permissions.PublisherIdentityPermission> in a partial-trust environment. (Demands for identity permissions always succeed in a full-trust environment.)
The common language runtime (CLR) tries to verify the Authenticode signature at load time to create <xref:System.Security.Policy.Publisher> evidence for the assembly. However, by default, most applications do not need <xref:System.Security.Policy.Publisher> evidence. Standard CAS policy does not rely on the <xref:System.Security.Policy.PublisherMembershipCondition>. You should avoid the unnecessary startup cost associated with verifying the publisher signature unless your application executes on a computer with custom CAS policy, or is intending to satisfy demands for <xref:System.Security.Permissions.PublisherIdentityPermission> in a partial-trust environment. (Demands for identity permissions always succeed in a full-trust environment.)

> [!NOTE]
> We recommend that services use the `<generatePublisherEvidence>` element to improve startup performance. Using this element can also help avoid delays that can cause a time-out and the cancellation of the service startup.
Expand Down
Loading