Microsoft KB Archive/823641

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:07, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 823641

Article Last Modified on 10/25/2005



APPLIES TO

  • Microsoft .NET Framework 1.1




SYMPTOMS

The following problems are fixed in this hotfix package:

  • When the Web Services Description Language (WSDL) imports a schema that includes multiple schemas by using the xsd:include element, and when these schemas include any command schema, the WSDL tool (Wsdl.exe) cannot generate the proxy for the Web service.
  • If the WSDL contains more than one binding, and if all the bindings use SOAP headers, Wsdl.exe may generate an incorrect proxy. This behavior occurs when you use the Wsdl.exe tool to create the Web service proxy. The proxy must have the SOAP header field generated in all the classes. Instead, the proxy has the SOAP header field generated only for the first class.

For a Microsoft .NET Framework 1.1 with Microsoft Visual Studio .NET 2003 version of this article version of this article, see 823639.

RESOLUTION

Note When you apply this hotfix, you must also apply one of the hotfixes that is described in the following Microsoft Knowledge Base articles.

The .NET Framework 1.1

822411 FIX: XML Messaging with the .NET Framework 1.1 hotfix rollup


The .NET Framework 1.1 Service Pack 1

892202 FIX: The WSDL tool cannot successfully generate the proxy when the WSDL file imports multiple schemas that in turn import a common schema in the .NET Framework 1.1 Service Pack 1


If you have a later version of the .NET Framework installed, or the computer is running Microsoft Windows Server 2003 Service Pack 1 or a later service pack, no additional hotfix is required.

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

You must have the .NET Framework 1.1 or the .NET Framework 1.1 Service Pack 1 installed, or the computer must be running Windows Server 2003. Additionally, you must have the .NET Framework 1.1 Software Development Kit (SDK) installed.

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
   ---------------------------------------------------
   24-Jun-2003  12:20  1.1.4322.915  65,536  Wsdl.exe
   24-Jun-2003  12:20  1.1.4322.915  53,248  Xsd.exe

STATUS

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

MORE INFORMATION

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


Keywords: kbbug kbfix kbqfe kbhotfixserver KB823641