+1  A: 

This might do the trick:

Manually setting soap:address in ASMX

Update:

The technique above seems to work just fine but has some limitations if you have more than one service. You also need to be running in Full Trust so doing this in a partial trust environment isn't going to work.

I'm not sure there's any other magic config switch or attribute to make this happen other than using the SoapExtensionReflector. After a good Google around, all the results point to the SoapExtensionReflector method.

But how about this? If the web services don't change all that often you could take a copy of the generated WDSL, edit the SOAP/HTTP bindings, and then publish it on it's own as a static XML file?

HTH
Kev

Kev
Thanks Kev. We do have multiple services within the app. I'm hoping there's a config setting we can update to not include the port or something. wishful thinking probably :).
Ian Suttle
Thank you for the additional info. Our app is already in production but the network architecture is changing a bit. We really want to avoid changing the app itself if at all humanly possible. +1 for the added info and extra effort. Thanks!
Ian Suttle
No prbs, appreciated. :)
Kev