Base Addresses for WCF Clients ?

Hi

Have I missed something obvious, or is there no way to use the
"BaseAddress" pattern in a WCF (.NET 3.0) client configuration file,
similar to that offered on the WCF Server?

IMHO this would make the transition from Dev to QA etc versions of WCF
servers much simpler.

Something like :
<system.serviceModel>
<client>
<baseaddresses>
<add baseAddress="http://123.123.123.123:8000" />
</baseaddresses>
<endpoint name="MyEndPoint" address="/MyNameSpace/SomeService"
i.e. the actual endpoint address = baseAddress + endpoint.address

Otherwise I guess this needs to be done programmatically, which seems
a waste of an otherwise flexible config file?

Thanks in Advance

Stuart

There is not base address on client. You just put everything in the endpoint
address.

"NonNB" <nonamebrande@xxxxxx> wrote in message
news:e085d8ba-0591-4785-ba2e-546cf76c2902@xxxxxx

Thanks for the reply Shimon. Ctrl H it is, or I guess will need to do
this programatically and essentially "reinvent" a more proprietary /
customized config file.

I don't get why can't you use config the way it is now.

What is the difference if you change is in endpoint
address=http://server1/endpoint
to different server2 or using base address?


"NonNB" <nonamebrande@xxxxxx> wrote in message
news:fec538df-80a3-4d7d-9097-3056808b55a5@xxxxxx

Our current project will have ~200 contracts by the time of
completion, but always to just 'one' server - life could have been
easier if just one point of configuration change for all endpoints.

Dev :
net.tcp://localhost:xxx/....

To QA:
net.tcp://qaserver:xxx/...

To Customer (UAT / Pilot / Live)
net.tcp://customerservers:xxx/...
etc

Thanks.
Finally got you.
Still not sure if programmatically change too much. Find and Replace will do
the job ... if you don't deploy too often to different servers.




"NonNB" <nonamebrande@xxxxxx> wrote in message
news:cd0f391f-4a7c-44d8-97a2-e603a46540b4@xxxxxx

"Shimon Sim" wrote:
WCF base addresses do not work sometimes. When I create several AppDomains
and try to use a service with base address of named pipes transport, WCF
tries to create a new pipe with the same name and - no surprise - fails.

For tcp this problem is solved with TCP Port Sharing (though it is not the
best solution to my mind) but for net.pipe you haven't anything similar.