ASP.NET Core: Accessing appsettings from another project in solution

Question

In my Startup.cs class I have the following config build which initializes the db context:

var builder = new ConfigurationBuilder()
                    .SetBasePath(env.ContentRootPath)
                    .AddJsonFile("appsettings.json", true, true)
                    .AddJsonFile($"appsettings.{env.EnvironmentName}.json",true)
                    .AddEnvironmentVariables();

Configuration = builder.Build();

NHibernateUnitOfWork.Init(Configuration["ConnectionStrings:OracleConnection"]);

NHibernateUnitOfWork is located in a different project as a class library project. I want to be able to inject (or somehow pass the settings) instead of using the NHibernateUnitOfWork.Init in my Startup.cs class.

I can build the appsettings in my class library but trying to avoid that.

What is a sane way to do this ?

See my answer here stackoverflow.com/questions/43080695/…

Razor
– Razor

2017-09-30 09:25:33 +00:00
Commented Sep 30, 2017 at 9:25 — Razor
– Razor, Commented Sep 30, 2017 at 9:25

John Laffoon · Accepted Answer · 2017-05-19 14:42:37Z

5

You can inject it.

In your Startup.cs class, you can add the following to your ConfigureServices(IServiceCollection services) method:

services.AddSingleton(Configuration);

From there, you can use constructor injection and consume it downstream the same way you normally would:

public class SomeClass
{
    public SomeClass(IConfigurationRoot configuration) 
    {
        NHibernateUnitOfWork.Init(Configuration["ConnectionStrings:OracleConnection"]);
    }
}

NOTE: This assumes Configuration is defined in your Startup.cs class:

public static IConfigurationRoot Configuration;

edited May 19, 2017 at 14:42

answered May 19, 2017 at 14:37

John Laffoon

2,9152 gold badges27 silver badges38 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Community · Accepted Answer · 2017-05-23 12:18:20Z

0

See this: Read appsettings json values in .NET Core Test Project

Essentially this is an integration solution using the TestServer. But if you're having to use the configuration, then it should probably be an integration test anyway.

The key to using the config in your main project inside your test project is the following:

"buildOptions": {
  "copyToOutput": {
    "include": [ "appsettings.Development.json" ]
  }
}

which needs to go inside your main project's project.json

edited May 23, 2017 at 12:18

CommunityBot

11 silver badge

answered Nov 2, 2016 at 13:48

tonycdp

3483 silver badges10 bronze badges

Collectives™ on Stack Overflow

ASP.NET Core: Accessing appsettings from another project in solution

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related