Forbidden XML Schema constructs in WSDL of a web service
===

I am a Java developer who has created a rather big Web service that works nice with Java clients or other tools (Soap UI).

One of our clients wants to write a .NET client for the web service and uses the "add service reference" feature of VS2010. According to the client this does not work since our WSDL and XSD files use "Forbidden XML constructs" as defined in this [article][1]: 

The problem is that we have made heavy usage of xsd:attribute data in WSDL. 

So the question is: 
Is there a workaround to make .NET stub generation code compliant with WSDL/XSD files that contain xsd:attribute? Is there another .NET library for webservices that supports this feature?

Another question of mine would be why does Microsoft impose these limitations in the first place? Why xsd:attribute is a forbidden costruct in a web service??? Any clues on that?

Probably related: http://stackoverflow.com/questions/7000474/c-net-generating-web-service-reference-using-wsdl-from-xml-schema-problem


  [1]: http://blogs.msdn.com/b/sonuarora/archive/2007/06/16/contract-generation-from-wsdl-xml-schema-datacontractserializer-vs-xmlserializer.aspx