One of the key features of ASP.NET Core is baked in dependency injection. Whether you choose to use the built in container or a third party container will likely come down to whether the built in container is powerful enough for your given project. For small projects it may be fine, but if you need convention based registration, logging/debugging tools, or more esoteric approaches like property injection, then you’ll need to look elsewhere. Why use the built-in container? One question that’s come up a few times, is whether you can…
Using dependency injection in a .Net Core console application
Read More