Steven

> I'm not really keen on having loads of QueryById types of queries. Is there a way we can have a QueryById to avoid those? Sure that's possible. Here's an...

> not only that but there can be situations where we need to make a query (or queries) before updating for whatever reasons. How do you handles these on CQRS?...

> Well I was thinking in having 2 repository projects for create/update/create that would only expose these and then another repository project with only the reads. That's why I was...

Upgrading the reference to .NET Standard 2.0 is a breaking change, which is why I won't fix this. For more details about the reasoning of *not* updating, please read [this](https://stackoverflow.com/a/74150694/264697).

> Do you concider adding netstandard2.0 as an extra target next aside netstandard1.3 also as a breaking change? No, that should not be breaking, and that's certainly an option. That...

I reopened this issue and updated the title to reflect this. Will try to add this to the next minor release.

This whole model of adding, replacing and trying to replace registrations is built on quick sand. The order in which you make the calls is crucial, but completely depending on...

> at this point, I think the only reliable route is to follow in the footsteps of Autofac and other DI containers and create an adapter I surely don't advice...

To be honest, I don't know, but I can imagine that exception filters only work on controllers. At a broader level, I think you'd stack delegating handlers (as decorators) to...

I have no intentions to add any tests to this reference project. > what parts of the system would you usually expect to see tests for when using CQRS I...