Dependency injection in .Net Web API project 2

7

I'm involved in a project that is developing a .Net Web API 2 Fw 4.51 application (with a view to future migration to .Net Core , which is an 'aggravating'), Fluent NHibernate e PostgreSQL , and we're choosing a IoC container that meets us satisfactorily.

We are between Unity, o Castle Windsor e o Microsoft.Framework.DependencyInjection (for this future migration issue for .Net Core we end up listing the new Microsoft tool in the list of possible candidates). Since we have instantiation based on requests to service, I would like to hear your opinion on which one is the most appropriate (or, if you would use another container).

Right now, thank you so much!

    
asked by anonymous 27.08.2016 / 12:55

1 answer

1

I would choose Unity for the simple fact that it is what I am more accustomed to and provides support for what I need (Interceptors, Flexibility to define object scope etc) and also because I have already found people using .NET core: link

    
16.02.2017 / 21:16