-
Notifications
You must be signed in to change notification settings - Fork 292
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Release 1.1] Release notes for Microsoft.Data.SqlClient v1.1.3 (#566)
- Loading branch information
1 parent
a469c15
commit 39873ee
Showing
4 changed files
with
75 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
# Release Notes | ||
|
||
## General Availability of Microsoft.Data.SqlClient 1.1.3 released 15 May 2020 | ||
|
||
This update brings the below changes over the previous release: | ||
|
||
### Fixed | ||
- Fixed driver behavior to not perform enlistment of pooled connection on aborted transaction [#551](https://github.com/dotnet/SqlClient/pull/551) | ||
- Fixed issues introduced with MARS TDS Header fix in last release by reverting original change that caused issues. [#550](https://github.com/dotnet/SqlClient/pull/550) | ||
|
||
|
||
## New Features | ||
|
||
New features over the 1.0 release of Microsoft.Data.SqlClient. | ||
|
||
- [Always Encrypted with secure enclaves](#always-encrypted-with-secure-enclaves) - Always Encrypted is available starting in Microsoft SQL Server 2016. Secure enclaves are available starting in Microsoft SQL Server 2019. | ||
|
||
## Target Platform Support | ||
|
||
- .NET Framework 4.6+ | ||
- .NET Core 2.1+ (Windows x86, Windows x64, Linux, macOS) | ||
- .NET Standard 2.0+ (Windows x86, Windows x64, Linux, macOS) | ||
|
||
### Dependencies | ||
|
||
#### .NET Framework | ||
|
||
- System.Data.Common 4.3.0 | ||
- Microsoft.Data.SqlClient.SNI [1.1.0,1.2.0) | ||
- Microsoft.Identity.Client 3.0.8 | ||
- Microsoft.IdentityModel.Protocols.OpenIdConnect 5.5.0 | ||
- Microsoft.IdentityModel.JsonWebTokens 5.5.0 | ||
|
||
#### .NET Core | ||
|
||
- Microsoft.Win32.Registry 4.5.0 | ||
- runtime.native.System.Data.SqlClient.sni 4.4.0 | ||
- System.Security.Principal.Windows 4.5.0 | ||
- System.Text.Encoding.CodePages 4.5.0 | ||
- System.Configuration.ConfigurationManager 4.5.0 | ||
- Microsoft.Identity.Client 3.0.8 | ||
- Microsoft.IdentityModel.Protocols.OpenIdConnect 5.5.0 | ||
- Microsoft.IdentityModel.JsonWebTokens 5.5.0 | ||
|
||
#### .NET Standard | ||
|
||
- Microsoft.Win32.Registry 4.5.0 | ||
- runtime.native.System.Data.SqlClient.sni 4.4.0 | ||
- System.Buffers 4.4.0 | ||
- System.Diagnostics.DiagnosticSource 4.5.0 | ||
- System.Memory 4.5.1 | ||
- System.Security.Principal.Windows 4.5.0 | ||
- System.Text.Encoding.CodePages 4.5.0 | ||
- System.Configuration.ConfigurationManager 4.5.0 | ||
- Microsoft.Identity.Client 3.0.8 | ||
|
||
### Always Encrypted with secure enclaves | ||
|
||
In general, existing documentation which uses System.Data.SqlClient on .NET Framework should now work with .NET Core, too. | ||
|
||
- [Develop using Always Encrypted with .NET Framework Data Provider](https://docs.microsoft.com/sql/relational-databases/security/encryption/develop-using-always-encrypted-with-net-framework-data-provider) | ||
- [Always Encrypted: Protect sensitive data and store encryption keys in the Windows certificate store](https://docs.microsoft.com/azure/sql-database/sql-database-always-encrypted) | ||
|
||
In order to use the enclave feature, connection strings should include the required attestation protocol and attestation URL. Examples: | ||
|
||
- `Attestation Protocol=HGS;Enclave Attestation Url=<attestation_url_for_HGS>` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters