neo4j-dotnet-driver

From this patch release we start to support .NET framework 4.5.2 alongside .net standard 1.3.
We have also replaced optional parameters in our public API to method overloading for better integration with C++ projects.

Read more in chagelog for more bug fixes in this release.

Asynchronous API is available from this release!

Async API is one of the main focuses in 1.5 .NET driver releases. In the first alpha release of this 1.5 series, we would like to represent a new asynchronous API, as well as full stack async support for direct driver, which is the driver connects to a specific server and does not support casual-cluster routing & load balancing.

The async API looks very similar to our existing synchronous API. The code bellow shows a simple example of how to code using the new async API:

public async Task PrintGreetingAsync(string message)
{
    var driver = var driver = GraphDatabase.Driver("bolt://127.0.0.1", AuthTokens.Basic(user, password), 
        new Config
        {
            EncryptionLevel = EncryptionLevel.Encrypted,
            MaxIdleConnectionPoolSize = 20,
            MaxConnectionPoolSize = 50,
            ConnectionAcquisitionTimeout = TimeSpan.FromMinutes(2)
        });

    var session = driver.Session();
    try
    {
        var greeting = await session.WriteTransactionAsync(async tx =>
        {
            var result = await tx.RunAsync("CREATE (a:Greeting) " +
                            "SET a.message = $message " +
                            "RETURN a.message + ', from node ' + id(a)", new {message});

            if (await result.ReadAsync())
            {
                return result.Current()[0].As<string>();
            }
            else
            {
                return null;
            }
        });

        Console.WriteLine(greeting);
        }
    finally
    {
        await session.CloseAsync();
    }
    driver.Close();
}

You are most welcome to try out this alpha and give us your valuable feedback (via such as gitHub issues).
The alpha artifact could be found available in Nuget and can be installed by using Install-Package Neo4j.Driver -Pre

Async support for routing driver (a.k.a. the driver for connecting to a cluster with built-in routing and load balancing) and docs are coming soon!

In 1.4 releases, we introduced byte array and multiple bookmark support. Read more on the new functions available in our changelog

Release candidate for 1.4.0 .NET driver. Pls give it a try and give us valuable feedback.

First release of 1.4 series with multiple bookmarks and byte arrays support.

Here is the 1.3.0 release 🎉
The 1.3.0 driver introduces routing context for improved use of routing driver together with a Neo4j cluster of version 3.2 or above.

Driver manual
Driver API
Changelog

Adds ConnectionIdleTimeout on connections to timeout connections in pool that have been idle longer than the configured time.

Changelog

Finally we are presenting the release candidate for 1.3 drivers. Try it out and give us your valuable feedback for this driver version!

Changelog

This release fixes a socket connection issue on some systems. It also includes a new support to use IPv6 addresses.

Besides, this release also improves the stability of the driver in routing mode. See the changelog for more information.

The 1.3 series is coming! This first release includes a few new enhancements to the routing driver such as accepting routing context from the routing uri. It also includes a few 1.2 bug fixes such as fixing connection errors on some operation systems.

See more details at our changelog.

We would like to present the 1.2 driver which provides improved Causal Clustering API. The improved API which

• automates the passing of causal consistency context (bookmark) within Sessions
• prevents Driver death when the database service is completely unavailable
• hides failures that are caused by cluster leader switch by replay transactions using the strategy defined by retry logic

Checkout driver documentation for more information of how to use the new API.

The first release of the new 1.2 driver!

Improved routing and error handling.
More stable when error occurs in the cluster.
See details in changelog

Fix the bug in load balancer that the new connection pools are not connecting to the specified server.

We would like to represent you the new 1.1 routing driver which adds routing and simple load balancing. This means that with the routing driver, the application user/operator does not need to add logic to their application or additional components to their infrastructure to interact with a Neo4j 3.1+ Causal Cluster. To use the new routing driver, just specify bolt+routing as the scheme in the URL when connecting to the cluster.

Read the changelog for more information about this release!

What to know what is in the coming 1.1.0 release? Try out this release candidate!

1.0 changelog
wiki

Added new in-house routing for routing Cypher statements to a neo4j 3.1+ causal cluster.
For the full story and bug fix history, please read more in our changelog

We present .NET Core support and TLS 1.2 support from this version. We also better improved the streaming of result by buffering the result automatically if not consumed in time.
For more details of bug fixes in this release, checkout the changelog

The first release of 1.1 .NET driver, where streaming of records is introduced!

This release includes a few key bug fixes in reading data from network buffer and packing chunks into network buffer. We also enhanced the session pool in this release to better handle acquiring and releasing sessions in a concurrent manner.