{"id":22365,"date":"2018-04-26T20:00:00","date_gmt":"2018-04-26T20:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/premier_developer\/?p=22365"},"modified":"2019-02-21T09:22:06","modified_gmt":"2019-02-21T16:22:06","slug":"setting-up-net-core-configuration-providers","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/premier-developer\/setting-up-net-core-configuration-providers\/","title":{"rendered":"Setting up .NET Core Configuration Providers"},"content":{"rendered":"

In this blog post, Premier Developer Consultant Randy Patterson<\/a> teaches us how to set up .NET Core configuration providers in Visual Studio. He shows how to look at NuGet packages to access the Configuration API and then setup the providers as ASP .NET Core web applications.<\/p>\n

\n

ASP Core uses the convenient Provider Pattern<\/a> to load configuration key\/value pairs from various sources and expose those to you as a single Configuration object. This allows you to grab a configuration key like ConnectionString<\/em> with one line of code regardless of where it was sourced from. However, the configuration API is not available by default in .NET Core Console applications.<\/p>\n

In this article we will look at the Nuget packages necessary to access the Configuration API and setup the same providers as ASP Core web applications.<\/p>\n

Create a .NET Core Console Application<\/h2>\n

In Visual Studio 2017<\/em> go to .NET Core<\/em> Then Console Application<\/em> and give it a name like \u201cMyCoreConsoleApp\u201d<\/p>\n

Next, add a JSON<\/a> configuration file with the name of appsettings.json<\/em><\/strong> as the first source of configuration keys.<\/p>\n

<\/p>\n

Be sure the property \u201cCopy to Output Directory\u201d<\/em> is set to \u201cCopy Always\u201d<\/em> for the newly added JSON file. This will ensure that the file is published with the application.<\/p>\n

\"E:\\SystemTemp\\SNAGHTML198df66e.PNG\"<\/p>\n

Replace the contents of the appsettings.json<\/em> file with the following content:<\/p>\n

{<\/code><\/p>\n

\"Message\":\"Hello from appsettings.json\"<\/code><\/p>\n

}<\/code><\/p>\n

This will set the property \u201cMessage\u201d to the value of \u201cHello\u2026\u2026\u201d<\/p>\n

Write Some Code<\/h2>\n

Before we update the application, we need to add the Nuget package that contains the provider needed to load JSON configuration files.<\/p>\n

install-package Microsoft.Extensions.Configuration.Json<\/code><\/p>\n

Next, replace the contents of the Main method with the following code.<\/p>\n

static void Main(string[] args)<\/code><\/p>\n

{<\/code><\/p>\n

IConfiguration config = new ConfigurationBuilder()<\/code><\/p>\n

.AddJsonFile(\"appsettings.json\", optional:true, reloadOnChange:true)<\/code><\/p>\n

.Build();<\/code><\/p>\n

Console.WriteLine($\"Contents of Message Property: {message}\");<\/code><\/p>\n

Console.ReadKey();<\/code><\/p>\n

}<\/code><\/p>\n

This will load the appsettings.json file into the configuration object extracting each property and value. In our case we have one property defined named Message<\/em> set to the value of \u201cHello from appsettings.json<\/em>\u201d. The WriteLine <\/em>method will display the value of the Message<\/em> property to the console window.<\/p>\n

Running the application yields the following output.<\/p>\n

<\/p>\n

You\u2019ve successfully loaded configuration data from an appsettings.json file.<\/p>\n

Add Environment Variables<\/h2>\n

Next, add the Environment Variables Provider by installing the following Nuget Package<\/p>\n

install-package Microsoft.Extensions.Configuration.EnvironmentVariables<\/code><\/p>\n

and update the Main method to include the provider<\/p>\n

IConfiguration config = new ConfigurationBuilder()<\/code><\/p>\n

.AddJsonFile(\"appsettings.json\", optional:true, reloadOnChange:true)<\/code><\/p>\n

.AddEnvironmentVariables()<\/code><\/p>\n

.Build();<\/code><\/p>\n

This will load environments variables into the configuration object and is useful for cross-platform or container deployments. Furthermore, because Environment Variables are loaded after<\/strong> the appsettings.json file, any duplicate keys will replace the values from the appsettings.json<\/em> file.<\/p>\n

Next, add an environment variable named \u201cMessage\u201d to override the Message property in appsettings.json from the Project Properties Page<\/p>\n

<\/p>\n

Looking at the output displayed below you can see that the environment variables provider replaced the Message<\/em> key that was initially set in the appsettings.json file with the contents of the environment variable.<\/p>\n

<\/p>\n

Add Command Line Arguments<\/h2>\n

Finally, we\u2019ll add the Command Line Arguments configuration provider. Similar to the previous providers, the first step is to install the proper Nuget package:<\/p>\n

Install-Package Microsoft.Extensions.Configuration.CommandLine<\/code><\/p>\n

Next, update the Main method to load the new provider.<\/p>\n

IConfiguration config = new ConfigurationBuilder()<\/code><\/p>\n

.AddJsonFile(\"appsettings.json\", optional:true, reloadOnChange:true)<\/code><\/p>\n

.AddEnvironmentVariables()<\/code><\/p>\n

.AddCommandLine(args)<\/code><\/p>\n

.Build();<\/code><\/p>\n

Finally, update the project properties to add a command line argument to replace the Message property with the string \u201cHello from args\u201d.<\/p>\n

<\/p>\n

Run the application and the output should look like the following<\/p>\n

<\/p>\n

The property \u201cMessage\u201d was set three times. Once in appsettings.json file, then as an environment variable and finally as a command line argument. The last provider loaded wins any conflicts.<\/p>\n

Conclusion<\/h2>\n

.NET Core added a powerful and flexible configuration API that is available by default in ASP Core application. Simply adding a few Nuget Packages to any .NET Core application will give you the same flexibility. The order the providers are added to the configuration builder is critical as the last loaded overrides any previous values. By applying the providers in the order specified in this article (Json, Environment Variables and Command Line Arguments) you will have a similar configuration environment found in ASP Core applications.<\/p>\n","protected":false},"excerpt":{"rendered":"

ASP Core uses the convenient Provider Pattern to load configuration key\/value pairs from various sources and expose those to you as a single Configuration object. This allows you to grab a configuration key like ConnectionString with one line of code regardless of where it was sourced from. However, the configuration API is not available by default in .NET Core Console applications.<\/p>\n","protected":false},"author":582,"featured_media":37840,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[113],"tags":[83,61,314,46],"class_list":["post-22365","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio","tag-net-core","tag-asp-net-core","tag-randy-patterson","tag-visual-studio"],"acf":[],"blog_post_summary":"

ASP Core uses the convenient Provider Pattern to load configuration key\/value pairs from various sources and expose those to you as a single Configuration object. This allows you to grab a configuration key like ConnectionString with one line of code regardless of where it was sourced from. However, the configuration API is not available by default in .NET Core Console applications.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/posts\/22365","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/users\/582"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/comments?post=22365"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/posts\/22365\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/media\/37840"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/media?parent=22365"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/categories?post=22365"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/premier-developer\/wp-json\/wp\/v2\/tags?post=22365"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}