•  20-08-2019
  •  | 
  •  

Question

Can .NET (managed code) read and write to CouchDB?

I would like to build a part of my project that does document management using CouchDB

Was it helpful?

Solution

Take a look at the SharpCouch utility class.

It is a simple wrapper class for the CouchDB HTTP API.

OTHER TIPS

Its a late answer, but do check out Hammock. It's active and going into production use on several projects soon and is receiving regular updates and fixes. Besides basic object persistence, Hammock gives you:

  • True POCO. You don't even need an 'id' property; Hammock tracks that internally.
  • Robust support for views, including an easy to use fluent API that both generates AND executes views, and support for creating custom map/reduce views.
  • Attachments support.
  • A generic Repository<> class that helps bring your queries/views (i.e. _Design doc) together with your c# application code. Repositories are responsible for maintaining _design docs, and this helps keep CouchDB views from feeling like stored procs.
  • A full unit test suite. This is not prototype software.

Yes.

See here for instructions on installing CouchDB on windows.

Here is a link to the getting started with C# wiki article. There is a link to a .Net wrapper in that article. It would be pretty easy to roll your own as well.

Given that you generally communicate with CouchDB over REST and JSON, I'd imagine it wouldn't be too hard to use JSON.NET and the normal WebClient/HttpWebRequest classes to do it. I haven't tried it myself, mind you...

Little late to the game but there's an open source project for a new driver written in C# over the async HTTP Client and by default Newtonsoft's JSON.Net for serialization (switchable). MyCouch - Simple async CouchDb client for .Net.

A Getting started post exists here: http://danielwertheim.se/get-up-and-running-with-couchdb-and-c-using-mycouch-on-windows/

Keep an eye on Ottoman an open-source project written in C#. It is still in heavy development, but I wanted to point it out as an option for projects in the planning stages. I will update this post as it gets closer to completion. You can view the source on github. Read the README to see examples and what is possible with the current version.

  • Unlike SharpCouch, which uses strings heavily, Ottoman uses generics for automatic serialization and desrialization for mapping an object from a JSON string and vice versa. All this without your objects needing to inherit off an interface or base class.
  • It uses Json.Net underneath to handle the JSON serialization and deserialization.
  • Maps the RESTFul error codes that CouchDB returns into Exceptions.
  • Planned Feature: Id generators for generating Id's for the objects being persisted
  • Planned Feature: Implicit Offline Optimistic Lock via Document Revisions, Ottoman will use an Identity Map to keep track for you and will throw an exception when a conflict occurs.
  • Planned Feature: It will be Mono compatible.
  • Planned Feature: This is down the road, but I do plan on having LINQ expressions for Map/Reduce functions which you express to CouchDB using JavaScript.

It is a fairly new project, but very active. Of course, I'm a bit biased also. ;-)

also take a look at divan - a light-weight wrapper for the cdb api

I have used JSON.NET in conjunction with the MS REST starter kit's http client class to integrate to CouchDB and it works really well.

CouchDB's wiki has a list of API for C# (with their features) if you want the latest status : http://wiki.apache.org/couchdb/Getting_started_with_C%23

Very easy to use .NET API for CouchDB included into WDK10 that you can grab from http://code.google.com/p/skitsanoswdk/ it is very flexible and allows you to deal with your data on objects and pure json level.

The options (ordered by latest update):

Check out Relax http://www.sharplearningcurve.com/wiki/Symbiote-Relax.ashx. Relax is a ".Net API abstraction of CouchDB's (excellent) RESTful API. It includes a repository-based interface for document interaction and a server controller for administrative type tasks."

One more - CouchDBClient: https://github.com/ttutisani/CouchDBClient

Disclaimer: I'm the author.

I tried to make CouchDBClient more friendly to work with custom objects - that's what usually applications store in the database.

Back when I started writing this framework, all others that I found and tried were making an impression of non-standardized method signatures (named using various conventions and harder to guess what they did), not unified interfaces (some operations around string docs, while others around json docs), not very flexible (some worked only with strings, others only with objects), or not very abstract (had to know CouchDB REST API first to use them correctly). I'm assuming and hoping they have matured since then, but at least this one is designed up to my taste.

I'm hoping that CouchDBClient can create a feeling of comfortable abstraction without worrying about underlying API too much, and just focusing on your application, and how it stores and retrieves objects it needs.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top