ASP.NET Core hosting environment variable ignored

Question

I have two web sites on my staging server, and both are ASP.NET Core sites that run in IIS. I have set the environment variable ASPNETCORE_ENVIRONMENT to Staging machine-wide. This works well for one of the sites, however the other ignores the variable and runs in production mode instead. I have to configure the hosting environment into the web.config file to run it in staging mode.

Why does one site not take the environment variable into account?

In both of my Startup(IHostingEnvironment env) constructors, I use the environment variables:

public Startup(IHostingEnvironment env)
{
    var builder = new ConfigurationBuilder()
        .SetBasePath(env.ContentRootPath)
        .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
        .AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true)
        .AddJsonFile("logging.json")
        .AddEnvironmentVariables();  //   <---
        Configuration = builder.Build();
    }

just to double check - you sure, that ASPNETCORE_ENVIRONMENT=Staging on second instance, but env.EnvironmentName returns "Production" for it and values from appsettings.Staging.json are not used? By the way don't you forget to publish appsettings.Staging.json file? — Set
– Set, Commented Oct 17, 2016 at 13:20
I don't use appsettings.Staging.json on either site. ASPNETCORE_ENVIRONMENT is set machine-wide. Startup logging for second site logs: "Environment: Production". — Thaoden
– Thaoden, Commented Oct 17, 2016 at 14:13
could you check what Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT") returns? — Set
– Set, Commented Oct 17, 2016 at 14:25
[09:20:33 INF] ASPNETCORE_ENVIRONMENT = '' Hosting environment: Production when starting via IIS, [08:56:07 INF] ASPNETCORE_ENVIRONMENT = 'Staging' Hosting environment: Staging when starting stand-alone directly on console. — Thaoden
– Thaoden, Commented Oct 18, 2016 at 7:22
Possible duplicate of IIS doesn't use user environment variables — Judy007
– Judy007, Commented Nov 28, 2017 at 22:46

Thaoden · Accepted Answer · 2016-10-18 07:47:24Z

33

As said in this similar question, the trick was simply to set the app pool to load the user variables (IIS -> Server -> App Pools -> Right click on pool -> Set application pool defaults... -> Load User Profile = True).

I configured only one of my app pools accordingly, thus only one of the sites could access the environment variables.

answered Oct 18, 2016 at 7:47

Thaoden

3,6004 gold badges36 silver badges45 bronze badges

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

4 Comments

Sam Over a year ago

I've tried this for my similar problem and it does not fix for me.

Alexey Koptyaev Over a year ago

Worked for me too. I'm wondering why setting the environment variable as a machine variable didn't work..

fuzzy_logic Over a year ago

Worked for me too, very strange according to MS doco machine env var should work..

serge Over a year ago

don't use set, but setx when setting the env var from the command line. and add /M to set machine wide, not for local user, because the app pool could use another user

Chris Pirie · Accepted Answer · 2016-10-18 06:02:59Z

23

I just spent the last couple hours dealing with the same issue. I'm not sure if the result will be the same since you seem to have one of two applications working.

I set the ASPNETCORE_ENVIRONMENT to "Staging" as a system variable through "Advanced System Settings" on Windows Server 2008 R2 and always ended up in the "Production" environment (which is the default environment if it can't find the setting anywhere).

Using "set" from Command Prompt showed the expected results of "ASPNETCORE_ENVIRONMENT=Staging".

Calling Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT") returned null. I created another variable called "Test" which also returned null. Calling any other existing variable returned expected results.

I tried recycling the application pool, changing the app pool's user, restarting IIS through management console, even restarting World Wide Web Publishing Service (probably same as reset in IIS mgmt console) all to no avail.

Rebooting the server was the only way I could get the application to return the expected result.

answered Oct 18, 2016 at 6:02

Chris Pirie

4211 gold badge4 silver badges9 bronze badges

2 Comments

gavin Over a year ago

holy sxxx, wasted 30 minutes of my time for this issue, thank you for your post

Sandeep Ingale Over a year ago

I can also confirm that only restarting the server worked. Since it's system variable only after restarting the server takes new variable.

Peter Mortensen · Accepted Answer · 2020-03-01 00:48:49Z

16

If you are debugging your code in Visual Studio, bear in mind that Visual Studio caches the environment variables that were present when Visual Studio was started - not when you hit "debug"!

So you may have to restart Visual Studio for any changes to the environment to be visible.

edited Mar 1, 2020 at 0:48

Peter Mortensen

31.4k22 gold badges110 silver badges134 bronze badges

answered Aug 9, 2018 at 13:25

Sean

3894 silver badges5 bronze badges

Comments

spottedmahn · Accepted Answer · 2024-09-20 20:13:40Z

8

From a cmd window, run net stop /y was && net start w3svc.

Source: ASP.NET Core Docs -> Use multiple environments in ASP.NET Core -> Windows - IIS deployments

Note: Restarting IIS via right click-> stop -> start in IIS Manager will NOT work.

edited Sep 20, 2024 at 20:13

answered Sep 20, 2018 at 17:17

spottedmahn

16.2k21 gold badges124 silver badges204 bronze badges

3 Comments

serge Over a year ago

the article says restating is the second option

spottedmahn Over a year ago

"Restart the server", yes, it does say that. Feels very heavy handed to me @serge

Todd Ropog Dec 17, 2024 at 20:16

This worked for me. Crazy that you have to hit it that hard to get it to update.

Thaoden · Accepted Answer · 2016-10-17 11:53:37Z

-6

public Startup(IHostingEnvironment env)
    {
        var builder = new ConfigurationBuilder()
            .SetBasePath(env.ContentRootPath)
            .AddJsonFile("appsettings.json", optional: true, reloadOnChange: true)
            .AddJsonFile($"appsettings.{env.EnvironmentName}.json", optional: true);

        if (env.IsDevelopment())
        {
            // For more details on using the user secret store see http://go.microsoft.com/fwlink/?LinkID=532709
            builder.AddUserSecrets();
        }

        builder.AddEnvironmentVariables();
        Configuration = builder.Build();
    }

You might not have added variable builder.AddEnvironmentVariables();

edited Oct 17, 2016 at 11:53

Thaoden

3,6004 gold badges36 silver badges45 bronze badges

answered Oct 17, 2016 at 11:33

Jagmeet Kumar

95 bronze badges

4 Comments

Thaoden Over a year ago

I checked this, it is there in both projects.

Set Over a year ago

AddEnvironmentVariables() does not change the value of env.EnvironmentName. It allows ro read configuration values from environment variables.

Thaoden Over a year ago

Does IsDevelopment() work without AddEnvironmentVariables()?

Set Over a year ago

@Thaoden IsDevelopment is just wrapper around env.EnvironmentName == "Development". env.EnvironmentName by default is set internally using ASPNETCORE_ENVIRONMENT. As IHostingEnvironment.EnvironmentName has a getter, the value can be changed directly in your code, but AddEnvironmentVariables() does not change that value, Instead it allows to use environment variables as additionla source for Configuration.

Collectives™ on Stack Overflow

ASP.NET Core hosting environment variable ignored

5 Answers 5

4 Comments

2 Comments

Comments

3 Comments

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

4 Comments

2 Comments

Comments

3 Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related