ASP.Net client sending XML string to remote .net web service

[brendan_gallagher_2001]

Hi,

I am using a .Net (VB.Net) webservice with an ASP.net client to
generate an xml string from a db and then send it to a web service on
the same box (client is part of the same service) which then processes
the xml amd sends a sucess result. I have this part already working.
However, I would like to be able to send the xml string to a vb.net
service on a remote server. I have the url of the service I want to
send the xml string to but I am not sure how to change it from the
localhost url. Is this done in the WSDL file in the servicename
elements?

regards and thanks.

[John Timney \(ASP.NET MVP\)]

There is a URL Behavior property of the WebService which defaults to
static. Changing it to dynamic allows the Web Reference URL to be placed in
the web.config file and read.

Theres a comprehensive exmplanation of a solution here:

http://msdn.microsoft.com/library/de...stallation.asp

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

<br********************@yahoo.co.uk> wrote in message
news:11**********************@g47g2000cwa.googlegr oups.com...

Hi,

I am using a .Net (VB.Net) webservice with an ASP.net client to
generate an xml string from a db and then send it to a web service on
the same box (client is part of the same service) which then processes
the xml amd sends a sucess result. I have this part already working.
However, I would like to be able to send the xml string to a vb.net
service on a remote server. I have the url of the service I want to
send the xml string to but I am not sure how to change it from the
localhost url. Is this done in the WSDL file in the servicename
elements?

regards and thanks.

[brendan_gallagher_2001]

Hi John,

Thanks for that. I'm really looking for a much simpler solution
though. I simply need to change the destination from localhost to a
remote address. I generate the string locally but I want to send it to
a remote service. Once I change it, I will not need to change it
again. Im assuming this would be changed by inserting a line in the
web.config or WSDL files.

regards
Brendan