Environmental overrides only work for configuration sections that have design-time support in EntLib's configuration tool, such as EntLib's. Unless you add design-time support for the System.ServiceModel configuration objects (or find such an implementation) you
won't be able to use environmental overrides.

Fernando

xiaofeng wrote:
Hi,

We have a lot of WCF endpoint adress in app.config, and want to update for different enviroment by using Environment overriding. But seems it's not wotking with this section.

How can we make it possible to work with EntLib configuration enviroment overriding?

Why does anybody think it is useful to use this based on the fact if you want to configure any setting that is not supported by entlib out the box you will have to either have to go through the arduous task of writing your own extension or find something
else that actually overrides any setting (in which case you should just use that for all your overriding). I am sure that someone will say that a global solution to configuration was never the intention of the team, in which case you really wasted your
time, because what you ended up producing was something usefiul only to people whose entire config file was produced using entlib and are so short-sighted that they never conceive of any other circumstance when they will need to use anything other than entlib
to configure their application - is that really encouraging best practice?