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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

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

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too