wcf - ConfigSource attribute - specifying config in two places -
we have wcf service needs deployed 200 plus customers' servers. able make portion of web.config available customization using configsource attribute so:
<bindings configsource="bindings.config" />
this allows overwrite main web.config file future upgrades while not overwriting customers' own modifications sections decide externalize way. unfortunately, there's problem - according this article, "when use configsource attribute, must move entire section separate file because there no merging of element settings." means section put in external file outside of our reach upgrades , changes without having mess external files customer may have made modifications to.
is there way around this? can have our cake , eat too, or have decide between having control ourselves , giving our customers flexibility?
well appears there's no way around this, can 1 way or other. in end decision made use configsource , externalize portions of web.config, knowing outside of our control vast majority of our web.config still available future modifications.
Comments
Post a Comment