Is there anything special when using "Process" to call "wsl"

[andrew-at-v]

Use Case: Calling python script from my dotnet application
I notice there is difference when I run the script directly using my windows terminal vs when I try to run the python script via "Process" class for the exact same command

Mostly what happen is it's working when i run it via windows terminal, it does not work when i run it via Process class

[huoyaoyuan]

WSL (assuming WSL 2) is an external system. It can't be used with local Process api at all. The workaround is to use wsl.exe as a proxy.

The Windows Terminal session is actually a remote session.

[andrew-at-v]

what do you mean by using "wsl" as a proxy?

[huoyaoyuan]

For linux command app -switch, execute wsl app -switch as a Windows command. The wsl command will send the remaining command line to WSL.

[andrew-at-v]

oh, that's what you mean, I already did that, I even try to run with debugging directly in WSL

It's not consistent, there is some script that work, some that does not and I can't find the cause other than
one way I use my dotnet app
other way I type it within terminal....