Skip to main content

Autofac 2.3

De cateva zile s-a lansat o noua versiune de Autofac( v. 2.3). Am dat jos ultima versiune si am inceput sa ma joc cu acesta si iata ce am descoperit:
Ce ne ofera Autofac:
  • dependency injection;
  • inversion of control( IoC);
  • suportat de diferite platforme( ASP.NET MVC, Silverlight, etc);
Nu este atat de complex precum Windsor de la Castle Project, dar ofera functiile de baza de care am avea nevoie pentru un proiect de dimensiuni mici.
Iata cum se foloseste:
Clasa de baza prin care putem sa inregistram sau sa obtinem instance este "ContainerBuilder"
var autofac=new ContainerBuilder();
Pentru a inregistra putem folosi de metoda "Register".
autofac.Register(component=> new NumeClasa());
Pentru a obtine o componenta din container trebuie apelata metoda "Resolve":
autofac.Resolve<NumeClasa>();
In cazul in care constructorul clasei noastre are nevoie de anumiți parametrii care au fost deja înregistrați putem sa apelam metoda "Resolve" in momentul in care înregistram componenta:
autofac.Register(component=> new NumeClasa(componenta.Resolve<ClasaInregistrata>()));
Sunt cazuri cand dorim sa inregistram o componenta ca si un serviciu cu un tip diferit fata de componenta pe care vrem sa o adaugam. In acest caz metoda "As" ne vine in ajutor:
autofac.Register(component => new NumeClasa()).As<INumeClasa>();
Sunt momente cand vrem o modalitatea in care sa controlam momentul in care se face dispose pe componenta pe care am inregistrat-o. Autofac ne vine in ajutor.
autofac.Register(component => new NumeClasa()).ExternallOwned();
Dar in acest caz trebuie sa implementam interfata "IDisposable" si sa o apelam noi explicit cand este nevoie de metoda "Dispose".
In mod normal, durata de viata a unei componente este egala cu durata de viata a aplicatiei, dar putem seta ca aceasta sa existe: pe thread, pe apel HTTP sau la fiecare apel sa se creeze o noua instanta a componentei.
Pentru a avea o singura instanta in toata aplicatia trebuie sa facem in felul urmator:
autofac.Register(component => new NumeClasa()).SingleInstance();
Pentru a avea instante diferite trebuie sa apelam metoda "InstancePerLifetimeScope" in loc de "SingleInstance". Prin intermediul ei putem sa obtinem instanțe unice pe thread sau pe request.
De exemplu ca sa avem o instanta unica pe thread putem sa facem urmatorul lucru:
var container=new ContainerBuilder();
autofac.Register(component => new NumeClasa())
......
//iar in interiorul la threadul nou
using(var perThread = container.BeginLifetimeScope())
{
....
//Instanta unica pe thread.
var numeClasa = perThread.Resolve<NumeClasa>();
}
Cam complicat, nu? Puteau sa ascunda acest mecanism, iar la apelul metodei resolve sa obtinem direct o instanta unica pe thread.
Toate configuratiile se pot face si in fisierul de configurare, care sunt extrem de asemanatoare cu cele folosite de Windsor.
Concluzie: Este o solutie simpla si foarte usor de folosit, dar putem avea probleme daca dorim sa facem lucruri mai complexe, Dupa cum s-a putut observa, Autofac este destul de rudimental, nu neaparat din lipsa de functionalitati, dar are un API destul de restrans, iar unele lucruri trebuie sa le definim de fiecare data sau sa ne definim un set de extension methods.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...