.NET core / framework compat #310
Merged
Conversation
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
DOC-11619
|
This is my best guess for a quick update - can be revisited again when .NET 8 support arrives. |
RichardSmedley
commented
Nov 7, 2023
| @@ -1,4 +1,4 @@ | |||
| The Couchbase .NET SDK is compatible with https://docs.microsoft.com/en-us/dotnet/standard/net-standard[.NET Standard] 2.0 and .NET Standard 2.1, which means that it's compatible with .NET Framework 4.6.2+, .NET 5.0, .NET 6.0, and .NET Core 3.1. | |||
| The Couchbase .NET SDK is compatible with https://docs.microsoft.com/en-us/dotnet/standard/net-standard[.NET Standard] 2.0 and .NET Standard 2.1, which means that it's compatible with .NET Framework 4.6.2+, .NET 5.0, .NET 6.0, and .NET Core 3.1 -- and supported so long as Couchbase supports the SDK release and Microsoft supports the .NET platform version. | |||
There was a problem hiding this comment.
We'll update this further for the 3.5 release.
…upported SDKs. Per NCBC-3552, mention that Capella certificate must be installed locally for .NET Framework clients.
…stall the Capella certificate locally.
RichardSmedley
commented
Nov 27, 2023
| @@ -146,27 +142,15 @@ include::hello-world:partial$supported.adoc[] | |||
| | *✖* | |||
| | *✖* | |||
|
|
|||
| | .NET Framework 4.6.2+ | |||
| | .NET 8.0 (Long-Term Support) | |||
| | *✔* | |||
There was a problem hiding this comment.
Were the older releases (3.0 / 3.1 / 3.2) tested against .NET 8.0?
There was a problem hiding this comment.
No, as .NET 8.0 is new as of Nov 14, 2023 - the earliest version tested on .NET 8.0 will likley be 3.4.14 due in Dec.
There was a problem hiding this comment.
Thanks, will remove this column for now.
RichardSmedley
commented
Nov 27, 2023
There was a problem hiding this comment.
One comment, but otherwise LGTM - thanks for the additions @RiPont
| The https://docs.microsoft.com/en-us/dotnet/standard/net-standard[.NET Standard documentation] and | ||
| https://dotnet.microsoft.com/platform/dotnet-standard#versions[.NET Standard version chart] may be useful to help understand other available options. | ||
|
|
||
| Couchbase strongly recommends using the latest version of .NET that's officially supported by both Microsoft and Couchbase. | ||
| Couchbase strongly recommends using the latest LTS version of .NET that's officially supported by both Microsoft and Couchbase. |
There was a problem hiding this comment.
Should we point to Versions of .NET ?
There was a problem hiding this comment.
Thanks - will add this, and we'll look to improve how we present the info in 3.5 👍
| @@ -223,7 +223,8 @@ The .NET SDK bundles Capella’s standard root certificate by default. | |||
| This means you don’t need any additional configuration to enable TLS -- simply use `couchbases://` in your connection string. | |||
|
|
|||
| NOTE: Capella's root certificate is *not* signed by a well known CA (Certificate Authority). | |||
| However, as the certificate is bundled with the SDK, it is trusted by default. | |||
| However, as the certificate is bundled with the SDK when using .NET 6.0 or later, it is trusted by default. | |||
| .NET Framework clients will have to add it to the Windows certificate store. | |||
There was a problem hiding this comment.
Do we need to more specific about what a ".NET Framework client" is? Meaning linking to .NET Framework and .NET 6?
There was a problem hiding this comment.
Maybe - but probably not from this page, rather from the compat page.
RiPont
approved these changes
Dec 12, 2023
RichardSmedley
added a commit
that referenced
this pull request
Dec 12, 2023
RichardSmedley
added a commit
that referenced
this pull request
Dec 12, 2023
...ported forward from #310
RichardSmedley
added a commit
that referenced
this pull request
Dec 12, 2023
ported forward from #310
RichardSmedley
added a commit
that referenced
this pull request
Mar 6, 2024
* .NET core / framework compat (#310) * .NET core / framework compat DOC-11619 * Update supported.adoc * Per NCBC-3511, update .NET SDK support matrix for LTS and currently-supported SDKs. Per NCBC-3552, mention that Capella certificate must be installed locally for .NET Framework clients. * Update "Managing Connections" to mention .NET Framework users must install the Capella certificate locally. * https://versionsof.net/ link * Awaiting 23.4.14 * table format / comments * Get it right this time <sigh> --------- Co-authored-by: Richard Ponton <[email protected]> * Ubuntu 22.04 * Delete modules/howtos/pages/durability-error-handling-from-the-sdk.adoc Ghost page removal * typo fix DOC-11739 * Dotnet 3.4.14 GA Release notes (#313) * Dotnet 3.4.14 GA Release notes * Gardening started but unfinished --------- Co-authored-by: Richard Smedley <[email protected]> * Remove protostellar ticket references (#315) * Remove protostellar ticket references * Gardening --------- Co-authored-by: Richard Smedley <[email protected]> * Release notes for CouchbaseNetClient 3.4.15 (#316) * Release notes for CouchbaseNetClient 3.4.15 * Gardening --------- Co-authored-by: Richard Smedley <[email protected]> * Remove NCBC-3635 from 3.4.15 * Gardening2 (#319) * NCBC-3653: Document that IGetResult.Dispose should be called Motivation ---------- The documentation should explain why Dispose should be called, which operations are effected and the example code should also do this. * Gardening * gardening part duex --------- Co-authored-by: Richard Smedley <[email protected]> * NCBC-3440: improve ClusterOptions documentation (#320) * NCBC-3440: improve ClusterOptions documentation * ventilated prose --------- Co-authored-by: Richard Smedley <[email protected]> * tweaks --------- Co-authored-by: Richard Ponton <[email protected]> Co-authored-by: Jeffry Morris <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DOC-11619