diff --git a/docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md b/docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md index c40a93307e858..9ccbc3302fa3d 100644 --- a/docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md +++ b/docs/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element.md @@ -54,10 +54,7 @@ Specifies whether the runtime creates 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 evidence for the assembly. However, by default, most applications do not need evidence. Standard CAS policy does not rely on the . 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 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 evidence for the assembly. However, by default, most applications do not need evidence. Standard CAS policy does not rely on the . 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 in a partial-trust environment. (Demands for identity permissions always succeed in a full-trust environment.) > [!NOTE] > We recommend that services use the `` 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.