Simple Injector VS Autofac

When I was building application with .NET Framework I always used libraries like Autofac and SimpleInjector for dependency injection. I really liked to create modules (Packages in SimpleInjector) to achieve higher cohesion and lower coupling in my class libraries. I made a module for every class library in which all dependencies inside of that class library were registered. Why should my web application (for example) know if MyBeautifulService in MyBeautifulClassLibrary should be transient or singleton?

You can use SimpleInjector library to do that. Link: https://github.com/simpleinjector/SimpleInjector

My favorite DI container is LightInject. Very fast and has all the features that I need. Other good DI containers are Grace and SimpleInjector, IMO.

When I was building application with .NET Framework I always used libraries like Autofac and SimpleInjector for dependency injection. I really liked to create modules (Packages in SimpleInjector) to achieve higher cohesion and lower coupling in my class libraries. I made a module for every class library in which all dependencies inside of that class library were registered. Why should my web application (for example) know if MyBeautifulService in MyBeautifulClassLibrary should be transient or singleton?

A well-known implementation of inversion of control is dependency injection. With libraries such as Microsoft.Extensions.DependencyInjection, Autofac, and others, it is possible to list abstractions and their implementations, and the library will take care of resolving the dependencies between types.

For the first shot, I wanted to manually web the systems together. For the next iteration, I might go with an IoC framework like Autofac.

When you test and debug your scripts in your pc, it should be fine to set TargetFramework to 4.8, but in order to run binaries / standalones in Aria / Eclipse environment, target Framework version must be set to 4.5.2 for v15.x and 4.6.1 for v16.x. Btw, it looks like autofac.org shows it works for .NET 4.5.1+.

Why do you want to know this? How do you come up with a random question like that? You can check out the whole source https://github.com/autofac/Autofac if you want to know how it exactly works.

anyway about the module register https://autofac.org/

Nevertheless, with the Microsoft.Extensions.DependencyInjection being the new and good default for libraries to provide means for configuration, I want to use these extension methods to setup my dependency injection container of choice, which is Autofac.

In the past, we were using libraries and frameworks like Autofac, Castle Windsor or Unity to implement Dependency Injection in our projects but Dependency injection is now part of the ASP.NET Core. All the Framework services like Configuration, Logging, Routing, etc. are now registered in a built-in DI Container and provided to us as services wherever we need them. The basic idea is to register all services (dependencies) when the application starts and then these services will be injected and resolved at runtime.

If you would like to find out more about Inversion of Control, you can read more about it at Microsoft Docs. You can also learn more about Autofac (and fall in love with their adorable mascot) on the Autofac website.