In C# the url is in "Service Reference" configuration. It takes the url of the WSDL file... The problem is that the XML response sent from server perl is different from the XML response aspected from C#. I use this code in PM file to return the response from server:

 

  #  $return elaborated

 my $response = SOAP::Data -> new() 
         
                  ->name('response')
                  ->prefix('')
                  ->type('string')
                  ->uri('FUNCTION')
                  ->value($result);
                 
   return $response;
[download]

I need to know how the server can make a correct XML response for DotNet. Probably the solution is a better use of "SOAP::Data -> new()" to write the correct tags and header...

The problem is .... I need to know how the server can make a correct XML response for DotNet. Probably the solution is a better use of "SOAP::Data -> new()" to write the correct tags and header...

Kinda almost but not really -- DotNet is not a SOAP message format ... you need to learn more about SOAP :)

Does you message (the SOAP::Data...) stuff matches your advertised WSDL? If it doesn't you should adjust WSDL until it advertises the correct "stuff".

If the xml generated and WSDL are close enough, its most likely the SOAP message styles ( RPC/ENCODED/RPC/LITERAL/DOCUMENT/LITERAL ) that aren't matching ...

There are a bunch of suggestions on that starting at Microsoft .NET client with SOAP::Lite Server including Modify your .NET server, if possible

Yes, I can't really help and I do hate SOAP :)

well, i am a beginner in Web Service, but with soap lite i wrote a complete Web Service (client and server sides) in Perl Language, and it works perfectly, i can send documents and images with "base64" encoding. My problem started with this c sharp client, so i hate C sharp ! ^_^