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
{{ message }}
This repository has been archived by the owner on Nov 20, 2018. It is now read-only.
How about adding string HttpContext.ApplicationEnvironment {get;} and three bool HttpContext.IsProduction {get;}, IsStaging, and IsDevelopment booleans as a convenience for the well-known environment names
@davidfowl The env.IsEnvironment("Development") returns true whether we select Debug or Release mode from VS. Is it not good to change the environment variable value if we select different configuration? The problem is that devs are used to select Release config in order to test how the application will work in production mode.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
http://msdn.microsoft.com/en-us/library/system.web.httpcontext.isdebuggingenabled(v=vs.110).aspx
We used to have this in katana with the "host.AppMode" key in the environment dictionary. The default implementation in PipelineCore might map to the environment name "development" in https://github.com/aspnet/Hosting/blob/63f643e0c1d9be3485300a297a74b13c8ed8299e/src/Microsoft.AspNet.Hosting/HostingContext.cs#L34.
/cc @lodejard and @Tratcher for comments
The text was updated successfully, but these errors were encountered: