| Subject: Base Addresses for WCF Clients ? |
| Group: microsoft.public.windows.developer.winfx.indigo |
| Date: 12/18/2007 3:44:44 AM |
| From: NonNB [Email Address Protection] |
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 |
| Back |
| Subject: Re: Base Addresses for WCF Clients ? |
| Group: microsoft.public.windows.developer.winfx.indigo |
| Date: 1/11/2008 5:53:47 AM |
| From: "Shimon Sim" [Email Address Protection] |
There is not base address on client. You just put everything in the endpoint address. "NonNB" <nonamebrande@gmail.com> wrote in message news:e085d8ba-0591-4785-ba2e-546cf76c2902@q77g2000hsh.googlegroups.com... > 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 |
| Back |
| Subject: Re: Base Addresses for WCF Clients ? |
| Group: microsoft.public.windows.developer.winfx.indigo |
| Date: 1/14/2008 3:55:04 AM |
| From: NonNB [Email Address Protection] |
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. |
| Back |
| Subject: Re: Base Addresses for WCF Clients ? |
| Group: microsoft.public.windows.developer.winfx.indigo |
| Date: 1/14/2008 1:43:14 PM |
| From: "Shimon Sim" [Email Address Protection] |
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@gmail.com> wrote in message news:fec538df-80a3-4d7d-9097-3056808b55a5@s12g2000prg.googlegroups.com... > 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. |
| Back |
| Subject: Re: Base Addresses for WCF Clients ? |
| Group: microsoft.public.windows.developer.winfx.indigo |
| Date: 1/15/2008 12:44:01 AM |
| From: NonNB [Email Address Protection] |
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 |
| Back |
| Subject: Re: Base Addresses for WCF Clients ? |
| Group: microsoft.public.windows.developer.winfx.indigo |
| Date: 1/15/2008 1:01:46 PM |
| From: "Shimon Sim" [Email Address Protection] |
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@gmail.com> wrote in message news:cd0f391f-4a7c-44d8-97a2-e603a46540b4@q39g2000hsf.googlegroups.com... > 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 |
| Back |