vaughnvernon / iddd_samples_net Goto Github PK

Hello Vaughn, great to see this code out here. One of the members in our study group found this and pointed us to it. Under IdentityAccessContext, DataModelTests.csproj and idd_identity_access_data_layer.csproj are not found.

Also, VisualDesignToolHook is missing.

I'm complaining, but I'm willing to help :) Any suggestions?

AssertionConcern should be a reusable component and not a base class for every object that need to do assertions.
Composition Over Inheritance

It should be something like this:
https://github.com/phatboyg/Magnum/blob/master/src/Magnum/Guard.cs

Hello guys

With current implementation we are publishing ProductCreated domain event in ctor for product.
If we will implement IProductRepository and use EF Core than this ctor will be called on read existed product from db.

Is ctor a good place to decide that new instance of product is created for new product?

Some ctor will be called when product will be readed from db or deserialized from json (let's for example we are working with json files as storage) and what ctor exactly depeneds on implementation of repository or ORM conventions.

Hi Vaughn,

I am trying to understand your implementation and got stuck in understanding where "PlanBackLogItem" is used. Can you please point out if you dont mind....

Cheers,
~Hari

I don't understand why EntityWithCompositeId is a special case. For me, this code could be applied to all entities (with a composite or unique id).

• Port the leveldb persistence bits.
• Need LevelDB component for C# .NET. Using the LevelDB .NET component, port the following:
• iddd_common basic Event Store support from Java to idiomatic C#:
  • com.saasovation.common.port.adapter.persistence.leveldb
• iddd_common Event Sourcing Event Store support from Java to idiomatic C#:
  • com.saasovation.common.port.adapter.persistence.eventsourcing.leveldb

Started work here: https://github.com/yreynhout/IDDD_Samples_NET

   void When(IDomainEvent e)
    {
        (this as dynamic).Apply(e);
  }

    protected void Apply(IDomainEvent e)
    {
        this.mutatingEvents.Add(e);
        When(e);
    }

This code doesn't work, it generates an StackOverflow exception due to it's infinite recursion.

I would like to give my contribution to the project. But i'm little bit confused about current project structure. Where should be placed unit test projects due to actual project convention?