-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error after installing Microsoft C/C++ Extension #3888
Comments
We need more repro info. Are you opening a folder? Does the folder contain a ".vscode" folder and a "c_cpp_properties.json" file? Can you do an Edit Configuration command to create that file? |
Okay, thanks for the info. I'm able to repro it in the Open File scenario. It should be fixed in our next Insiders release: #3986 . |
Should be fixed with 0.25.0-insiders: https://github.com/microsoft/vscode-cpptools/releases/tag/0.25.0-insiders . |
I had faced a similar problem after update the extension. 1- Delete .vscode/c_cpp_properties.json file |
As title states, the extension from Microsoft C/C++ in the visual code's recommended extensions list keeps returning an error every time I try to install it.
The error goes like this:
Failed to parse "\.vscode\c_cpp_properties.json": ENOENT: no such file or directory, open '\.vscode\c_cpp_properties.json'
Now I also keep getting these error messages from the Problem section of the lower panel (outputs, terminal...etc):
#include errors detected. Please update your includePath. Squiggles are disabled for this translation unit (C:\Users\Jordan\Documents\sample.cpp).
cannot open source file "iostream"
I've tried reinstalling the extension & visual code multiple times...restarting my computer multiple times, but nothing seems to work. It used to work before I did a clean reset for my windows 10 computer, but now it's just acting up. Please fix this error so I can continue to create applications programmed in C++... :)
P.S, these are additional images in case anyone wants a look at them themselves:
The text was updated successfully, but these errors were encountered: