The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
This is a stretch, but when I am having weird system problems I sometimes go to event viewer and look at Windows Logs --> System Logs. Disk errors and other ephemera may show up around the time you had the Visual Studio problems.
We have had Visual Studio crash on us. For most, we found that disabling the source control plugin and/or deleting the intellisense file helped.
You could try running VS in safe mode to see if the problem still happens (devenv.exe /SafeMode) or you could try looking at suppressed alert messages to see if that gives you any more information (devenv.exe /ResetSkipPkgs).
At one time the members of my development team would see a symptom like this when pressing F5 to debug. In our case, we had some security software that IT required us to install. I think it was called FireAMP or something like that. Since we saw the issue start right after that was deployed, we requested permission to disable it, and that seemed to solve the issue.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Well, I ordered a Raspberry Pi 3B+ - I guess that makes me Pi-curious.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013