>I don't see why this wouldn't work, but... why would you do this? With all the different .NET Web Service clients available including the WCF client which can connect to just about any kind of service, why would you want to reinvent the wheel? It's quite difficult to create proper HTML by hand and properly handle all the namespace conversions that are often require to make this work right...
>
>If you really want to go down this path I'd recommend you download a copy of SoapUI and connect to the service with that. It will show you the SOAP responses and you can build your manual requests based on that. Makes it much easier to see what's happening and often times you can find small problems before you start coding and can't see the forest for the trees :-)

Thanks

One of the goals is to go generic by having a class at the framework level. I have one for SOAP and one for SOAPSVC. However, with the SOAPSVC class, I cannot find a way to have it working when I have a binding and a custom behavior. See thread #1552778 for what I mean. If you can find a way of where the adjustment would be, that would be appreciated. This class does it pretty well. However, it is only working when I do not have the change the binding and benefit from a custom behavior.