Replies: 1 comment 2 replies
-
It would be interesting to see a screen recording. While I've seen Windows in my life, I have a hard time imagining all of the details of the process you described. @ssbarnea do you think you could do this? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
While trying to setup my test box to work with windows wsl2 code and out extension I encountered some problems:
Steps done so far
ls -s ~/c /mnt/c/Users/ssbarnea/c
so basically the folderc
that contains all the source code is in linux(wsl) home directory, same as from Windows machine.Not sure what this really means. But that is very weird as I already have the Ubuntu terminal open and running. Retrying seems to work, hopefully that was an one-time glitch.
Finally opened our code in wsl
Cannot activate the 'Test Explorer UI' extension because it depends on the 'Test Adapter Converter' extension which is disabled.
. I remember that also happened another time to me and I had to manually enable that extension, which was already installed. I am not sure what is causing this but it worth investigation as it kinda sucksHow can I make it install automatically?
npm failing to run
That seems that WSL expose windows apps to linux, such node but that does not make them work, at all. Apparently installing nvm and installing node with it works. Read https://github.com/nvm-sh/nvm#installing-and-updating as windows broken npm is not picked first.
Dev Container prompt (TBD)
Detecting WSL version
Beta Was this translation helpful? Give feedback.
All reactions