Steven

I quickly went through Workflow Core's code base. What I found was that, contrary to (unfortunate) common practice, Workflow Core actually does have a decent amount of abstractions in place...

> where the constructors of the various objects may be taking longer than they should. If you can, prevent doing anything *at all* inside your constructors, except checking preconditions and...

Thank you for pointing at that old Stack Overflow answer. I updated that answer to be in line with the code snippet given above, because this is a better and...

I haven't found a way to intercept the creation of intercepting the creation of creating dependencies injected into Minimal API maps. As far as I can see, resolving services is...

See: https://github.com/dotnet/aspnetcore/issues/41863

Microsoft confirmed that an integration point is missing in .NET 6. The workaround is to create a wrapper class that allows forwarding resolving the type to Simple Injector. This is...

Hi @leoniDEV, thank you for your valuable feedback and useful links. .editorconfig seems clearly the way to go.

There are many ways to design a fluent API, but it all comes down to returning objects from registration methods that have some similarity, because this allows a single extension...

@CasperWSchmidt, I would argue against this. The added benefit of not having to type `container` is IMO limited. But, more importantly, after Simple Injector starts returning `Container` from its registration...

Hi @torarnegustad, Please consider migrating to a newer version of Simple Injector and test whether this works in that version. I suggest testing your case in v5, because in that...