> My first thought is that the initial configuration for this should be
> done at deployment time, so it shouldn't matter.
[quoted text clipped - 3 lines]
> channel. If you can do this, let your service startup without
> configuration and delay running other logic until configuration is saved.
Yes, that is not a bad suggestion. Just make everything an application
setting and just modify the .config by hand before starting.. Maybe
I'm just over thinking it.. What about if I wanted a GUI to modify
those application settings can I use the Configuration Manager classes
to read the configuration files (if so any examples?) or should I just
roll my own XML parser to modify the configuration file?
-jr
Peter Bromberg [C# MVP] - 11 Feb 2008 02:47 GMT
Yes, but you would need to provide a mechanism for your Service to reload and
use the revised configuration data. A FileSystemWatcher can do this. See this
article on a self-updating service for some ideas:
http://www.eggheadcafe.com/articles/20041204.asp
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
MetaFinder: http://www.blogmetafinder.com
> > My first thought is that the initial configuration for this should be
> > done at deployment time, so it shouldn't matter.
[quoted text clipped - 12 lines]
>
> -jr