Pavel Voronin

Thanks, it's clearer now. Though why is overload required for the design-time support, why cannot tool just call `Create` with `designTime: true` ?

Ah, originally it was just `object Create(DbContext context)`. Thanks for taking time to explain. And the second question: How to register services which require some dependencies coming from asp.net core?...

@ajcvickers But do you at least agree that it's a valid concern/pain point?

@ajcvickers Ok, how would you work with the aggregates on the read-side of the application? - Define plain anemic DTOs with Navigation properties using table splitting feature? - Join aggregates...

@roji > At the same time, the concept is incredibly useful for passing a graph around That's absolutely true with one particularly important nuance: `aggregate = fixed aggregate` It's the...

@roji > Assume, when thinking about this problem, that eagerly loading the blogs with their posts is vital for performance, e.g. to avoid doing an additional roundtrip for each and...

I had some check to prevent access to Navigation properties withing aggregates: ``` /// /// Attribute for indicating that navigation property to other aggregate(s) should be used exclusively for reads,...

> The concept of an aggregate does not forbid having references outside of the aggregate. It depends on what you mean by reference. Foreign Key is also a reference. But...

[Vaughn Vernon's article](https://www.informit.com/articles/article.aspx?p=2020371&seqNum=4#) I'll mention it once again. There are very different scenarios: - DDD aggregates are intended for processing commands (write model). - Query processing is far more laxed,...

> not having navigation properties for the purposes of writing would mean no navigation properties for the purpose of reading Yes, the feature request is exactly to have navigations without...