Steven

Hi @KrishnaKollu, Whether or not the `DynamicQueryProcessor` (mediator) is effectively a Service Locator, depends on where it's used. You already mentioned this in your question. As you might recall from...

> Do you have any recommendations for how to make it more clear what the consumer is using? i.e. would it make sense to do that via code comments? Adding...

I skimmed over the article and they indeed seem identical. My opinion hasn't changed about its use.

> The book says: Touché. The Mediator pattern I refer to in my book is _the exact same pattern_. `IQueryProcessor`, `ICommandProcessor`, and command bus are _all_ implementations of the Mediator...

> I’m not entirely clear on how the mediator solves for the LSP. A Mediator solves LSP from the perspective of the handler's client, as the Mediator's contract *promises* that...

I'm unfamiliar with Salesforce Apex and its constraints. This means I'm unable to give you any feedback on your code.

What you can try is hiding the management around showing (and disposing) your forms behind an abstraction. For instance: ``` c# public partial class FormMain { private IFormManager manager; public...

> what about if another form is called from FormUserNew so we would have chain like: FormMain (starting form) --> FormUserNew --> FormOther (how handle this form?) In that case...

Thank you for your detailed feedback. That's very much appreciated. I made some updates to the [ASP.NET Core integration guide](https://simpleinjector.org/aspnetcore) that, hopefully, reflect your feedback. Please take a look and...

Constructor injection in Forms does work, so there is something going on that we can't determine from your question. Please share are a minimal complete verifiable example.