Microsoft KB Archive/896181

Knowledge Base

FIX: You receive an "Unable to generate a temporary class" error message in Internet Explorer when you try to open an ASP.NET page that consumes Web services in the .NET Framework 1.1

Article ID: 896181

Article Last Modified on 3/23/2007

---

APPLIES TO

• Microsoft .NET Framework 1.1

---

SYMPTOMS

Consider the following scenario. In the Microsoft .NET Framework 1.1, you try to open a Microsoft ASP.NET page that consumes Web services. When you do this, the .NET Framework cannot generate temporary serialization assemblies for the Web service, and you receive an error message that is similar to the following in Microsoft Internet Explorer:

InvalidOperationException: Unable to generate a temporary class (result=1). error CS0011: Referenced class '_ASP.login_ec_ascx' has base class or interface 'System.Web.UI.UserControl' defined in an assembly that is not referenced. You must add a reference to assembly 'System.Web'.

CAUSE

This problem occurs because the temporary serialization assemblies do not reference the System.Web assembly. This behavior causes the Web service to fail at run time.

RESOLUTION

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 Microsoft .NET Framework 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:

http://support.microsoft.com/contactus/?ws=support

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

This hotfix requires the .NET Framework 1.1 Service Pack 1 (SP1).

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other software updates.

Hotfix 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 tool in Control Panel.

   Date         Time   Version        Size       File name
   ---------------------------------------------------------------------
   23-Mar-2005  22:42  1.1.4322.2310    573,440  System.web.services.dll  
   23-Mar-2005  22:42  1.1.4322.2310  1,355,776  System.xml.dll

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Steps to reproduce the problem

1. In Microsoft Internet Information Services (IIS), create a virtual directory.
2. Create a new .aspx page that is named Repro.aspx.

3. Add the following code example to Repro.aspx.

   <script runat="server" language="C#">
   
   /// <remarks/>
   [System.Diagnostics.DebuggerStepThroughAttribute()]
   [System.ComponentModel.DesignerCategoryAttribute("code")]
   [System.Web.Services.WebServiceBindingAttribute(Name="BSHSoap", Namespace="https://members.microsoft.nl/BSHWebService/")]
   public class BSH : System.Web.Services.Protocols.SoapHttpClientProtocol {
   
   /// <remarks/>
   public BSH() {
   
   }
   
   /// <remarks/>
   [System.Web.Services.Protocols.SoapDocumentMethodAttribute("https://members.microsoft.nl/BSHWebService/Login", RequestNamespace="https://members.microsoft.nl/BSHWebService/", ResponseNamespace="https://members.microsoft.nl/BSHWebService/", Use=System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)]
   public System.Data.DataSet Login(System.Guid AppId, string EmailAddress, string Password) {
   object[] results = this.Invoke("Login", new object[] {
   AppId,
   EmailAddress,
   Password});
   return ((System.Data.DataSet)(results[0]));
   } 
   
   [System.Web.Services.Protocols.SoapDocumentMethodAttribute]
   public void TestMe(System.Web.HttpCacheability xxx) {
   this.Invoke("TestMe", new object[] { xxx });
   return;
   } 
   }
   </script>
   
   
   <script runat="server">
   
   private void Page_Load(object sender, System.EventArgs e)
   {
   BSH bsh = new BSH();
   
   }
   
   override protected void OnInit(EventArgs e)
   {
   this.Load += new System.EventHandler(this.Page_Load);
   base.OnInit(e);
   }
   </script>

4. Save Repro.aspx in the IIS virtual directory that you created in step 1.
5. Open Repro.aspx in Internet Explorer.
   
   You receive the error message that is mentioned in the "Symptoms" section.

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: fail

Keywords: kbwinserv2003sp2fix kbqfe kbhotfixserver kbfix kbbug KB896181

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.