Additionally, the .NET Framework 2.0 managed assembly may take longer than usual to load because of various other settings. For example, the .NET Framework 2.0 managed assembly may take longer than usual to load because of the network configuration.
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 2.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
PrerequisitesYou must have the .NET Framework 2.0 installed before you apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|File name||File version||File size||Date||Time|
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.
The generatePublisherEvidence configuration setting will be available in the version of the .NET Framework that follows the Microsoft .NET Framework 3.0.
To create an application configuration file that contains this configuration setting, follow these steps:
- Create a file, and then name the file the <ApplicationName>.exe.config file.
- In a text editor, open the file that you created in step 1.
- Add the following code to the file.
<?xml version="1.0" encoding="utf-8"?>
- Save the changes to the file.
Identyfikator artykułu: 936707 — ostatni przegląd: 05.04.2012 — zmiana: 1