If you reference parameters at the C # level in the ASP.Net web service, I don't think this is unusual. Your parameters will simply become children of the response element. Here is a quick example of a web service with a single web method that has parameters:
[WebService(Namespace = "http://begen.name/xml/namespace/2009/10/samplewebservicev1")]
public class SampleWebServiceV1 : WebService
{
[WebMethod]
public void
WebMethodWithOutParameters(out string OutParam1, out string OutParam2)
{
OutParam1 = "Hello";
OutParam2 = "Web!";
}
}
Using the above web method, a SOAP request is as follows:
POST /SampleWebServiceV1.asmx HTTP/1.1
Host: localhost
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://begen.name/xml/namespace/2009/10/samplewebservicev1/WebMethodWithOutParameters"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<WebMethodWithOutParameters xmlns="http://begen.name/xml/namespace/2009/10/samplewebservicev1" />
</soap:Body>
</soap:Envelope>
And the answer is as follows:
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<WebMethodWithOutParametersResponse xmlns="http://begen.name/xml/namespace/2009/10/samplewebservicev1">
<OutParam1>Hello</OutParam1>
<OutParam2>Web!</OutParam2>
</WebMethodWithOutParametersResponse>
</soap:Body>
</soap:Envelope>
. , -, #.