Closed PauloZier closed 2 years ago
Can you post a screenshot of the error given, or its contents? And, if possible, include the extension host logging, which can be found here:
The issue is in the casing of the file path, caused by this issue: #76 and PR #77 I'll try to make a fix and unit test for this, maybe with better error handling.
Thank you very much! To temporarily solve it I reverted to the previous version.
Unit tests aren't easily possible, because of #84 I have fixed the issue, and tested it in WSL
@KreativJos , is there an ETA on a release for this fix?
Thank you very much! To temporarily solve it I reverted to the previous version.
@PauloZier, Is there a trick that I'm missing for installing an older version in WSL? When I hit "Install in WSL", it's installing the most recent version (i.e. v1.6.2) regardless of me picking 1.6.1 or 1.6.0.
@BrandonAvantGMS , I don't know how it works in WSL, but in VS Code I did it this way
@KreativJos , is there an ETA on a release for this fix?
The PR has to be checked by someone else, so it depends on whether they have the time. If it is accepted, a new release will be created.
@BrandonAvantGMS , I don't know how it works in WSL, but in VS Code I did it this way
It is the same in WSL (mine isn't selectable as I installed the vsix file from my own build):
After the update, the extension is giving an error when trying to create a new .cs file. I'm using Linux [Debian 11]