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
winget doesn't support refreshing the current session when updating PATH after installation, so when Microsoft.DevProxy package is installed, users must start a new session to use the devproxy alias, if they try to run proxy an error will be thrown that devproxy cannot be found, this is also the same for Microsoft.DevProxy.Beta packages and devproxy-beta alias.
We should investigate into ways that we can handle this for the user so they can use proxy immediately after install.
The text was updated successfully, but these errors were encountered:
It seems like a known issue with winget that many folks struggle with. There are some workarounds. Since it's not specific to us, I suggest that we document it but don't try to fix it ourselves and rather align with winget.
After exploring a couple of options, we haven't found a way that's working and automatically registers the new path with the current terminal session. As such, I suggest we document the current behavior and close this issue.
winget doesn't support refreshing the current session when updating PATH after installation, so when
Microsoft.DevProxy
package is installed, users must start a new session to use thedevproxy
alias, if they try to run proxy an error will be thrown thatdevproxy
cannot be found, this is also the same forMicrosoft.DevProxy.Beta
packages anddevproxy-beta
alias.We should investigate into ways that we can handle this for the user so they can use proxy immediately after install.
The text was updated successfully, but these errors were encountered: