We use the SDK Path for multiple things (launching Dart but also the analysis server snapshot) so changing that isn't a good solution. We also probably don't want to run the analysis server inside WSL in case the proxying adds any latency (Dart Code communicates with it over STDIN/STDOUT).

So, probably the way to do this would be to allow you to specify a custom location for the Dart executable used for launching and debugging (since this is user-provided we don't need to make any assumptions about the file extension).

Some additional complications:

Can we connect to the debugger (we launch Dart with some flags that open a web server that we use to talk to the debugger - we need to be sure that inside WSL when it's binding to localhost ports we can connect to them as normal from the Windows side)
Do we need to map the paths for use inside WSL? (eg. if we run proxy\dart.bat C:\MyStuff\MyThing.bat can Dart inside WSL use that path? I guess not?)
If paths need translating, this will need doing in the debugger too, so that when we send breakpoints (or receive pause events) they are handled correctly. We already do a lot of path mapping for Flutter (since it runs on the remote device) so possibly we can extend that to work here

I had a quick Google, and it looks like path mapping is required, but probably quite straight forward:

C:\Users\me\Documents\GitHub -> /mnt/c/Users/me/Documents/GitHub

Since we already send multiple paths per breakpoint (Dart, Flutter etc. are a little inconsistent) probably we can just do this conversion always to avoid you having to set an option to say it's WSL and paths need translating.

Again; I can't promise to look at this soon, but it does seem like a neat feature to support so I would like to have a go.

Support running through in WSL through VS Code Remote Development extensions #435

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions