Project Dependency Injection . Net Web API 2

Question

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

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

From now on, thank you very much for the strength!

Answer 1

I would choose Unity for the simple fact that it is what I am most used to and provides support for what I need (Interceptors, Flexibility to define scope of objects etc) and also because I have found people using for . NET core: https://stackoverflow.com/a/39173346/1384539