Fredrik Høisæther Rasch

The issue described in the [comment above](https://github.com/dotnet/command-line-api/pull/951#issuecomment-669579258) was solved by capturing the `ExecutionContext` when running the culture-directive handler. The captured context is stored in a new internal property on `InvocationContext`....

@jonsequitur > So I would propose removing the dedicated directives and saying that in order to set the culture via a directive, people should use the `[env]` directive. On this...

**Update**: because of the work in #1013 I discovered that Localization features (e.g. in `Microsoft.Extensions.Localization`) usually use `CurrentUICulture` to decide what culture to use for localization. In order avoid situations...

As @jonsequitur pointed out here https://github.com/dotnet/command-line-api/pull/1013#discussion_r466529245 capturing the ExecutionContext as described [in the comment above](https://github.com/dotnet/command-line-api/pull/951#issuecomment-669599161) feels very heavy handed. We could of course simply add a light container on InvocationContext...

@jonsequitur > The environment variable approach has the advantage of not necessarily being an implementation detail of the parser, and of flowing to downstream processes in a well-understood manner. It's...

In plain HTML his works as a workaround: ```html ```

I have started work on PR #2450 where I will add new examples to `HostingPlyground` on how to use the .NET Generic Host. This PR also introduces a new feature...

I have started work on PR #2450 where I propose new overloads to `UseHost` that accept `HostApplicationBuilder`.

In many cases the prefix is the enum member type name. So, in order to keep it simple, I suggest `--config strip-enum-type-from-member-name` which would simply strip the enum member type...

@tlmii Hmm, I am using a non-English keyboard (Norwegian Bokmål) in my case, but I am not using AltGr in today' crash. Related to the issue described I also noticed...