Property Injection in ASP.NET Core

by

No, the built-in DI/IoC container is intentionally kept simple in both usage and features to offer a base for other DI containers to plug-in.

So there is no built-in support for: Auto-Discovery, Auto-Registrations, Decorators or Injectors, or convention based registrations. There are also no plans to add this to the built-in container yet as far as I know.

You’ll have to use a third party container with property injection support.

Please note that property injection is considered bad in 98% of all scenarios, because it hides dependencies and there is no guarantee that the object will be injected when the class is created.

With constructor injection you can enforce this via constructor and check for null and the not create the instance of the class. With property injection this is impossible and during unit tests its not obvious which services/dependencies the class requires when they are not defined in the constructor, so easy to miss and get NullReferenceExceptions.

The only valid reason for Property Injection I ever found was to inject services into proxy classes generated by a third party library, i.e. WCF proxies created from an interface where you have no control about the object creation. And even there, its only for third party libraries. If you generate WCF Proxies yourself, you can easily extend the proxy class via partial class and add a new DI friendly constructor, methods or properties.

Avoid it everywhere else.

More Related Contents:

  1. When are .NET Core dependency injected instances disposed?
  2. ASP.Net Core Call a controller from another controller
  3. Net Core Dependency Injection for Non-Controller
  4. Ioc/DI – Why do I have to reference all layers/assemblies in application’s entry point?
  5. Why not use an IoC container to resolve dependencies for entities/business objects?
  6. Why do I need an IoC container as opposed to straightforward DI code? [closed]
  7. What is a composition root in the context of dependency injection?
  8. Why does one use dependency injection?
  9. Inversion of Control vs Dependency Injection
  10. Inversion of Control < Dependency Injection [closed]
  11. Dependency injection through constructors or property setters?
  12. Why would one use a third-party DI Container over the built-in ASP.NET Core DI Container?
  13. .NET Core DI, ways of passing parameters to constructor
  14. When to use PerThreadLifetimeManager?
  15. What are the costs and possible side effects of calling BuildServiceProvider() in ConfigureServices()
  16. Use DbContext in ASP .Net Singleton Injected Class
  17. How to extend a component with dependency injection?
  18. Meaning of bean discovery mode annotated in CDI 1.1
  19. Dependency injection, inject with parameters
  20. Proper way to register HostedService in ASP.NET Core. AddHostedService vs AddSingleton
  21. Replace service registration in ASP.NET Core built-in DI container?
  22. .NET Core dependency injection -> Get all implementations of an interface
  23. What is the purpose of the getter methods in Components in Dagger 2?
  24. How do I inject ASP.NET 5 (vNext) user-secrets into my own utility class?
  25. Register AspNetCore 2.1 Identity system with DbContext interface
  26. Dependency Injection with classes other than a Controller class
  27. MEF (Managed Extensibility Framework) vs IoC/DI
  28. When to use Dependency Injection
  29. How to inject a reference to a specific IHostedService implementation?
  30. How do I handle classes with static methods with Ninject?

Leave a Comment