basicHttp is SOAP 1.1, wsHttp is SOAP 1.2 (they're quite different, esp. when it comes to SOAP faults)
basic is - very basic. It's compatible with old-style ASMX ASP.NET webservices and just about any other web service stack out there
basic is very limited in its security settings
wsHttp is an implementation of a gazillion WS-* standards, and offers much more features: security, reliable messaging, transaction support, duplex communications and a whole host more.
wsHttp is the much "heavier" and more extensive protocol, less compatible, less nimble
I know this has been asked quite a few times, and trust me I've been looking at and trying many of them for half the afternoon, but still cannot get past this.
I'm trying to submit some form contents (which …
I've got a WCF Service running on my local IIS server. I've added it as a service reference to a C# Website Project and it adds fine and generates the proxy classes automatically.
However, when I try and call any …
I'm testing out some WCF services that send objects with Guids back and forth. In my web app test code, I'm doing the following:
var responseObject = proxy.CallService(new RequestObject
{
Data = "misc. data",
Guid = new Guid()
});
For some reason, the …