This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 27%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELP%3C/text%3E%3C/svg%3E)
Good day! I've a trouble with my Visual Studio 2022. When I trying to include a file from project directory by using #include "test.h" an intellisense is displaying an all files from other includes (like winapi and C++ files)
It's a not problem with project, because in Visual Studio 2019 all good. I just want to see only files in project directory by using #include with double quotes
Visual Studio 2019:
Visual Studio 2022:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 86%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
I assume VS2019 did the right thing if you use <>?
If so and you've not done so already, I suggest that you submit a bug report on it using VS's Report a Problem facility.
Post a link to your bug report back here so that others can find it and vote/comment on it.
Yeah, VS2019 works fine.
#include <> is displaying external includes
#include "" is displaying a local includes
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 13%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
I guess this is also potentially a case of expectations.
One big issue here is that what Visual Studio 2022 is doing is more correct according to the standard. The standard does define that the quoted form should fall back to the angled bracket form if it fails to find the header.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Thanks for sharing the ticket link here, I reproduce this issue.
It seems that the ticket has been closed as a duplicate(the reported ticket before => #Include " is now behaving the same as #include <).
It was a 1 year ago, why it doesn't be added ? I've an ADHD and I can't navigate in my file paths with #include correctly, it so hard for me because I can't figure out which catalog I'm in because of the huge.
Hi @La Psychose ,
I understand, I notice that the duplicate ticket is a suggestion ticket.
I strongly suggest you vote on that ticket and add comments there. It's helpful for suggestions collection, features improvement and progresses acceleration.
Kind Regards,
Tianyu
I hope it will be fixed soon