Article ID: 327071 - View products that this article applies to.
This article was previously published under Q327071
Qualified attributes in an XML schema do not result in the correct declarations in the XSD or WSDL-generated code.
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 fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNOTE: 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 typical 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 fix 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.
Date Time Version Size File name Platform -------------------------------------------------------------------------- 31-Jul-2002 11:27 1.0.3705.299 1,298,432 System.Xml.dll i386
To work around this problem, manually add the XmlSchemaForm.Qualified declarations to the generated code.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
By default, the .NET Framework assumes that non-declared attributes are Unqualified. This can create errors when an attribute is not declared as a qualified attribute.
Steps to Reproduce the BehaviorTo reproduce the problem, follow these steps:
After you apply the hotfix, the generated code is the following:
Article ID: 327071 - Last Review: February 12, 2007 - Revision: 2.5
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Contact us for more help