You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The specified environment name is case insensitive. Whether you set the variable to Development or development or DEVELOPMENT the results will be the same.
I ran into this issue couple of days ago. Case matters.
For example , if you are reading a configuration file depending on the environment, file is called appsetings.production.json and variable is set to "Production". Code that might be using env.EnvironmentName will not read the file on Linux. It will try to read appsettings.Production.json.
The text was updated successfully, but these errors were encountered:
@grbinho I think it might be the case that "The specified environment name is case insensitive." is true for environment variables but not for file names.
We could make it clear that the file names are case sensitive.
In the documentation about environments
This section is not valid for Linux.
I ran into this issue couple of days ago. Case matters.
For example , if you are reading a configuration file depending on the environment, file is called
appsetings.production.json
and variable is set to "Production". Code that might be usingenv.EnvironmentName
will not read the file on Linux. It will try to readappsettings.Production.json
.The text was updated successfully, but these errors were encountered: