Skip to main content

Set the hosting environment for a .NET Core console application

ASP.NET Core has the built-in concept of an environment. This allows you to change the behavior of your application based on the detected environment. A typical example where we use this is to load different configuration values.

In your application you can access this value through the EnvironmentName property on the IHostEnvironment interface.

The Launch Profiles UI

If you want to change this environment value in Visual Studio while debugging, you can do this through the Launch Profiles UI.

To launch this window, you have 2 options:

  • Right click on your project, click on Properties.
  • Scroll down to the Debug section and click on the Open debug launch profiles ui link.

Or:

  • Click on the Dropdown arrow next to the run icon.
  • Select <Profilename> Debug Properties from the dropdown menu.

    This will open the Launch Profiles UI:

    Here you can update the ASPNETCORE_ENVIRONMENT environment variable to update the environment.

    Behind the scenes this will update your launchsettings.json file:

    DOTNET_ENVIRONMENT

    But what if you want to do the same thing in a .NET Core console application? If you are using the .NET Core Worker template, you can do almost the same thing with only one big difference; instead of setting the ASPNETCORE_ENVIRONMENT variable, you should set the DOTNET_ENVIRONMENT environment variable.

    And here is the related launchsettings.json file:

    Remark: Using the DOTNET_ENVIRONMENT variable also works for ASP.NET Core applications.

    More information: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/environments?view=aspnetcore-6.0

    Popular posts from this blog

    Kubernetes–Limit your environmental impact

    Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

    .NET 9 - Goodbye sln!

    Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...
    OSZAR »