Last post Feb 12, 2019 09:38 PM by melloyello
Feb 11, 2019 03:52 PM|melloyello|LINK
Trying to connect to a third-party SOAP web service with .NET Core 2.0 behind a proxy. With .NET Core 2.x I have the only option to create a WCF Web Service as a Connected service, however the Proxy objects generated are not same as with full frame .NET
Web Service Reference. It creates only async methods (which I don't mind).
With .NET Core 2.x I am getting an exception: ServiceModel.CommunicationException: Unrecognized message version when I call a method on the proxy client after setting basic authentication credentials from code
ServiceModel.CommunicationException: Unrecognized message version
Everything works fine with basic authentication from a full frame .NET console program (VS 2017) after creating a Web Service Reference. My company has moved to .net core and this is a problem we need a solution
Feb 11, 2019 07:54 PM|bruce (sqlwork.com)|LINK
if you are really talking about access thru a proxy server that requires authentication, see:
Feb 12, 2019 05:45 AM|Edward Z|LINK
>>Trying to connect to a third-party SOAP web service with .NET Core 2.0 behind a proxy.
If you generated the client code without behinding a proxy, will it work?
>> however the Proxy objects generated are not same as with full frame .NET Web Service Reference.
What is the difference between .net and .net core generated code.
What is the SOAP Web service? Is it WCF Soap service or asmx service?
Feb 12, 2019 09:38 PM|melloyello|LINK
Thanks everyone for trying to help, my binding end point was incorrect, I had by mistake put the wsdl uri.