|
1 | 1 | # .NET Driver Version 2.7.0 Release Notes
|
2 | 2 |
|
3 |
| -## Known Issues: |
4 |
| -* Incomplete SCRAM-SHA-256 Support in .NET Standard: In .NET Standard, authenticating via SCRAM-SHA-256 may not work with non-ASCII passwords because SaslPrep is not fully implemented due to the lack of a string normalization function in .NET Standard 1.6. Normalizing the password into Unicode Normalization Form KC beforehand MAY help. SCRAM-SHA-1 is the recommended alternative for now. |
| 3 | +The main new features of 2.7.0 are support for new features of the 4.0.0 version of the server including: |
| 4 | + |
| 5 | +* Transactions |
| 6 | +* New CountDocuments and EstimatedDocumentCount methods (depending on whether you need an exact result or a fast estimate) |
| 7 | +* Support for change streams on all collections in a cluster or a particular database via the new Watch methods on IMongoClient and IMongoDatabase |
| 8 | +* SCRAM-SHA-256 authentication |
5 | 9 |
|
6 | 10 | An online version of these release notes is available at:
|
7 | 11 |
|
8 | 12 | <https://github.com/mongodb/mongo-csharp-driver/blob/master/Release%20Notes/Release%20Notes%20v2.7.0.md>
|
9 | 13 |
|
10 |
| -The full list of JIRA issues that are currently scheduled to be resolved in this release is available at: |
| 14 | +The list of JIRA tickets resolved in this release is available at: |
11 | 15 |
|
12 | 16 | <https://jira.mongodb.org/issues/?jql=project%20%3D%20CSHARP%20AND%20fixVersion%20%3D%202.7.0%20ORDER%20BY%20key%20ASC>
|
13 | 17 |
|
14 |
| -The list may change as we approach the release date. |
15 |
| - |
16 | 18 | Documentation on the .NET driver can be found at:
|
17 | 19 |
|
18 | 20 | <http://mongodb.github.io/mongo-csharp-driver/>
|
19 | 21 |
|
20 | 22 | ## Upgrading
|
21 |
| -* The .NET Driver now **disables** certificate revocation checking by default, setting `CheckCertificateRevocation` in `SslSettings` to `false` by default. Any applications relying on the older default of `true` now must explicitly set `CheckCertificateRevocation` to `true` in in `SslSettings` to re-enable certificate revocation checking. |
22 |
| - * Previously, the driver enabled certificate revocation checking by default, in contrast to the `mongo` shell and other MongoDB drivers. This was also in contrast to .NET's defaults for `SslStream` (see .NET Framework documentation [here](https://docs.microsoft.com/en-us/dotnet/api/system.net.security.sslstream.authenticateasclient?view=netframework-4.7.2#System_Net_Security_SslStream_AuthenticateAsClient_System_String_) and .NET Standard documentation [here](https://docs.microsoft.com/en-us/dotnet/api/system.net.security.sslstream.authenticateasclient?view=netstandard-2.0#System_Net_Security_SslStream_AuthenticateAsClient_System_String_)). |
| 23 | + |
| 24 | +* The .NET Driver now **disables** certificate revocation checking by default, setting `CheckCertificateRevocation` in `SslSettings` to `false` by default. Any applications relying on the older default of `true` now must explicitly set `CheckCertificateRevocation` to `true` in `SslSettings` to re-enable certificate revocation checking. |
| 25 | + |
| 26 | + Previously, the driver enabled certificate revocation checking by default, in contrast to the `mongo` shell and other MongoDB drivers. This was also in contrast to .NET's defaults for `SslStream` (see .NET Framework documentation [here](https://docs.microsoft.com/en-us/dotnet/api/system.net.security.sslstream.authenticateasclient?view=netframework-4.7.2#System_Net_Security_SslStream_AuthenticateAsClient_System_String_) and .NET Standard documentation [here](https://docs.microsoft.com/en-us/dotnet/api/system.net.security.sslstream.authenticateasclient?view=netstandard-2.0#System_Net_Security_SslStream_AuthenticateAsClient_System_String_)). |
| 27 | + |
| 28 | +## Known Issues: |
| 29 | + |
| 30 | +* Incomplete SCRAM-SHA-256 Support in .NET Standard: In .NET Standard, authenticating via SCRAM-SHA-256 may not work with non-ASCII passwords because SaslPrep is not fully implemented due to the lack of a string normalization function in .NET Standard 1.5. Normalizing the password into Unicode Normalization Form KC beforehand MAY help. SCRAM-SHA-1 is the recommended alternative (when targeting .NET Standard) for now. |
0 commit comments