Hi,
That's a step in the right direction.
Ideally I want to keep the <service>, <serviceBehaviors> ... etc in a
service specific
configuration file, eg ServiceA.dll is entirely configured by
ServiceA.config.
I'm wondering if my self-hosting parent application could
programmatically
change configSource="ServiceX.config" before instantiating the
specific
service X.
I'll have to investigate.
Thanks.
> You talking about something like this??
>
[quoted text clipped - 59 lines]
>
> > Thanks, Steve.
sloan - 17 Oct 2007 15:56 GMT
Well, a config file is just a fancy xml document, so that's possible.
I went the other route I think.
When I have several different projects, I end up having the app.config file
of the Host(er) as seen below.
Then I've written some el-crappo code to merge different app's into the
single WCFService.config file.
If you figure out anything, post a follow up (probably in a new thread, or
it'll get lost).
..
As a side note, you may want to look at the
msdn.microsoft.com/stocktrader/
Greg has put together a Configuration framework piece. Its still in its
infancy, but is going to be great for managing multiple machine wcf/config
settings.
channel9/wiki site has some videos (with Greg explaining) as well.
> Hi,
>
[quoted text clipped - 78 lines]
>>
>> > Thanks, Steve.