Skip to content

v3 fast follows #265

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 22, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions source/includes/language-compatibility-table-csharp.rst
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,11 @@
- .NET 4.7 [#2.14-note]_
- .NET 4.6

* - 3.0
- ✓
- ✓
-

* - 2.13 to 2.30
- ✓
- ✓
Expand Down
17 changes: 17 additions & 0 deletions source/upgrade/v3.txt
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,17 @@ Version 3.0 Breaking Changes
and {+mdb-server+} versions, visit the
:ref:`Compatibility <csharp-compatibility-tables>` page.

- The driver drops support for .NET Core 2.x and .NET Framework 4.6. You must upgrade to
.NET Core 3.x or later, or .NET Framework 4.7.2 or later.

To learn more about the compatibility between .NET/C# driver versions
and .NET versions, visit the
:ref:`Compatibility <csharp-compatibility-tables>` page.

- The v1.x legacy API, which was deprecated in v2, has been removed. If the driver
provides a replacement for a deprecated API, the compiler
messages in v2.x will display it.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two separate issues here.

First the legacy v1.x API was removed. That was contained in the legacy shim mongocsharpdriver. If you're using those v1.x APIs, you need to migrate to the new API and we don't provide any upgrade guidelines. Very few users are still on the old v1.x API and thus we don't provide upgrade guidance. (We don't need to say that. Just FYI.)

Second the v2.x API contained a number of deprecations, which have been removed in 3.0.0. The 2.30.0 driver contains guidance in the form of deprecation warnings including the new APIs to use.

Copy link
Collaborator Author

@mongoKart mongoKart Oct 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I appreciate the clarification. It was hard to find specifics about this. I moved the legacy shim removal from What's New to Breaking Changes (since it will be, for anyone still using it) and changed the wording.

I believe the following two entries in the Upgrade Guide adequately discuss the deprecated (now removed) v2.x members, but let me know if not.


- The classes, methods, and properties in the ``MongoDB.Driver.Core`` namespace that were
deprecated in v{+last-version-2-number+} are marked ``internal``. If the driver
provides a replacement for a deprecated class, method, or property, the compiler
Expand Down Expand Up @@ -155,6 +166,12 @@ Version 3.0 Breaking Changes
authentication provider in your application's bootstrap code. To learn more about
using AWS authentication with the {+driver-short+}, see :ref:`csharp-mongodb-aws`.

- To use In-Use Encryption, you must add the ``MongoDB.Driver.Encryption`` package to
your project and register the encryption mechanism in your application's bootstrap code.
To learn more about using In-Use Encryption with the {+driver-short+}, see
:manual:`In-Use Encryption </core/security-in-use-encryption>` in the {+mdb-server+}
manual.

- If you try to serialize or deserialize a floating-point
``Infinity`` or ``NaN`` value to an integral representation, the driver throws an
``OverflowException``. To learn more about floating-point ``Infinity`` and ``NaN``
Expand Down
Loading