This is indeed in visual studio (2015). If I can reproduce the issue in a dummy project I’ll report it. I’ve reported a case last friday.