>Something tells me that we cannot use HttpWebRequest to send a SOAP envelope to a Web Service built as SVC or Java for example. Can someone confirms me this?
>
>I am able to load into a test project a Service Reference to a Web Service, which we believe is made for SVC. That works. But, I cannot use my standard SOAP class, which is using HttpWebRequest to build the entire SOAP envelope manually as a string and send it as is.
>
>Down below in that page:
>
>http://stackoverflow.com/questions/2434703/using-the-httpwebrequest-class
>
>...it says that we should not use HttpWebRequest in such a situation.

Don't see anything on that link that implies one shouldn't use HttpWebRequest ?

Does this mean when negotiating with Web Service build like that that it wouldn't be possible to negotiate with the building of our own SOAP envelope manually?

Can't see why it would be a problem if the request is formulated correctly......


>The beauty with handling it all as is is that we can have a generic class and simply fill the properties and call the method to send the data. With a Service Reference, this is not the case as we have to create a fake reference into the project and then we have to find a way to have the method name to be call dynamically, using some kind of invoke mechanism, which works BTW, but then it gets complicated when you need to change the binding and add a behavior.