<p>I'm working with a third party to integrate some of our systems with theirs and they provide us with a SOAP interface to make certain requests and changes in their connected systems. The problem for me is that they do not supply a WSDL-file for me to work against. If I had a WSDL-file it would be a simple matter just to run the supplied .NET command (wsdl.exe) and generate a proxy class to interact with the service.</p>

<p>Is there an "easy" way to do this without a WSDL-file? I have all the functions that we can access and what parameters I need to send and what I should expect in return.</p>

<p>Is it common to have a SOAP-service without WSDL-files? (I'm asking this since we're going to add more external systems into the mix in the future)</p>

<p>Has anyone done a proxy-class or any other form of client against a WDSL-less service and have any good pointers on how to do it?</p>

I haven't built a SOAP interface without access to a WSDL file, but the format is
fairly well-documented
.  Your best bet might be to create a simplified WSDL file of your own that reflects what you know of the service you're subscribing to....
If you decide to go this route, an
existing stackoverflow question
points at some tools for validating your WSDL.