Okay... I don't know what the solution to this problem is but I found a "workaround".
Basically, VB.net didn't like the "soapenc:string" in the WSDL... so I viewed the WSDL, saved it to a file, replaced "soapenc:string" with the original "xsd:string". Of course, to make our .NET app look at the correct WSDL would require an actual release of the product. Since that's a lot of trouble, I downloaded and configured ISAPI Rewrite lite, and redirected those WSDL requests to the actual wsdl file. All is well in my world again. Now to comment the code so I remember that if I make any changes to the web service that I have to save the WSDL again ;) Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:229769 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
