Thanks for reading ☺

One common gotcha is refresh:

If you’ve just set your environment variable you’ll need to “refresh” the process that you want to use it. For example if you open a Visual Studio instance and then go and edit your environment variable than that VS instance won’t see them until restarted.

Child processes inherit the environment variables. For examples running `cmd` `set A=myVar` and `code .`(start VS Code) then that code instance will have access to the environment variable A with value ‘myVar’.

Really lacking details there. If you could share some perhaps I can be of help:

What’s your use case?

Do you use the standard WebHost.CreateDefaultBuilder?