connection strings in app.config - ?!Confused!?

Can someone please help, I am totally confused how to use connection strings in the app.config. I mostly have been creating web applications, but now am involved in a windows application project. I am used to keeping my connection strings int he web.config on the server, and having the code pick and choose which string to use. This makes it simple to switch connection strings from test development, to production, ect..

Okay, so in windows application development, why is the app.config file stored on the client PC? Anyone can just pop open their notepad program and read server information, and possible username information.

I guess technically the app.config file will not change much if at all, but if it does need to change (such as server died and was replaced with new name) how would a re-deployment happen?

Thanks,

Brandon
[875 byte] By [bjswift] at [2007-11-20 9:28:22]
# 1 Re: connection strings in app.config - ?!Confused!?
Because the APPLICATION is on the users machine. :rolleyes:

If you are using 2.0 (or later) you can encrypt sections of the App config to minimize tampering.
TheCPUWizard at 2007-11-10 3:09:05 >
# 2 Re: connection strings in app.config - ?!Confused!?
Wizard:

That is exactly the source of my confusion, that the application is on the client machine. Basically, we re-thought our connection issues, by letting the user type in the server, then choosing from a list for the database, and to type in their username/password or click 'windows authentication' and have a class which uses sqlconnectionstringbuilder to build the connection string. This works because we are only going to support SQL Server, so won't need to worry about multiple connection string structures..
bjswift at 2007-11-10 3:10:05 >