-
Notifications
You must be signed in to change notification settings - Fork 303
Frequently Asked Questions
Yes, we have a few cleanup tasks to prepare the library for open source, but by GA the plan is to open source the library and post the source here on GitHub.
The existing library will remain. PRs to the System.Data.SqlClient library will be ported to Microsoft.Data.SqlClient as relevant.
Add the Nuget package to your project, then update your references and using statements.
There are two primary changes:
First, since this is an application level package, for .NET Framework any updates to the library will need to be shipped in an application update, rather than coming from Windows Update. This matches the existing behavior for .NET Core applications.
Second, there are a few new features in Microsoft.Data.SqlClient which will not be backported to System.Data.SqlClient. Those features are Data Classification Support, UTF-8 support for .NET Core and .Net Framework, and Always Encrypted support for .NET Core.
Issues should be opened under this GitHub repository.
The package supports .NET Framework 4.6 and up, .NET Core 2.1 and up, and .NET Standard 2.0 and up. For earlier framework support please continue to use System.Data.SqlClient.
7. Can I use Microsoft.Data.SqlClient and System.Data.SqlClient at the same time / in the same application?
Yes. The libraries can reside side by side just like any other library, but since they contain the same class names this could cause confusion. We recommend porting entirely to one or the other if possible.
It's coming. In the meantime, the documentation for System.Data.SqlClient is still relevant to Microsoft.Data.SqlClient. The APIs and functionality have not changed except for the additions mentioned in the release notes.