Create 611802 - SQLConnection.ConnectionString throws NRE (microsoft#742)

saurabh500 · Ron Petrusha · commit e623b574f935 · 2018-05-10T13:47:48.000-07:00
* Rename 611802 - SQLConnection.ConnectionString throws NullReferenceException.md to 611802 - SQLConnection.ConnectionString throws NullReferenceException .md

Documenting known issue for .Net Framework System.Data NRE.

* Update 611802 - SQLConnection.ConnectionString throws NullReferenceException .md

* Update 611802 - SQLConnection.ConnectionString throws NullReferenceException .md

* Update 611802 - SQLConnection.ConnectionString throws NullReferenceException .md

* Update 611802 - SQLConnection.ConnectionString throws NullReferenceException .md
diff --git a/releases/net472/KnownIssues/611802 - SQLConnection.ConnectionString throws NullReferenceException .md b/releases/net472/KnownIssues/611802 - SQLConnection.ConnectionString throws NullReferenceException .md
@@ -0,0 +1,23 @@
+# NullReferenceException while setting `SqlConnection.ConnectionString` to an empty string or null.
+## Symptoms
+
+When an application tries to set the `ConnectionString` property of the `SqlConnection` object to an empty string or null value, a `NullReferenceException` is thrown. This exception occurs when .NET Framework 4.7.2 is installed on the OS hosting the application.
+
+
+## Cause
+
+.NET Framework 4.7.2 includes a change that increases the default connection retry count for connections to Azure SQL Database to two. 
+This change sets the internal value of the retry count without validating if the `ConnectionString` is a non-null or non-empty value, 
+which results in the `NullReferenceException`.
+
+## Impact
+
+The impact is limited to applications using the `SqlConnection.ConnectionString` API to set an empty connection string, which now throws an  exception.
+
+## Workarounds
+
+No known workarounds with .NET Framework 4.7.2.
+
+## Resolution
+
+The .NET team is working on a fix that will be available in a future update.
