[ad_1]
\n<\/p>\n
Classes that are injected with dependencies usually don’t use the concrete classes ( Whenever the framework encounters a constructor (in this case the constructor of the controller) that “wants” an interface it has too look up which concrete class it should use for injection.<\/p>\n The relationship between “class wants type X” and “framework will inject it with type Y” is defined in the There are three options for defining the above relationship, that differ in the lifetime the object created by the dependency injection framework is alive.<\/p>\nUserManager.cs<\/code>) for their constructor parameters, but rely on interfaces e.g. IUserManager<\/code>. Although it is possible to use concrete classes, an interface provides looser coupling which is the reason for using dependency injection in the first place.<\/p>\nWhere<\/h1>\n
ConfigureServices<\/code> method in Startup.cs<\/em>.<\/p>\nWhat<\/h1>\n
1. Decide on the lifetime of the created object<\/h3>\n