Vscode-project-manager: Opening WSL/WSL2 from local installation (Host) is not working

[alefragnani]

With the release of #345, you are now able to save/open remote projects (Docker and SSH) right from your local installation.

But it appears, based on reports, that WSL/WSL2 is not working.

This issue is to track specifically the support for WSL/WSL remote projects.

[Christilut]

Let me know if you need something tested on Windows 10 with WSL1.

[Maraat]

Also if you need something tested on WSL 2 I can try it.

[alefragnani]

Just released 11.0.1 yesterday, and based on this comment it appears WSL is working.

Could you try it? You just have to re-save the projects, to properly update its path.

Thank you

[Christilut]

Seems to work! Awesome! 🎉

Thanks for all the effort :)

[Christilut]

Few small things I noticed:

It says Path does not exist when I select List projects to open but doesn't seem to matter.

And when I'm in a WSL project, it shows all projects (including the current) when I select List projects to open but when I'm in a normal project, it shows all minus the current.

[alefragnani]

@Christilut , That’s great to hear it’s working!

When you say Path does not exist, are you talking about the _detail_ below the project name, in Command Palette? I now noticed that, at least 😬 .

I could reproduce the _show/not show_ behavior you reported. I’ll open a new issue for that too.

So now, I just need confirmation WSL2 is working too. Let’s hope for the best 😄

Thank you

[Christilut]

Yep in the Command Palette

[Kirkdeam]

WSL2 seems to work too, but with the same behavior as Christilut mentioned.

[alefragnani]

That’s great to hear!

I’ll open two separate issues, relatives to the scenarios described by @Christilut .

Thank you for reporting