I’m trying to upgrade the SDK from beta1 to beta3 in our .NET application, the build is successful, but the APIs do not work as before. All seems fine until I try to retrieve a document and then I get an exception. The code flows as follows… var options = new ClusterOptions() .WithServers(clust…

Just to close out this topic. The issues that I noted above were resolved with beta4. That is to say, after updating to SDK 3.0.0-beta4, I did not experience any of these issues. Thanks, -Ryan

.NET SDK 3.0.0-beta3 changes (code from beta1 no longer working)

.NET SDK

jmorris January 7, 2020, 10:27pm 6

No, I don’t think so; collections are a developer preview opt-in and if they are not enabled, the SDK will use a fake default collection. Unless of course there was a bug there

This could be the case, can you upload an exact example?

Topic		Replies	Views
Bucket with name default does not exist or cannot be reached .NET SDK dot-net	4	1395	March 4, 2022
Performance degradation after upgrading to v3.3.6 .NET SDK	12	1074	May 18, 2023
Problem getting started with .Net SDK 3.0 .NET SDK	1	1330	November 7, 2019
NullRefereceException inside Couchbase client 3.0 during connection .NET SDK	10	2345	June 20, 2020
ExistsAsync / GetAsync Failure .NET SDK	10	2103	February 11, 2021

.NET SDK 3.0.0-beta3 changes (code from beta1 no longer working)

Related topics