visual studio code - Why am I getting the error: An error occurred while trying to create a file in the destination directory - Stack Overflow
vscode debugger - vs code not opening up in windows - Stack Overflow
Why does vscode tell me i have an error even though the code runs correctly?
How to fix error in Visual Studio code in regard to the visual studio developer being applied
Videos
my solution for this was to set it to always start as administrator, I don't feel like reinstalling vscode (newly installed) It's not a great solution for those who have multiple users, but I got rid of the error.
Ah, I saw that was a problem within User Permission, there were only 2 options checked. https://prnt.sc/uV-bF_q52Y3Y
I hope my solution will help you.
If you run your "vscode" as admin then you won't see this error anymore.
- Go to your "vscode" install location
- If not sure then open the start menu.
- Write vscode.
- Right click on the icon and click "Open File Location".
- In a new window there will be again an icon for the "vscode" right click on the icon
- Again and click "open file location".
- In another window, there will be an actual vscode's "exe" file.
- Right-click on this file and go to the "send" > "send on desktop" option.
- On the Desktop right-click on the icon and go to the properties
- Click on Advance Option and Check the "Run as Admin" Option
- Click Apply and Ok.
- Now if you want Right Click on this icon again and select "pin to taskbar".
Hopefully, you won't see this error again.
no need of Unistalling, just go to your vscode-setup and reinstall it. (by this procedure all of your's settings, files , extensions etc.. will be restored as it is.)
Try this; it worked for me!
- Go to the Microsoft store.
- Install VS Code from there.
- An error message may appear.
- Open VS Code and wait.
Using a web browser, I also tried the download URL that the error message provided on your system and I received a 404 "Not found" on that file.
You aren't the first person to have experienced this particular problem, apparently. Issue #9214 on the vscode-remote-server shows the same commit hash failing to download.
The response from a Microsoft Developer for VSCode there was:
a6606b6ca720bca780c2d3c9d4cc3966ff2eca12 is not the official release build- seems like you might have ended up on a private build somehow? You are also on an out of date version, so updating or uninstall/reinstall should fix it
Uninstall VSCode itself, download the installer from Microsoft directly, and reinstall.
As mentioned in the comments, if there's a ~/.vscode-server in your Linux home directory, then I would delete or rename it as well for good measure.
It's messy but quick fix (for now); running "rm -r ~/.vscode-server/" worked for me even though the delete fails because the extensions folder in .vscode-server is not empty.
If this issue happens to me again, I'll rather go inside that dir and work out what specifically to delete so that it's a cleaner solution and update this answer.
I am afraid you can't see the information in the "Error List" window. What you can do is to open "Output" windows (you find it in "View" menu or press Ctrl+W,O. The output will be not in the table form, but you will nevertheless see the information which you need:
Visual Studio 2015 has this feature:
Bit late to the punch, however you can use the shortcut Ctrl + Shift + M, which will open the problems pane.
You can use this command:
Ctrl+Shift+M
By the way, you can quickly jump to errors and warnings in the project.
Cycle through errors with:
F8 or Shift+F8
You can filter problems either by type ('errors', 'warnings') or text matching with the above search bar you'll see.
Another useful filter is 'Show Active File Only'
Reference here
I had this problem too. Deleting bin and obj folders not work. Cleaning solution not work. Various platform I need to be as is.
Helped me close solution and delete folder .vs, which is often full of problematic mess. After opening solution all false errors disappeared.
As mentioned in a comment, you can do a Clean and Rebuild. If that does not work for you, you can browse to the solution folder and within each of the project folders delete the bin and obj folders. Then perform a build.
You may also want to look into your Configuration Manager and ensure that all of your projects are set to the same Configuration (Debug/Release) and Platform (Any CPU/x86/etc...) and marked to build for that configuration.
Finally, you may also want to check the Build Order for your solution. Ensure that projects are all built in the proper order.
-- Edit:
On thing brought up in comments that I will add here was to make sure that any library projects in the solution are added as Project References rather than referencing the output DLL directly.