When I try to open VS Code it shows a blank screen.
VS Code on opening
Then as suggested by some other answers I tried adding --disable-gpu to the target which is given as: "C:\Users\Yash\AppData\Local\Programs\Microsoft VS Code\Code.exe"--disable-gpu
On clicking OK. I have the following error.
Post the suggested solution
Please tell me what to do.
I know I am late for this answer, but unfortunately nothing worked above mentioned answers. So here is my answer:
I uninstalled the VS code completely from my machine following steps from this link: https://debug.to/1074/how-to-uninstall-vs-code-completely#:%7E:text=1%20Go%20to%20Visual%20Studio%20Code%20path.%20%25LocalAppData%25%5CPrograms%5CMicrosoft,the%20.vscode%20folder%20at%20the%20below%20path%20%25UserProfile%25
I then disabled my anti-virus software. In my case, it was Quick Heal security (expired).
I installed the VS Code again on my machine, and IT WORKED!
I have been looking into this issue since 3 days! And finally, I am happy that it is working.
the file JS.NEMUCOD.AF prevents desktop from showing its contents
when antivirus quartines this files vscode doesnt work properly
Related
Emmet Abbreviations are not working for me in VS Code. I looked up solutions, and added "emmet.triggerExpansionOnTab": true to my settings.json file.
When I added it, every time I pressed tab to indent it says "command 'emmet.expandAbbreviation' not found".
It stops showing that once I remove the line.
Additionally, there is no syntax coloring or suggestions in HTML files. I tried to fix it by adding "files.associations": {"*.html": "html"} but that didn't work either.
Does anyone know how to fix this?
I had this issue too, but I simply restarted VS Code and that actually solved the problem!
I had the same issue as well and could not find much help.. but what fixed it for me was using a previous version.. so something with the never version might not work with my settings I guess (and some them I can't change like my Mac OS..;-).. as my mac is 2015 edition).. Anyways if you are still having this issue.. this link is what worked for me..
https://code.visualstudio.com/updates/v1_55
Download an earlier version and you should be fine...
I simply commented out "emmet.triggerExpansionOnTab": true then it started working.
After trying a lot of different things (including re-installing vscode) I got desperate, disabled all of my extensions, reloaded vscode, and then reinstalled my key extensions. I didn't figure out which extension may have been causing the problem, but that did get it working again.
I solved it by re-enabling the emmet extension again. Not sure when it has been disabled.
Open the built-in extensions explorer (direct command: Extensions: Show Built-in Extensions), scroll down to find the emmet extension. For me it was disabled, and I had to open the context menu and click Enabled.
I recently encountered this problem after a VS Code update. I searched for disabled extensions and saw that, to my surprise, some 2/3 of my extensions have been disabled. I manually enabled one which seems to have triggered something because within seconds all these extensions (except those I actually had disabled some time ago) were live again.
I have Live-Server extension installed in my VSCode.
I was trying to run the live-server but a pop-up appeared as below:
This is a reminder to make sure that you have not forgotten to attach 'c\Users\HP\AppData\Local\Temp\ritwickdey.LiveServer-unresponsive.cpuprofile.txt' to an existing performance issue.
I couldn't find much recourses to understand what the issue was or what action I should take about it.
BTW: Live Server is not loading the browser-page by its own, but at port:5500 its running.
Please Help.
after researching i found this blog, where i got to know that its because of performance issue
https://www.nicoespeon.com/en/2019/11/fix-vscode-extension-performance-issue/
first thing bundle your vsCode extensions:https://code.visualstudio.com/api/working-with-extensions/bundling-extension
if that solves the issue then great if not then add this extension to vsCode
https://marketplace.visualstudio.com/items?itemName=nicoespeon.abracadabra
hope the first link will provide complete solution.
Happy Learning
Typing in the integrated terminal in VS Code on Big Sur is very annoyingly laggy and slow. This is the only application that experiences this, iTerm, etc. do not experience this issue. I tried disabling all plug-ins, themes, fonts, etc. to try to get to root cause.
Based on the thread here I was able to successfully mitigate the issue by running this command: codesign --remove-signature /Applications/Visual\ Studio\ Code.app/Contents/Frameworks/Code\ Helper\ \(Renderer\).app and restarting VS Code, the lag is completely gone and everything is back to normal.
If you trust VS Code developer then removing the signature should not be an issue but YMMV.
For me, I was super happy to find this solution, as it was driving me crazy.
Probably an update on Konstantin Popovskikh's answer that was deleted.
In settings.json, setting this:
"terminal.integrated.gpuAcceleration": "off",
Helped a lot for me, however it does have the side effect of not rendering underscores while typing - but for me, this is the lesser of two evils.
Note: You don't appear to have to reload the session you can just save the .json file and the terminal will update (you can visibly see it change slightly).
Overnight, any help I had for Unity3D in VSCode, i.e. intellisense, disappeared. And I get the sense, no pun intended, that I'm not the only one who's afflicted.
I've tried updating and reinstalling what I assumed VSCode needed to make Unity3D intellisense work. And have checked and re-checked settings, reinstalled VSCode package, in Unity3D.
I've worked through a few tutorials that claimed to address the issue.
What else does VSCode depend on to make this relationship work?
Thanks! Here's to hoping you've fixed this and your life has gotten easier!
Try going to Edit > Preferences > External Tools > Regenerate Project Files (This is because of a bug where the VS Code extension doesn't generate the project files correctly the first time, you can check it out here).
You'll need to be using the VS Code Editor Extension 1.2.0 (you can check which version you're using in the package manager) or later for that option to appear. Also if for whatever reason there are 2 .sln files in your project folder (I've had that happen before, though it's less likely), that also causes problems.
Ok. First, thanks to Lightning_A and Charleh!
The resolution to my specific circumstance was to install the VSCode extension "Unity Snippets Modified" https://github.com/with-heart/vscode-unity-snippets
I had been using https://github.com/kleber-swf/vscode-unity-code-snippets.
Perhaps it's just a matter of Kleber's extension, which is/was great, was broken upon updating Unity to 2020? I dunno and don't have the time to look into it, unfortunately.
Hopefully, my question, the answers I received, and my subsequent resolution saves others from the rabbit-hole I went down.
Again, thanks everyone!
Using Visual Studio Code I have installed a few extensions (like Guidelines showing vertical dotted lines between pairs of matching brackets). When I start VS Code I can see all my extensions working fine in the Editor window.
However, when I switch to another tab within VS Code, I no longer see the Guidelines or evidence of any extension working in the new editor tab. Worst of all, when I then switch back to my original tab, all the guidelines etc that were there a few seconds ago are gone!
To fix the issue I have to restart VS Code. This can't be right! Has anyone hit the same problem?
I have tried uninstalling VS Code where it warns me some components could not be uninstalled and I have to do them manually. It doesn't tell me which. When I then reinstall, the extensions are visible (without me reinstalling them) but again I hit the same issues as above.
Please help?
Seems like having too many extensions installed, or perhaps one that is misbehaving behind the scenes, causes this problem. Reduce the number of installed extensions. Use Help->Developer Tools -> Console to see if there are any messages relating to the Extensions server