Do you avoid using non strongly typed connection strings?

Last updated by Brady Stroud [SSW] 2 months ago.See history

This rule has been archived
Archived Reason: Update connection string management - favor IOptions pattern over Visual Studio's Application Settings. Offers robust, flexible config in .NET Core, aligning with modern development practices. Refer to Microsoft's IOptions pattern in .NET documentation for implementation guidance.

Using non strongly typed connection strings means that you have to hard code at some point in your code. Once you change the name of your connection strings, you have to change the code that references them too.

Visual Studio provides a convenient tool, called Application Settings, that allows you to manage all of your connection strings from only one location. You can use its wizard to compose connection strings quickly and correctly. Also, it provides a management class to read and write all of your connection strings.

var connString = System.Configuration.ConfigurationManager.ConnectionStrings["MyProj.Properties.Settings.ConnectString"].ToString();
var conn = new SqlConnection(ConnString);
var cmd = new SqlCommand(strSql, conn);

Bad example - Using non strongly typed connection strings, the highlighted text is hard code actually

Figure: Good example - Using Application Settings to configure connection strings

We open source. Powered by GitHub