Given the behavior you've described, I suspect this behavior can only be fixed by the Visual Studio team.

There may be a workaround; however, I'm not aware of one.