Bit of a long shot this, but we've had a company working with us reporting that .NET couldn't interpret the WSDL for a webservice we've published. We've not done anything particularly special, functions consisting of a single XML parameter in returning an XML document (what the XML is is of course a different issue but we're not there yet), and as far as we can see the WSDL looks perfectly fine to us, so we're not entirely sure we understand what this other company is talking about.

Just to be sure we haven't done anything odd with regards to hosting, I've run the WSDL through http://xmethods.net/ve2/WSDLAnalyzer.po and http://www.validwsdl.com/ which proves that not only can those external sites see our server OK but that WSDL document itself can be parsed without issue (which it does seem to be).

I know in a perfect world WSDL is WSDL, a document specifically for the unambiguous describing of methods. Having said that, is anyone aware of any discrepancies between the way DA have interpreted things that MS may have interpreted differently? Some kind of edge case where a perfectly valid document isn't interpreted correctly by .NET or even a scenario where a VDF generated WSDL may leave room for be misparsed?


FWIW, especially after having looked at the online validators, I'm not entirely sure we have a problem at all and the cause is something else entirely, but occasionally you do begin to doubt yourself.