@Ganado, yeah, I've been inundated with similar errors to what's shown at your link from VS 2019 lately. I've noticed that even when a statement is typed correctly sometimes Intellisense goes loopy until I close the project and reopen it. Intellisense has gotten especially trigger-happy with the last couple of updates to VS.
I can be in the midst of typing a statement, Intellisense jumps and flags what I've typed as wrong. Refusing to update even after finishing typing.
Annoying, absolutely, but it is something I've gotten used to, working around it when needed.
vs 2019, the # was there, its just like I typed it. I never did figure out what its problem was, I was having some major configuration problems with a new install, though. I think it was related to that.
yea I fixed it by mimic of a peer's installed / uninstalled bits. I just posted cause it struck me funny, really. But I appreciate the tip. Getting used to the limitations again... I skipped from the original .net or 2008ish to 2019 and find they took out so much... no tenbytes, no assembly in 64 bit, no editing macros (notepad ++ is a better editor now, for shame M$), #ifndefs are broken if stuck using PCH (I am), ... its gone downhill in nearly every way.
Oops, not quite what I meant. I meant that there's hardly anything that can go wrong with it that's not your fault. For instance, VS is so complicated (for simple people like me) that 8 times out of 10 I will hit the wrong thing when I want to compile, and it deletes stuff, or something like that. Or it does something weird and then I have to figure out how to fix the darn thing.
Did I say that errors aren't helpful? If I did, I didn't mean it, if it weren't for errors my programs would suck.
Oh, ok. I said that "it's also less helpful if there are errors in your code." Meaning the command line.
I don't know why I said that, maybe I was tired or drunk or something (kidding, I haven't been drunk since high school). But it is helpful, especially if you set the -Wall and -Wextra flags.