tshad,
What I do is write a Windows Application program that updates the Window's
Services app.config file.
I have the Windows Application restart the service so that it sees the
updated config file.
Currently I am using System.Xml to update the config file, however I'm
thinking the new Configuration namespace in .NET 2.0 (VS 2005) will simplify
changing the config file.
FWIW: The new Configuration namespace in .NET 2.0 definitely simplifies
leveraging the config file!
--
Hope this helps
Jay B. Harlow [MVP - Outlook]
..NET Application Architect, Enthusiast, & Evangelist
T.S. Bradley -
http://www.tsbradley.net
"tshad" <ts**********@ftsolutions.comwrote in message
news:eQ****************@TK2MSFTNGP04.phx.gbl...
|I need to pass a few parameters to my Windows Service program. The end user
| will be changing the parameters and settings should be saved.
|
| What is the best practice
| - use app.config
| - use .ini file
| - use Registry
| - write a Windows Application program and save the settings to database
| table
|
| should I trust the end user to modify registry, .config or .ini file?
|
|