Unifying the EventStore client and hte .net core version


Are there plans to unify the current EventStore API and the .net core version?

What, if any are the differences between the two API’s?

Kind regards


To the best of my knowledge https://github.com/EventStore/EventStore/pull/1680 is the closest to ready to go; it’s just a matter of the core team getting time to dig into, verify and merge.

The NetCore fork repo doesn’t have any significant features/fixes that are not in master (I think one PR which can be cherrypicked)

The above PR has the changes that the NetCore repo had (only a few hundred lines without any major hacks or rewrites, but probably touching 80 files), but also lots of work on making sure tests are in right (I have not dug in myself but that’s what my scan said)

The things not in the NetCore repo are (off the top of my head):

  • concurrency bugfixes as too

  • OperationExpiredException

  • Some new node coniguration modes

  • Minor bugfixes re e.g. using IPv6 fixes


I will try to look at the differences tomorrow (and will raise it in stand up, I just get up much earlier than everyone else now :)) but they should be pretty minor.

There is a thread in issue waiting for an approach https://github.com/EventStore/EventStore/issues/1650. Currently a big pain is Embedded Event Store mixing this with Core client its a pain especially unit testing as there are namespace/assembly conflicts.