Hey Cor, its really simple.
Use integrated window security for your connection strings.
Then there are no user names or passwords in the config file's connection
string.
Its ridiculous that MS makes it so easy to use My.settings for user settings
but makes it all but impossible to modify application configuration settings
without going through the notepad bull....
So if I'm going to have to take the responsibility for that, an easy answer,
where the hell do I find some usefull sample code?
Bob
"Cor Ligthert [MVP]" <no************@planet.nl> wrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
Bob,
I have seen in these newsgroups many questions how you could protect the
connection strings with the most difficult kinds of cryptography. You want
the opposite.
I think that because of those completely different use of those things you
would have to make it yourself and take the responsibility with that.
Just my thought reading your message.
Cor
"Bob" <bd*****@sgiims.com> schreef in bericht
news:e0**************@TK2MSFTNGP04.phx.gbl... Over the life of a distributed app, it is possible for the connection
string that it was configured with initailly needs to change.
You can't scope a connection string setting to user so that it can be
changed easily by user for use with MY namespace. If it scoped to
application, it can't be changed by the user. Is the only way to modify
an application setting to go into the application's config file with
notepad? There must be a way to make a form that is user friendly and
allow the user to change an app setting without using notepad!
I wish they wouldn't try so hard to protect us against ourselves, just
make YOUR software more reliable and let me worry about what I do is all
I ask!
In any case, folks, I would really appreciate any trick up your sleeve to
let me change my application settings from within my program. Its Ok if
they just take effect the next time it launched.
Thanks for any help,
Bob
