-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unable to use [env:key=value]
directive with 8.0.100
#37686
Comments
@jonsequitur did the env var directive get removed/obsoleted from S.CL? If so we may consider adding it back ourselves. @xt0rted are you able to use shell-specific env-var setting techniques to workaround this? |
@baronfel I've been using the cli with another dotnet tool which also uses When I was working on my tools I found I always had to opt-in to this directive like so: var parser = new CommandLineBuilder(rootCommand)
.UseEnvironmentVariableDirective()
// ...
; I've looked through the v7 sdk code and couldn't find where that was happening so I'm not sure how the cli used to wire this up. With the latest version of |
Good spot! I've added it back in #37827, we'll get it approved and merged. |
Approved and merged for release in Feb. Closing. |
I just updated to 8.0.200 and I'm still unable to run Here's the full output for a .net 7 web app using both the 7.0.406 and 8.0.200 sdks. 7.0.406dotnet --info
dotnet watch [env:DOTNET_WATCH_RESTART_ON_RUDE_EDIT=true] --verbose
8.0.200dotnet --info
dotnet watch [env:DOTNET_WATCH_RESTART_ON_RUDE_EDIT=true] --verbose
|
Describe the bug
In versions of the sdk prior to 8.0.100 I was able to pass env vars by doing
dotnet watch [env:DOTNET_WATCH_RESTART_ON_RUDE_EDIT=true] ...
but after updating to 8.0.100 I now get the following error:To Reproduce
global.json
to use8.0.100
dotnet r watch
again and you should get the above errorYou can skip the dotnet tool bit and run dotnet watch directly, happens either way.
Exceptions (if any)
Details
Further technical details
dotnet --info
Details
None, running via cli in windows terminal
The text was updated successfully, but these errors were encountered: