{"id":2452,"date":"2016-12-08T11:19:16","date_gmt":"2016-12-08T11:19:15","guid":{"rendered":"https:\/\/www.couchbase.com\/blog\/?p=2452"},"modified":"2025-10-09T06:45:39","modified_gmt":"2025-10-09T13:45:39","slug":"couchbase-net-sdk-2-3-10-now-available","status":"publish","type":"post","link":"https:\/\/www.couchbase.com\/blog\/couchbase-net-sdk-2-3-10-now-available\/","title":{"rendered":"Couchbase .NET SDK 2.3.10 Now Available!"},"content":{"rendered":"

Today we’re releasing version 2.3.10 of the Couchbase .NET SDK. This is a maintenance release of bug fixes and enhancements including the Data Structures API and FTS API. In case you missed it, we have a Developer Preview of .NET Core support here<\/a>.<\/p>\n

New Features and Changes<\/h2>\n

We follow semantic versioning, meaning we increment the dot-minor number when adding features. We sometimes add low-risk features in maintenance releases with uncommitted interface stability so you as a developer can easily gain access to new features. Features added under in a maintenance\u00a0release are uncommitted and are open to change but should be promoted to committed in the next dot-minor release.<\/p>\n

See here<\/a> for a discussion of interface in the .NET SDK.<\/p>\n

Data Structures API update<\/h3>\n

When we introduced the Data Structures API in the 2.3.9 release we added support for lists, maps and dictionaries. In this release we’re also adding support for Queues. This enables you to use a JSON document stored in Couchbase to maintain an ordered FIFO queue, with all the normal concurrency control you would expect from an in-memory queue. An example on how to use a queue is below:<\/p>\n

bucket.QueuePush(\"my_queue\", new Person(\"Jerry\"));\r\nbucket.QueuePush(\"my_queue\", new Person(\"Rodney\"));\r\n\r\nvar size = bucket.QueueSize(\"my_queue\"); \/\/ 2\r\nvar person = bucket.QueuePop(\"my_Queue\"); \/\/ Jerry\r\n<\/code><\/pre>\n
Also, as part of the refinement of the uncommitted Data Structures API we have updated some method names to be consistent across all the Couchbase SDKs. The changes are below:<\/p>\n\n\n\n\n\n\n\n\n
Old<\/th>\nNew<\/th>\n<\/tr>\n<\/thead>\n
ListPush<\/td>\nListAppend<\/td>\n<\/tr>\n
ListShift<\/td>\nListPrepend<\/td>\n<\/tr>\n
ListDelete<\/td>\nListRemove<\/td>\n<\/tr>\n
SetExists<\/td>\nSetContains<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Sorting FTS results<\/h3>\n
An enhancement to the FTS (Full-Text Search) capabilities of Couchbase Server 4.6 is to allow the user to apply their own sorting preferences on the server before returning the result. This is done using the Sort<\/strong> method on ISearchParams before submitting a search. There can be one or more sorting fields, and fields that are prefixed with a dash indicate a descending order.<\/p>\n
var searchParams = new SearchParams();\r\nsearchParams.Sort(\"name\", \"-age\");\r\n<\/code><\/pre>\n
The above example sort criteria indicates to sort by ascending name then by descending age.<\/p>\n
Waiting for N1QL indexes<\/h3>\n
The SDK enables you as a developer to create N1QL indexes programmatically. However, indexes are created in an asynchronous manner on the server and executing queries against incomplete indexes is a bad idea. As part of this release we have introduced a way for the SDK to watch and wait for one or more indexes to go into the ‘online’ state before continuing. An example of creating an index and waiting for it to be online is below:<\/p>\n
\/\/ Create index called \"accounts\" on columns \"account_id\" and \"account_name\"\r\nbucketManager.CreateN1qlIndex(\"accounts\", false, \"account_id\", \"account_name\");\r\n\r\n\/\/ Wait for the index to be marked as 'online', with a 30 second timeout\r\nvar indexNames = new List { \"accounts\" };\r\nbucketManager.WatchN1qlIndexes(indexNames, TimeSpan.FromSeconds(30));\r\n<\/code><\/pre>\n
Release Notes<\/h2>\n