Speed Up Citrix Receiver For Web – Storefront 1.x – 2.x (First launch)

To fix this we need to add the generatePublisherEvidence configuration setting to the .NET Framework 2.0 to disable signature verification in a .NET Framework 2.0 managed application.  You can use this configuration setting in an application configuration file.  To do this, add the following code to the <ApplicationName>.exe.config file for the .NET Framework 2.0 managed application:

<configuration>
<runtime>
<generatePublisherEvidence enabled=”false”/>
</runtime>
</configuration>

1. Open Aspnet.config for editing in the following directory:If your application is hosted in IIS, change one of the following:
   • C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.config
   • C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config

   Note On x64 machines, you must also change one of the following:

   • C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet.config
   • C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config

Add the following lines to your Aspnet.config file: <generatePublisherEvidence enabled=”false”/>

When you disable signature verification, the .NET Framework 2.0 managed application starts faster.

Note When you disable signature verification, the .NET Framework 2.0 managed application no longer receives publisher evidence.  This behavior affects the .NET Framework 2.0 managed application only when you use publisher evidence or when you use the PublisherIdentityPermission class.