NewB question on maintaining config files

We have a C# dotNet app running as an NT service on several boxes,
performing data conversion processing for us. Each box has its' own config
file, with app settings that control the behavior of the app on that box.
The app was written by a savvy dotNet developer in our shop, who I am trying
not to harass too frequently with questions.

We are spending lots of time switching out config settings on those boxes,
so I ventured to volunteer to write a little app to query the current
settings off the boxes, display them, and allow updates that would then be
written back to the box. I've done similar coding in many languages, but I
am brand new to dotNet and C#.

The app will be a simple winform with a bunch of repeated controls, each
bundle of controls representing the settings on the box. A single button
will invoke the update back to all the boxes.

So I am now researching how to obtain the settings, then re-apply my
changes. I have been doing a lot of reading on the ConfigurationManager
class, which seems to be the mainstay of this kind of processing. However
it seems to default to being the tool to handle the current EXE config file.
Is there a way I can fake it out to open a config file with a different name
on a different location, then use its' AppSettings to grab the details I
need? Or is there a much more sensible approach that I just don't know
about yet?

Any pointers or links to code samples appreciated
Gary


.