Steven

What you are seeing are copy-paste errors. The constructors should of course be named after their class. Feel free to send a PR with a fix.

Here's a starting point for some best practices: - **DO** Configure your container in one place: The Compostion Root - **DO NOT** let application code depend on the container -...

Does it help if we support you using donations?

What alternatives for Sage are there? Any tool or add-on that comes close to Sage?

The "best" is always subjective, but... if you can, choose one pattern for the complete application, meaning: Either you make everything synchronous or you make everything asynchronous. Having two models...

You can have both synchronous and asynchronous interfaces, while having an asynchronous caller. The trick is to have an async-to-sync adapter implementation, such that the caller has no idea that...

Currently, there's no way to let Simple Injector warn you about you about this. This is mainly because Simple Injector's generic-type sub system was created way before non-nullable reference types...

Although Simple Injector does integrate with ASP.NET Core, it does so by running Simple Injector side-by-side with the built-in DI Container. This is contrary to how Containers like Autofac function,...

Generally speaking, by taking a hard dependency on `IServiceProvider` you are tightly coupling to the .NET DI infrastructure, making it harder, if not impossible, for non-conformig containers, like Simple Injector,...

> ...although I do not exactly know why here Let me explain. I previously referred to MVC's `IControllerActivator`, and I think this is a good analogy to understand what I...