If your Microsoft ASP.NET Web application makes calls to XML Web services, you may notice in Task Manager that an instance of Csc.exe runs briefly the first time that the application calls each XML Web service. This is typical behavior.
However, depending on the memory usage of the application and the number of different Web services that the application calls, Csc.exe may also run again after each Web service and each ASP.NET page has been called one time. In extreme cases, this behavior can cause poor performance of the application.
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, Microsoft recommends that you wait for the next .NET Framework 1.0 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.
The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
This problem was corrected in the Microsoft .NET Framework 1.1.
ASP.NET and Web services in the Microsoft .NET Framework use dynamic compilation of code. ASP.NET uses this technique to compile .aspx or .asmx pages that have inline code in them. By default, the resulting assembly is cached in the Temporary ASP.NET Files folder. To compile these pages, the .NET Framework runs the Csc.exe file, the Vbc.exe file, or another command line compiler, depending on the .NET-compatible programming language that is used in the page.
When an application calls Web services, the .NET Framework automatically generates and compiles client proxy classes. The .NET Framework generates these classes in C# and then runs the Csc.exe compiler to compile these classes. The resulting assemblies are cached in memory in the ASP.NET cache.
Before you apply this hotfix, these generated assemblies may be displaced from the cache because of memory pressure. Therefore, the .NET Framework must recompile these assemblies again the next time that the application requires them.
For additional information about the terminology that is used to describe Microsoft product updates, 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