comments

It seems like this happens during the first VS session after a new build has been installed. So far, the 3 times I’ve seen it was right after I had installed a new build. Restart VS and the problem goes away and doesn’t come back until the next build.

This is on a machine where I have not built PTVS or NTVS from sources. I first noticed the issue in NTVS, but today it happened in PTVS, using today’s rolling builds.