Remove inaccurate .NET Framework 4 note from generatePublisherEvidence documentation

[Copilot]

The documentation contained a note claiming <generatePublisherEvidence> has no effect on assembly load times in .NET Framework 4+. This contradicts both user-reported behavior (30-40s delays prevented by this setting in .NET 4.7 apps behind HTTP proxies) and the document's own recommendation to use this element for service startup performance.

Changes

• Removed the incorrect note stating the element has no effect in .NET Framework 4 and later
• Retained the recommendation that services use this element to improve startup performance and avoid timeouts

The documentation now presents consistent information without conflicting statements about the element's effectiveness.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Update/remove the .NET 4 note saying "" has no effect on assembly load times.</issue_title>
<issue_description>In the Remarks section of the generatePublisherEvidence element page. there is a big blue warning note saying "In the .NET Framework 4 and later, this element has no effect on assembly load times."

That statement is not true (or at least, is not always true).

In our .NET 4.7 desktop app, we have needed to add <generatePublisherEvidence enabled="false"/> to the *.exe.config files for all of our signed executables, in order to prevent 30-40 launch delays when a system is behind an HTTP proxy and the servers hosting certificate revocation lists are not reachable.

Without the magic XML in the App.config file, the assembly is delayed for 40-seconds while the OS tries to reach out to OCSP and CRL endpoints to figure out if the app's certificate has been invalidated.

Some of our executables are Windows Services, so causing these startup delays is definitely something to avoid. In fact there is already a note saying "We recommend you disable this feature for Windows services", which seems to go directly against the "This setting doesn't apply to .NET 4 or greate" note.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4a579a8e-74fd-a86e-8e80-78719c9b1b4e
• Version Independent ID: 56f18e1d-69fe-4423-23ad-29d7d5bce914
• Content: <generatePublisherEvidence> Element
• Content Source: docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md
• Product: dotnet-framework
• GitHub Login: @rpetrusha
• Microsoft Alias: ronpet</issue_description>

<agent_instructions>The note about .NET 4 can be removed.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@BillWagner Thank you for pointing this out @DougSchmidt-AI

We've added it to our backlog.</comment_new>
<comment_new>@dotnet-bot
This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.</comment_new>
<comment_new>@BillWagner
reopening per comment.</comment_new>

• Fixes Update/remove the .NET 4 note saying "<generatePublisherEvidence>" has no effect on assembly load times. #7351

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

Internal previews

📄 File	🔗 Preview link
docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md	docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element

[Copilot]

Pull request overview

This PR removes an inaccurate note from the <generatePublisherEvidence> element documentation that claimed the element has no effect on assembly load times in .NET Framework 4 and later. The issue reporter documented real-world evidence of 30-40 second delays in .NET 4.7 applications that were resolved by using this configuration element, directly contradicting the note. The removal resolves an internal contradiction where the document both claimed the element had no effect and recommended its use for service startup performance.

Changes:

• Removed the incorrect NOTE stating the element has no effect in .NET Framework 4 and later
• Retained all other documentation, including the recommendation for services to use this element