Microsoft KB Archive/839092

From BetaArchive Wiki

Article ID: 839092

Article Last Modified on 5/21/2007



APPLIES TO

  • Microsoft .NET Framework 1.1




SYMPTOMS

When you deploy your Microsoft .NET Framework 1.1 application that is hosted on a Web site, you may experience performance problems when you load the application. These problems occur when the NeutralResourcesLanguageAttribute class is not added to the third-party satellite assemblies that are used by your application.

CAUSE

This problem occurs when the .NET Framework 1.1 runtime must probe the third-party satellite assemblies for resources. When the third party has not added the NeutralResourcesLanguageAttribute class to the assembly and you do not have access to the source code to add the attribute, the runtime probes for resources. For executables that are hosted on Web sites, this probing occurs over the Web and can negatively affect application performance.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for the .NET Framework 1.1. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

885055 How to obtain Microsoft .NET Framework 1.1 Service Pack 1


Hotfix information

If you cannot install the .NET Framework 1.1 SP1 in your environment, a supported hotfix is available for the .NET Framework 1.1.

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The 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.

   Date         Time   Version        Size       File name
   ---------------------------------------------------------------
   17-Apr-2004  03:32  1.1.4322.1031     77,824  Corperfmonext.dll  
   17-Apr-2004  03:29  1.1.4322.1031    282,624  Fusion.dll       
   17-Apr-2004  03:29  1.1.4322.1031    311,296  Mscorjit.dll     
   17-Apr-2004  03:32  1.1.4322.1031    102,400  Mscorld.dll      
   19-Apr-2004  07:23  1.1.4322.1031  2,093,056  Mscorlib.dll     
   17-Apr-2004  03:22                    10,756  Mscorlib.ldo
   17-Apr-2004  03:30  1.1.4322.1031  2,502,656  Mscorsvr.dll     
   17-Apr-2004  03:31  1.1.4322.1031  2,490,368  Mscorwks.dll     

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in the .NET Framework 1.1 Service Pack 1.

MORE INFORMATION

After you apply this hotfix, you must use a config file to limit resource probing of satellite assemblies. To do this, create a config file for each application that you deploy. Because of limitations in changes that could be applied in the servicing release, you must add a config section handler to your config file for the .NET Framework 1.1. In the .NET Framework 2.0, the config file is supported. However, you must remove three lines of code from the config file.. The following code example is a config file that specifies two satellite assemblies. When you upgrade from the .NET Framework 1.1 to the .NET Framework 2.0, remove the <configSections> lines of code from the config file, if they exist.

<?xml version ="1.0"?>
<configuration>
<!-- The following configSections handler is only necessary on the .NET Framework 1.1.
     You must delete the configSections code from the config file on the .NET Framework 2.0. -->
    <configSections>
        <section name="satelliteassemblies" type="System.Configuration.IgnoreSectionHandler, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowLocation="false" />
    </configSections>
    <satelliteassemblies>
        <assembly name="MyAssembly, Version=1.2.3.4, Culture=neutral, PublicKeyToken=null">
            <culture>en-US</culture>
            <culture>fr-FR</culture>
            <culture>de-CH</culture>
            <culture>es-MX</culture>
        </assembly>
        <assembly name="MyAssembly2, Version=1.2.3.4, Culture=neutral, PublicKeyToken=null">
            <culture>de-CH</culture>
            <culture>es-MX</culture>
        </assembly>
    </satelliteassemblies>
</configuration>

This is a per-application config file that lets you limit the satellite assembly probes for each assembly that may use the ResourceManager class independently of each other. For each assembly that is specified in the config file, you must provide the fully qualified assembly name. Then, you must provide a <culture/> tag for each culture that the ResourceManager class should probe for. If you do not specify a <culture/> tag, the ResourceManager class does not probe any satellite assemblies. Instead, the ResourceManager class uses the neutral resources that are located in the main assembly.

For additional information about how the runtime locates assemblies, visit the following Microsoft Developer Network (MSDN) Web site:

For more information about the satelliteassemblies section in the the ResourceManager class of the config file, visit the following MSDN Web site:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates



Additional query words: GAC DLL

Keywords: kbqfe kbhotfixserver kbnetframe110presp1fix kbbug kbfix kbprb KB839092