This post has been republished via RSS; it originally appeared at: SQL Server articles.
The SqlClient team is moving forward with continuous updates and improvements to the Microsoft.Data.SqlClient data provider for SQL Server. Our plan is to provide GA releases twice a year with two preview releases in between. This cadence should provide time for feedback and allow us to deliver features and fixes in a timely manner. This second 2.0 preview includes over a dozen fixes and changes over the previous 1.1 GA release.
One of the main changes to note, is related to security and is likely to be a breaking change to clients if they rely on the previous default settings and encryption is enforced a server with an invalid certificate. SqlClient will now validate server certificates by default if encryption is enforced from the server side but the client has not specified Encrypt=true. If this breaks your clients, your options are to use a certificate on the server which is part of your client's trust chain (recommended) or to change your clients to use TrustServerCertificate=true (not recommended).
For the full list of changes in Microsoft.Data.SqlClient 2.0 Preview 2, please see the Release Notes.
To try out the new package, add a NuGet reference to Microsoft.Data.SqlClient in your application and pick the 2.0 preview 2 version.
We appreciate the time and effort you spend checking out our previews. It makes the final product that much better. If you encounter any issues or have any feedback, head over to the SqlClient GitHub repository and submit an issue.
David Engel