Better document the DevelpomentModeNameTransformer

document the release process

NCBC-264 Review the release-process document

Couchbase Client hangs during instantion of the Client if the request to http://xxx.xxx.xxx.xxx:8091/pools/default/bucketsStreaming/default is blocked or never returns

Hangs after threads are aborted

Add documentation on error handling with views/queries

Detailed logging information

Link broken to nlog configuration file

Implement timeouts on actual operations

Enhance discussion of return codes/values

Use an enumeration instead of integers for return codes

Add expiries and CAS to StoreJson extension methods

CouchbaseCluster RESTful wrappers should not expose WebExceptions

Stats call doesn't handle I/O error

Docs: Recommendations for which logging level to be set during testing/staging/production and examples of messages at each level

ExecuteGet-multi should return detailed status results for each key

Enhance intelligence of client to know about all nodes of a cluster for making REST connection

Docs: Reference installation

Provide file based caching of config for stateless .NET apps

Need details on "StoreMode" values

Handle "no active vbucket" view failure

Need better explanation of usage and return values of increment operation (and likely others)

Docs don't mention InnerResult

Optimize multiple set (multi-set or mset bulk update) with setq

Config updates seem to be occuring when vbucket configuration hasn't changed

JSON extension methods not listed in API references

When performing MultiGet, unloading AppDomain crashes the host

Getting a thread abort (ocassionally) on store

Could not find the pool '...' at http://host:8091/pools : password-less buckets make the other buckets unavailable

Error handling documentation

Explicit docs for what .NET Framework versions are supported

evaluate socket pool reliability change

building shippable artifacts under CI

InvalidOperationException in views during server restart

Improvement needed around documentation of using singleton client

Provide Consistent Order of Parameters

running integration tests under CI

Provide Extract of Comments for API Docs

As a .net developer, I have an API that allows me to access all of the features of tap so that I can make use of all of the powers of membase.

Provide more detail on "Unable to locate node" errors

Minimize key size by storing as binary array

Implement keep-alive logic for data connections

programmatically set all the Couchbase configurations

logging level documentation needed

building under CI

Client not properly handling cluster_run server

Docs should use Execute* methods with best practice error handling and logging in all examples

Docs/Library: Unlock after getl

Provide Error Handling Consistent with Other SDKs

Replica read command

Authenticated view tests should use app.config

Improve discussion around using store versus executestore

Docs: working with multiple buckets in the .NET client

Provide Consistent Timeouts

Refactor solution so that Enyim is part of main source branch

Check for SetTcpKeepAlive at runtime for Mono support

Fix invalid tests in NUnit project.

ExecuteGet() for DictionaryType on multiple keys does not throw a exception if it is not able to connect to a node

We need documentation that explains how users can check for error codes

When node is unavailable for a view query, don't throw an InvalidOperationException

During rebalance client tries to connect the primary node only

Fix CBSE-426 - .Net Client fails silently if there is a wrong configuration

Use Couchbase.Management API to create buckets and views for unit tests requiring custom setups

Write the .NET/Windows Getting Started Section for the Essentials Guides

deploying to download locations directly from CI

Garbled error message when CAS value does not match

BinaryOperation failues should include message

Set, add, and replace should be separate methods

generating shippable artifacts

Statistics through Stats() Enyim.Caching.MemcachedClient.

Enhance packaging to not conflict with other tools that include Enyim.Caching via Nuget

default logging on Enyim should include INFO level logging on connections being dropped

Way to determine which Servers are active

Provide Standardized Logging

should retry count be allowed to be 0, or should it be forced higher

NCBC-174 Fix the test : CouchbaseAuthenticatedViewTests\When_Bucket_Is_Authenticated_View_Returns_Results

add a keyStats feature

Certain method summaries are not linked properly in docs

Touch should return a boolean

.Net client fails in two sdkd scenarios

flush_all method still available through API, does nothing against 2.0 cluster