In addition to other issues that PowerShell has when launched from OCL, the wsl command also does not work. Opening the distro by name (e.g. the ubuntu command), but this is not sufficient for most WSL interop workflows. The solution to this issue, as well as the one I linked above (as provided in @dubeg's answer), is to set up OCL to launch powershell.exe at the following path:
It seems to me that this path should be the default for all presets using PowerShell so that all these issues (no PSReadline, no WSL, and who knows what else) are taken care of out of the box. I don't know if this could cause any problems for people running VS on 32-bit machines, but in 2019, that's got to be hardly anybody.
In addition to other issues that PowerShell has when launched from OCL, the
wslcommand also does not work. Opening the distro by name (e.g. theubuntucommand), but this is not sufficient for most WSL interop workflows. The solution to this issue, as well as the one I linked above (as provided in @dubeg's answer), is to set up OCL to launch powershell.exe at the following path:It seems to me that this path should be the default for all presets using PowerShell so that all these issues (no PSReadline, no WSL, and who knows what else) are taken care of out of the box. I don't know if this could cause any problems for people running VS on 32-bit machines, but in 2019, that's got to be hardly anybody.