Hi Bruce,

Glad to see you again:). How are you doing on the former webservice/ ISA
server issue, have you got any progress on that?

Regarding on the ASP.NET autogenerated WSDL document, it will always
generate the service address through the local intranet's address of the
machine(in your case it's the machine/server name of the development
machine). Actually, the public ip address or dns specific address name may
vary depend on the network environment between the client and server, so
it's abit hard to let the ASP.NET webservice dynamic generate the correct
ip/servername address accordign to different client.

IMO, for development time, since we can test the webservice through local
client or local intranet client, the default autogenerated wsdl document
and service description page should be ok. When we need to deploy/publish
the webservice to production server(which has certian public ip address or
dns server address), we can consider customizing the webservice description
page. And currently there're two simple means to do this:

1. Entirely replace the default generated webservice description page with
our custom page and also use our custon wsdl document(may copy the
autogenerated one and modify the service address element value).

2. Just provide a custom WSDL document page(through WebServiceBinding
setting).

Here are two web articles discussing on this:

#<wsdlHelpGenerator> Element  
http://msdn2.microsoft.com/en-us/library/ycx1yf7k(VS.80).aspx

#Using a Custom WSDL File in ASP.NET Web Services
http://pluralsight.com/blogs/craig/archive/2005/12/15/17482.aspx

Hope this helps and please let me know if there's anything else we can help.

Regards,

Steven Cheng
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.