Autofac
An addictive .NET IoC container (by autofac)
Castle Windsor
Castle Windsor is a best of breed, mature Inversion of Control container available for .NET (by castleproject)
Our great sponsors
Autofac | Castle Windsor | |
---|---|---|
13 | 1 | |
4,376 | 1,503 | |
0.7% | 0.1% | |
7.5 | 3.6 | |
15 days ago | about 1 month ago | |
C# | C# | |
MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Autofac
Posts with mentions or reviews of Autofac.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-03-25.
-
Modular Dependency Injection in .NET
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?
-
Optimizing .NET solution architecture for faster compilation through project decoupling
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.
-
"7D Mad Rogue Kart" post-mortem
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.
- Autofac Resovle with type stored in variable
-
Aria Access Issue with System.Net.Http
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+.
-
AutoFac question
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.
-
I am new to programming, I am learning python, I visit this sub quite often, everyone dislikes Pyhton here, and...
anyway about the module register https://autofac.org/
-
Modularize ASP.NET DI configurations using Autofac
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.
-
A Step by Step Guide to ASP.NET Core Dependency Injection
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.
-
Introduction to Aspect-Oriented Programming (AOP) in .NET with Autofac Interceptors
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.
Castle Windsor
Posts with mentions or reviews of Castle Windsor.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Just saw a new pattern, I call it "almost factory"
Most of the DI containers have a feature of resolving components by name. Here's an example of a "typed factory" that can be provided by the container and the component name can be used to select the service implementation: https://github.com/castleproject/Windsor/blob/master/docs/typed-factory-facility-interface-based.md
What are some alternatives?
When comparing Autofac and Castle Windsor you can also consider the following projects:
Unity - This repository contains all relevant information about Unity Container suit
Microsoft.Extensions.DependencyInjection
Ninject - the ninja of .net dependency injectors
Simple Injector - An easy, flexible, and fast Dependency Injection library that promotes best practice to steer developers towards the pit of success.
DryIoc - DryIoc is fast, small, full-featured IoC Container for .NET
Scrutor - Assembly scanning and decoration extensions for Microsoft.Extensions.DependencyInjection
Autofac vs Unity
Castle Windsor vs Microsoft.Extensions.DependencyInjection
Autofac vs Ninject
Castle Windsor vs Ninject
Autofac vs Microsoft.Extensions.DependencyInjection
Castle Windsor vs Unity
Autofac vs Simple Injector
Castle Windsor vs Simple Injector
Autofac vs DryIoc
Castle Windsor vs DryIoc
Autofac vs Scrutor
Castle Windsor vs Scrutor