neventstore/obsolete-neventstore-example

Collection of sample code to demonstrate how to use NEventStore

NEventStore

NEventStore is a persistence library used to abstract different storage implementations when using event sourcing as storage mechanism.

This library is developed with a specific focus on DDD/CQRS applications.

NEventStore currently supports:

• .net standard 2.0
• .net framework 4.6.2

Starting from Version 6.0.0 NEventStore will use Semantic Versioning to track the version numbers.

Build Status (AppVeyor)

Branches:

• master
• develop

Main Library Packages

• NEventStore - the core library package.
• NEventStore.Serialization.Json - Json serialization to be used with an IDocumentSerializer.
• NEventStore.Serialization.Bson - BSon serialization to be used with an IDocumentSerializer.
• NEventStore.PollingClient - provides an implementation for a PollingClient.

Documentation

Please see the documentation to get started and for more information.

ChangeLog can be found here

Developed with:

How to build (Windows OS)

To build the project locally on a Windows Machine:

• Open a Powershell console in Administrative mode and run the build script build.ps1 in the root of the repository.

Vesioning

Versioning is done automatically by the build script updating the AssemblyInfo.cs file (false in .csproj files) before the build starts. The version number is retrieved from the git repository tags using "gitversion" tool.

Things are handled this way because NEventStore is used a submodule in other projects and it need to have it's own version number when building other projects.

You should not update the version number manually, not commit the updated AssemblyInfo files.

obsolete-neventstore-example's Issues

Please Create An Example that uses MongoDB

I'm having problems finding good documentation around integrating / setting up NEventStore with Mongo. Am I missing some obvious resources on the net? Mr. Google is coming back with lots of nothing from what I can tell.

It would be wonderful to have an example of using NEventStore with MongoDB.

You'd kill two birds with one stone. A) You won't have to write prose documentation on this. B) those integrating your project with Mongo have a starting point to work from / guide them.

The repository is not updated for a while- please remove it

The repository is not updated for a while and not compilable anymore.
The examples inside NEventStore: https://github.com/NEventStore/NEventStore/tree/master/src/NEventStore.Example and
https://github.com/NEventStore/NEventStore/tree/master/src/NEventStore.PollingClientExample are working fine and should be used for quick start.
Please remove the repository to avoid confusion.

Redesign the folder structure of the example project

Providing a sample project is a great mandatory thing in any descent open-source project. It's a good news that you included this.

However, it's current structure is limiting the possibility to have multiple samples in the repository.

Is it possible to redesign the project structure to allow multiples sample to co-exists?

A proposal a new structure may be:

• (root)
  • Basic
    • very simple sample
  • Asp.net
    • sample 1
    • sample 2
  • Windows
    • sample 1

Then, contributors may complete the samples eventually.