Hi,
I've succesfully created a standard interface to a well known Document Management System using SOAP-XML. The standard WSDL issued by the manufacturer contains a basic set of classes including methods and properties.
So far so good. However, the DMS is based on a standard model which means that customers are free to add non-standard features. For example, the method "GetDocument" returns a document object with several properties with corresponding values. During
reception of the message, VB.Net raises an execption stating that there is an invalid property value in the message. This is correct, the value is not in the standard WSDL (used in our development service reference) but is available in the .asmx file on the
customers webserver. I am looking for an elegant and flexible way to deal with non-standard messages at my customers' sites without recompiling the application.