Since upgrading to VS 2015, my team has experienced random quirky things which I\'m sure are being worked out at Microsoft right now. One pretty annoying one is that we see
I suffered a similar issue when updating VS2017 v15.7 to v15.9.
The answer for me was to close down VS, clear out the hidden .vs folder in my solution's root directory and restart VS.
.vs