Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with environment variable case sensitivity #2012

Closed
grbinho opened this issue Oct 27, 2016 · 3 comments
Closed

Issue with environment variable case sensitivity #2012

grbinho opened this issue Oct 27, 2016 · 3 comments
Assignees
Labels
Pri2 Priority 2

Comments

@grbinho
Copy link

grbinho commented Oct 27, 2016

In the documentation about environments

This section is not valid for Linux.

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.

@Rick-Anderson
Copy link
Contributor

@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.

@Rick-Anderson
Copy link
Contributor

master issue #2028

@tdykstra tdykstra modified the milestones: Backlog, 1.1.0 Dec 5, 2016
@spboyer
Copy link
Contributor

spboyer commented Feb 9, 2017

Closing. #2424 addressed issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Pri2 Priority 2
Projects
No open projects
Development

No branches or pull requests

5 participants