|
| 1 | +# Release Notes |
| 2 | + |
| 3 | +## General Availability of Microsoft.Data.SqlClient 1.1.2 released 15 April 2020 |
| 4 | + |
| 5 | +This update brings the below changes over the previous release: |
| 6 | + |
| 7 | +### Added |
| 8 | +- Allowed passing username with Active Directory Interactive Authentication [#493](https://github.com/dotnet/SqlClient/pull/493) [#516](https://github.com/dotnet/SqlClient/pull/516) |
| 9 | + |
| 10 | +### Fixed |
| 11 | +- Fixed the ConnectionString's password persistence in .NET Core. [#489](https://github.com/dotnet/SqlClient/pull/489) |
| 12 | +- Addressed MARS TDS header containing errors [#510](https://github.com/dotnet/SqlClient/pull/510) |
| 13 | + |
| 14 | +### Changed |
| 15 | +- Updated driver libraries to be CLS Compliant [#522](https://github.com/dotnet/SqlClient/pull/522) |
| 16 | + |
| 17 | + |
| 18 | +## New Features |
| 19 | + |
| 20 | +New features over the 1.0 release of Microsoft.Data.SqlClient. |
| 21 | + |
| 22 | +- [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. |
| 23 | + |
| 24 | +## Target Platform Support |
| 25 | + |
| 26 | +- .NET Framework 4.6+ |
| 27 | +- .NET Core 2.1+ (Windows x86, Windows x64, Linux, macOS) |
| 28 | +- .NET Standard 2.0+ (Windows x86, Windows x64, Linux, macOS) |
| 29 | + |
| 30 | +### Dependencies |
| 31 | + |
| 32 | +#### .NET Framework |
| 33 | + |
| 34 | +- System.Data.Common 4.3.0 |
| 35 | +- Microsoft.Data.SqlClient.SNI [1.1.0,1.2.0) |
| 36 | +- Microsoft.Identity.Client 3.0.8 |
| 37 | +- Microsoft.IdentityModel.Protocols.OpenIdConnect 5.5.0 |
| 38 | +- Microsoft.IdentityModel.JsonWebTokens 5.5.0 |
| 39 | + |
| 40 | +#### .NET Core |
| 41 | + |
| 42 | +- Microsoft.Win32.Registry 4.5.0 |
| 43 | +- runtime.native.System.Data.SqlClient.sni 4.4.0 |
| 44 | +- System.Security.Principal.Windows 4.5.0 |
| 45 | +- System.Text.Encoding.CodePages 4.5.0 |
| 46 | +- System.Configuration.ConfigurationManager 4.5.0 |
| 47 | +- Microsoft.Identity.Client 3.0.8 |
| 48 | +- Microsoft.IdentityModel.Protocols.OpenIdConnect 5.5.0 |
| 49 | +- Microsoft.IdentityModel.JsonWebTokens 5.5.0 |
| 50 | + |
| 51 | +#### .NET Standard |
| 52 | + |
| 53 | +- Microsoft.Win32.Registry 4.5.0 |
| 54 | +- runtime.native.System.Data.SqlClient.sni 4.4.0 |
| 55 | +- System.Buffers 4.4.0 |
| 56 | +- System.Diagnostics.DiagnosticSource 4.5.0 |
| 57 | +- System.Memory 4.5.1 |
| 58 | +- System.Security.Principal.Windows 4.5.0 |
| 59 | +- System.Text.Encoding.CodePages 4.5.0 |
| 60 | +- System.Configuration.ConfigurationManager 4.5.0 |
| 61 | +- Microsoft.Identity.Client 3.0.8 |
| 62 | + |
| 63 | +### Always Encrypted with secure enclaves |
| 64 | + |
| 65 | +In general, existing documentation which uses System.Data.SqlClient on .NET Framework should now work with .NET Core, too. |
| 66 | + |
| 67 | +- [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) |
| 68 | +- [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) |
| 69 | + |
| 70 | +In order to use the enclave feature, connection strings should include the required attestation protocol and attestation URL. Examples: |
| 71 | + |
| 72 | +- `Attestation Protocol=HGS;Enclave Attestation Url=<attestation_url_for_HGS>` |
0 commit comments