Passing parameters best practice

[tshad]

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?

Thanks,

Tom

 

[Marina Levit [MVP]]

I think no matter what mechanism you use, you should have a front end
interface for the user to use. The user shouldn't have to dig into the
registry, or the config file of the application.

These various places have various degrees of security. If your parameters
don't need to be secure, then you could go either the registry route, or
app.config.

No matter what route you take, you will need to restart your windows service
to pick up the new configuration settings.

 

[sloan]

My preferred route these days is a custom configuration section/handler.

http://support.microsoft.com/kb/309045/EN-US/

After you do 1 or 2 of them (aka, get past the struggle part), they are
simple to write.

It gives you a true "object" at the end of the day to encapsulate your
values...instead of always getting the app/key/value.
It keeps the app.config file organized and neat also.

 

[sloan]

Please do not cross post.

http://groups.google.com/group/micr...0ec80b5458e?lnk=st&q=&rnum=1#fef8e0ec80b5458e

http://groups.google.com/group/micr...0d3559e2828/bddc6e384504155e#bddc6e384504155e

microsoft.public.dotnet.languages.csharp
microsoft.public.dotnet.languages.vb