Click or drag to resize

Signed assemblies load slowly

The common language runtime (CLR) tries to verify the Authenticode signature at load time to create publisher evidence for the assembly. However, by default, most applications do not need publisher evidence since a standard code access security (CAS) policy does not rely on the publisher evidence. You should avoid the unnecessary startup time associated with verifying the publisher signature unless your application executes on a computer with a custom CAS policy or you need to satisfy security requirements in a partial-trust environment. (Demands for identity permissions always succeed in a full-trust environment.)

We recommend that you disable the <generatePublisherEvidence> element in the .NET Framework configuration files to improve startup performance. Because this involves both the client computers as well as servers, we recommend that this only be done on those computers that actually experience inadequate load times. To do this, you can add a setting to the <ApplicationName>.exe.config file for the application. Create the file if it does not yet exist in the same folder as the executable.

The following example shows the setting to add to the PowerUserU.exe.config, OfficeClient2U.exe.config, ConfiguratorU.exe.config, and AMHookTrayU.exe.config files.

Note Note

Meridian Enterprise versions released after version 2012 install configuration files that include this setting by default.

Copy
<configuration>
    <runtime>
        <generatePublisherEvidence enabled="false"/>
    </runtime>
</configuration>

To configure the setting for all ASP.NET web applications or for all applications on a computer, add the respective setting to the following files:

On 32-bit computers:

On 64-bit computers:

When you disable signature verification, the .NET Framework 2.0 managed application starts faster. For information, see the following Microsoft resources.

See Also