Is there something wrong with setting connection strings in applicationSettings?

Question

.NET supports several ways to store configuration settings for quite some time, which has led to a lot of confusion. It doesn’t help that the three best hits for searching “Settings in C #” on MSDN are ten years (and many of the related questions [2] on this venerable site are also 6-7 years old). It is very difficult to determine which of the early recommendations was since outdated.

In my project, I decided to use ApplicationSettings(as opposed to AppSettings) because:

• This is apparently the current recommended approach on MSDN (and here ).
• The item AppSettings is deprecated since .NET 4+ * (the topic is “no longer available”, but see “Other versions” on this page.) _{[* Although, vaguely, the AppSettings property is still supported ]}
• I prefer to edit the settings in the designer tool rather than in the xml editor.
• I prefer strongly typed settings.

However, now I need to decide where to place the connection strings. The latest documentation on MSDN (and here, on SO , and also since CP ) still recommends using the section <connectionStrings> app.config. But accessing this from code requires the use of the old syntax, which I now consider deprecated with appSettings. In other words, it makes no sense to read one part of the file app.configwith the old syntax:

ConfigurationManager.ConnectionStrings["MydDBConnName"];

and another part of the same file with the new syntax :

Properties.Settings.Default.myOtherSetting;

Also, this prevents me from editing lines in the designer.

So bottom line: is there any reason not to standardize all my configuration settings (including connection strings) in an element ApplicationSettings?

Answer 1

ConnectionStrings , , () DbConnection, DbCommand ..

, , , SQL, - ( , , , SQL) "" . .

(SQL Server, Oracle, ODBC, OleDB), ConnectionStrings .

Answer 2

- -.

, DatabaseContext, , . ApplicationSettings.

(, ) , - Locator > .

, (, ), Root of Composition. , ApplicationSettings .

, / .

Answer 3

, , <connectionStrings> , , . Windows , , , , , . .

, , , , " " . , <appSettings> , . , . , , , " ", - , .

Answer 4

, ApplicationSettings . Entity Framework , ConnectionStrings. , , , . - Windows Authentication .

Answer 5

The standard is what you do. For example, in my work environment, the only information that changes in a particular application is the server name. We have dev / test / prod servers. Therefore, we only save the SQL Server name in the configuration file. The database name does not change. We just read the database server from the configuration file and build the line in the application.