Of course. Gordon is 1000% correct in noting that .NET DataSets will not interoperate with any other toolkit and questioning the author's motives. As Tim said in the other articles I listed "Consumers of this WSDL definition are meant to understand the special significance of this "well-known" URI—it is the four-part strong name of a specific runtime assembly included in the .NET Framework. This style of WSDL is great for clients that are implemented using .NET Remoting because they can generate a proxy assembly with the right information for marshaling. However, for other Web service toolkits—including ASP.NET—that do not understand this URI and expect to find a schema definition for the DataSet type, this WSDL will be useless."
I wanted to list the article for completeness next to the better MSDN articles for those in a limited Intranet Microsoft type of solution who may want to do this internally. But yes, its really bad for Interop!
7:36:43 PM 
|
