It happens from time to time, XAML and asp.net or whatever, did it in 2012, relaunching usually fixes it.