c# - WCF Service References : Managing App.Config -
my solution composed of several class library projects. 1 of these include service reference. functionality exposed particular assembly need called several other assemblies.
how can manage configuration file(s) solution, don't have repeat <system.servicemodel>
contents on every single assembly making use of web service?
that approach (repeating in every app's config) default , recommended way go - cannot have config files class-library assemblies (you can, it's fair bit of work them work - not worth trouble).
if can't live this, create wcf client proxy in code, bindings, options, endpoints , all. gain bit of ease-of-use (no more config needing put every app calling class library), loose bit of flexibitlity (endpoint addresses , binding options hard-coded).
Comments
Post a Comment