I have a vs2005 solution containing about 5 projects, three of which
have their own .settings files.
When I deploy the application, I want all the settings to be in one
place - configurable - presumably in an app.config file where I can
edit them. The settings will be used by a windows service,
filewatcher, database access application.
How do I achieve this?
As a workaround, I have created an additional project which contains a
single static class with static property accessors pointing to values
from an internal settings file.
I've consolidated all the settings information from the other projects
into that one project. I then referenced that project from all the
others and used it's settings via the static class properties.
Does that sound like the right approach?
I just had the idea that I might be missing something. I've downloaded
the Configuration Application Block and am investigating that,
thinking that it might help me. As usual, there's bucketloads of
general information on the application block, but nothing succinct, so
I'm going to have to do the hard yards until I find something
pertinent.
Any advice would be much appreciated.