BUG: Incorrect proxy is generated when the WSDL file contains multiple bindings (816636)
The information in this article applies to:
- Microsoft Web Services (included with the .NET Framework 1.1)
- Microsoft Web Services (included with the .NET Framework) 1.0
- Microsoft Visual Basic .NET (2003)
- Microsoft Visual Basic .NET (2002)
- Microsoft Visual C# .NET (2003)
- Microsoft Visual C# .NET (2002)
SYMPTOMSYou can generate a proxy class for your Web Service
Description Language (WSDL) file that has multiple bindings. All the bindings
use SOAP headers. In the SoapHeaderAttribute of the generated proxy class, you may find that only the first
binding class has all the required parameters. The remaining classes may not
have all the expected parameters in the SoapHeaderAttribute. WORKAROUNDTo work around this problem, you can manually add the
parameters to the SoapHeaderAttribute for the classes that are missing parameters. An example is
described in the "More Information" section of this article.STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are
listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 9/13/2005 |
|---|
| Keywords: | kbvs2002sp1sweep kbBug kbCodeGen kbXML kbWebServices KB816636 kbAudDeveloper |
|---|
|