title: calling WCF services using SOAP
body: <p>I'm trying to test a WCF service without creating a WCF client.  I have similar code/issues as presented <a href="https://stackoverflow.com/a/1643025/1397017">here</a>.</p>
  
  <p>I want full control on the SOAP payload so I want to be able to issue my own web requests/responses and substitute my own XML as the parameters into any method.  I also want the return SOAP XML exactly as is, without creating response objects, fault exception objects, etc.</p>
  
  <p>As a point of reference, I want to do exactly what <a href="http://www.soapui.org/" rel="nofollow noreferrer">SoapUI</a> is doing at the point you click the execute button and get the response back. I'm only assuming that SoapUI is NOT creating a WCF client, building the request and calling the method, but rather issuing a full SOAP call to the WCF service and displaying the result. </p>
  
  <p>In answer to the questions in the comments, the reason I don't want to create a WCF client is that I want to be insulated from any and all changes to the service, not have to rebuild references, modify my own code, create separate code for every new service/method, etc. because this process is kicked off automatically after every build, with no interaction.  </p>
  
  <p>So, I have hundreds of thousands of test XML parameters that I pass into hundreds of methods, without caring about what they are.  We have done it for years on ASMX web services and the one method (very similar to the above link) handled all web services/methods/test parameters.  </p>
  
  <p>With switching to WCF I get internal server errors especially when testing invalid XML nodes: missing required nodes, errors in a create method for duplicate names, etc. (any error condition). I think it makes sense that there is an easy way to do this with WCF in the same manner.  </p>
  
  <p>I want EXACTLY what SoapUI is sending back, I just need to know how it's doing it.</p>