Using Dependency Injection with .NET Core Class Library (.NET Standard)

Question

I have gone through the link:

https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers/dependency-injection

and learnt that how I can use dependency injection for Web API.

As mentioned in the above link I can use Startup (Startup.cs) class for dependency injection inside API layer. But how can achieve dependency injection for the .NET Core Class Library. Below is the screenshot how I am adding a class library.

And my project structure is

In the project “DataManagement.Repository” I have written a class “UserRepository” and in the project “DataManagement.Repository.Interfaces” written an Interface “IUserRepository”.

In the project “DataManagement.Business” I have written a class “UserManager”

class UserManager
    {
        private IUserManager _userManager;
        public UserManager(IUserManager userManager)
        {
            _userManager = userManager;
        }
    }

As you can see that I am trying to achieve dependency injection through the constructor.

But I am not sure that what changes need to be done for enabling dependency injection inside .NET Core Class Library (.NET Standard).

score 47 · Accepted Answer · answered Dec 26 '16 at 01:36

47

You don't have to do anything in your class library. Only the main application has a composition root (earliest point in an application lifecycle you can set up your object graph).

This happens in Startup.cs in your ASP.NET Core application. There you also register your dependencies:

services.AddScoped<IUserManager,UserManager>();

That's it. Class libraries don't have a composition root. Neither they should, because you can't use them without an application and the IoC Container used is a choice of the application not of the library.

You can however provider convenience methods to do this registrations, like the AddXxx method common in ASP.NET Core or some kind of module system, like in 3rd party IoC containern like Autofac or Castle Windsor.

answered Dec 26 '16 at 01:36

Tseng

52,202
10
166
183

1

as u said in answer, if i add this dependency in `Startup.cs` om asp.net core application and then i add it's reference to .NetCore class library, i can use it? – pejman Dec 27 '16 at 08:10
1

Yes, if you use dependency injection all the way (and never instantiate a service `new`) it will work – Tseng Dec 27 '16 at 08:12
1

I asked a question about this subject in `http://stackoverflow.com/questions/41342064/using-ihostingenvironment-in-netcore-library` plz give me help if u can. thanks – pejman Dec 27 '16 at 10:16
1

Does the .Api project then have to have a reference to the .Repository project in order to access the implementations of the .Repository interfaces? – WillC Jan 26 '19 at 01:27
1

@WillC: Yea, since your composition root is the web application. You can abstract it a bit away, using Extension methods (such as ASP.NET Core does with the `.AddXyz` where you do the registrations within the .AddXyz` Method. – Tseng Jan 26 '19 at 13:58
1

You can additionally hide transitive dependencies with `` (by adding `PrivateAssets="All"` to the reference (in your `Xyz.Extensions.DependencyInjection` project that contains the `.AddXyz`method). This will hide the concrete implementations in your main application, so `new ServiceA()` will result in an error, so people won't accidentally. See https://github.com/dotnet/project-system/issues/2313#issuecomment-306247396 – Tseng Jan 26 '19 at 13:58
1

my composition root is an api, where i load a plugin (dynamically). Now this plugin uses some library as nuget, how can i in this situation do registration for dependencies required by library ? – kuldeep Jul 23 '20 at 20:31

Using Dependency Injection with .NET Core Class Library (.NET Standard)

1 Answers1

Linked