Open mattywarr opened 1 month ago
Ou, I have same, I thought it's only my local bug or it's sanction bug because I'm from Russia. I have installed VSCodium but out of the box it cannot debug tests.
I don't believe this is Roslyn. Roslyn is failing to start because DevKit is failing to start. Looks like an issue reading telemetry properties?
Tagging @jonathanjyi
@mattywarr could you provide a copy of the file located at: %Temp%\csdevkit\Telemetry\Resources.json
Please "REDACT" any personal information you need to.
@mattywarr , @dositec if you delete the files under %Temp%\csdevkit and restart, does it resolve your issue?
No need to redact, the resources file looks borked.
But as you indicated, deleting the contents of the temp folder seems to have resolved it!
@jonathanjyi, the 'needs-more-info' label has been removed upon receiving further response from the original bug filer.
I
No need to redact, the resources file looks borked.
But as you indicated, deleting the contents of the temp folder seems to have resolved it!
I had the same file content but I have fixed the problem, I cleanup temp folder, and tuned bios to normal mode(was fast) + disable "x.m.p." (motherboard - ASUS).
Thanks for the updates @dositec @mattywarr , I'm investigating how these files are getting corrupted now.
Describe the Issue
When trying to use a version higher than 1.4.29, the extension fails to start on my computer and I don't know why. Only started happening late last week when I updated to latest prerelease 1.8.10 from 1.8.8. Rolling back to any version since to 1.4.29 does not work.
C# Extension Output Log
C# Dev Kit Output Log
Steps To Reproduce
Install the extension higher than 1.4.29 on my computer. It appears to be environmental in some way so not really reproducible (Works OK on my Mac)
Expected Behavior
I expect the extension to start
Environment Information
Windows 10 VS Code 1.90.2 System (Though user version is the same)