I've noticed that VS2022 is giving me LOTS of Intellisense errors (45 at the latest count).  However, if I select 'Build Only' instead of 'Build+Intellisense', all the errors go away. Even with the Intellisense errors turned on, the project builds and runs OK.

I have tried addressing many of these errors, but they aren't particularly fixable. For instance, Intellisense doesn't like the ellipsis mark (3 dots) in the line '  case -100 ... - 67:', and it apparently doesn't like enum identifiers that are used without the full name, i.e. 'VL53L0X_READYCHECK' as opposed to 'VL53L0X_REQUEST::VL53L0X_READYCHECK', even though the hover tag shows the full identifier correctly.

Researching this issue on the inet shows lots of complaints about Intellisense errors when using VS2022, but none of the proposed fixes (including removing the .vs folder) seem to work (or seem irrelevant) for me.

Anyone else having this problem - and maybe found a way to fix it?  If not, has anyone successfully downgraded back to VS2019?

TIA,

Frank

Here's the build log, with 'verbose' and 'build properties' enabled

Hmm, it's a pretty big program, but I'll work on that.  I assume you need it to be a stand-alone running sketch, correct?

Frank

OK, here's a small stand-alone sketch that shows two of the most prevalent Intellisense errors.  I defined a set of enums and then defined a variable of that type.  Intellisense insists that I use the full name for the enum, even though it compiles correctly.

Then I wrote a 'switch' statement using the enum variable, and did a case using ellipsis.  Intellisense flags this as an error even though it compiles correctly. 

If only build errors are shown, there are zero errors, but with 'build + intellisense', there are LOTS.

Full program folder and verbose compile output attached as a ZIP file.  Hope this helps.

Frank

Thanks Tim, for taking the time to look at this.  However, please don't go full OCD on this, as it is just an annoyance, not something that should take your valuable time away from real work 

No not yet, it will be in the release notes when it is available.