I have written a windows service using VB 2005 (.Net 2.0).  I have a
couple of settings that I need to store, just some paths.

I put them in the Application settings section and then manually edit
the file and start the service  and everything works fine.  However
when a new version is installed the file gets overwritten and the
settings are lost.

I tried making them user settings and using the "ShouldUpgrade"
setting trick, but it appears that they still get overwritten.  I
assume that with a service the .config stored in the execution
directory is the only one that is created?  As a result it is always
overwritten by a new version?

Is there a better way to handle this?  I guess I can just create my
own config file and not use application settings, but I hate to do
that.  I am going to be working on another service that will require a
large number of settings to be stored, using my.settings would be
convenient for that project, but if the settings are overwritten after
a new install I might not want to do it.

Now that I think about it, even if I create my own file, which would
be included in the installation, it would overwrite as well.  I guess
it boils down to, is there a better way to handle settings for a
windows service that won't get overwritten?

Thanks in advance for any help,
Matt