Prevent mixing MVC and Web API in the same project. Microsoft seems to suggest this, because the Visual Studio template for Web API mixes the project automatically with MVC, but this is a bad idea. From an architectural point of view, MVC and Web API are completely different. MVC is a UI technology aimed to … Read more
It’s a fair question; fundamentally the difference is in the additional features Autofac can offer you if you need them. For simple applications, the Microsoft DI may offer enough functionality, but I’ve found as my application grows there’s some extra features I find myself wanting/needing. The features that in my mind encouraged me to originally … Read more
I have met the same issue. The problem is that this line code services.AddMediatR(typeof(AddEducationCommand).GetTypeInfo().Assembly); handles all the MediatR IRequest and IRequestHandlers. but you created an IRepository interface and its implementation class which can’t be handled by that MediatR.Extensions.Microsoft.DependencyInjection so keep all your changes but add this – manually register this like services.AddScoped(typeof(IUniversityRepository), typeof(UniversitySqlServerRepository)); then issue … Read more
The migration from Ninject to Autofac seems to be correct, but the binding for the ISecureDataFormat<AuthenticationTicket> interface may not be working as expected, leading to an activation error in some dependencies. Based on the debugging messages, the BearerTokenCookieStore class is failing to resolve this dependency. In the Ninject version, ISecureDataFormat<AuthenticationTicket> is bound to a method … Read more
Let me start by saying that I’m the lead developer behind Simple Injector. I agree with Mark that in most cases performance of a container isn’t a problem. Still, some containers perform very poor at some points and it can be hard to intuitively sense what parts of the configuration can be problematic from a … Read more
Is the manual newing-up of the ServiceProductDataProvider with RegisterInstance not the same as the Register .SingleInstance() ?? The RegisterInstance allows you to register a single instance in AutoFac. The difference between RegisterInstance and RegisterType + SingleInstance methods is that the RegisterInstance method allows you to register an instance not built by Autofac. But both solution … Read more
You can always use the WithParameter method to explicitly specify a constructor parameter: builder.RegisterType<DoesSomething>() .As<IDoesSomething>() .WithParameter(“helper”, new HelperClass(“do”, “something”)); builder.RegisterType<DoesSomethingElse>() .As<IDoesSomethingElse>() .WithParameter(“helper”, new HelperClass(“do”, “somethingelse”)); As far as I can tell there is no need for an interface for HelperClass because it essentially is just a value holder. For this to work you would need … Read more
It is certainly possible to configure Autofac to work with both MVC and Web API. This is expected to be a very common scenario. There are two separate dependency resolver implementations because MVC and Web API can be used independently of one another. The same applies for the Autofac integrations. When using both MVC and … Read more
The package you need can be found by searching for “autofac webapi2” on Nuget. It is called Autofac ASP.NET WebApi 2 Integration.
InstancePerHttpRequest and InstancePerApiRequest essentially do the same thing – you get a single instance of your service for each discrete web request. I’ll use InstancePerHttpRequest for the rest of the answer, but keep in mind that these two are interchangeable. InstancePerLifetimeScope means a new instance of the service will be created for every lifetime scope … Read more