Re: Passing parameters best practice
- From: "Marina Levit [MVP]" <someone@xxxxxxxxxx>
- Date: Wed, 9 Aug 2006 14:25:16 -0400
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.
"tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
news:uM$sn%239uGHA.324@xxxxxxxxxxxxxxxxxxxxxxx
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
.
- References:
- Passing parameters best practice
- From: tshad
- Passing parameters best practice
- Prev by Date: Re: Disabling Browser Cache on ASP.NET Pages That Use Master Pages
- Next by Date: Re: Passing parameters best practice
- Previous by thread: Passing parameters best practice
- Next by thread: Re: Passing parameters best practice
- Index(es):
Relevant Pages
|
