You can hand code the connection proxy without WSDL, but it is a bit of a
pain. A better option is create an equivalent service (equivalent in
methods, not implementation) on your own box and grab the WSDL from that
service. Editing the path information to the web service is simple. Then,
use the wsdl created to create a proxy class using wsdl.exe. You will find
it far less time consuming. Once you get a successful test, send the company
that put you through this pain the WSDL as a thank you for the pain. ;->
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"Wayne P." <in******@nospam-totalink.net> wrote in message
news:uO*************@TK2MSFTNGP12.phx.gbl...
I need some guidance, as I am used to Visual Studio '03 taking care of
this for me. I need to connect to a web service, but the web service does not
provide a WSDL document to point to...
Is there an easy way to setup and use SOAP without a WSDL document that
sets everything up?
TIA!
Wayne