Actually, I had this problem with versions 1.xx in VS2015 and VS2017 as well. This is one of the reasons why I never tried to do anything serious with this framework. I have a project I'm eager to try, and with the features that are coming out with ver 2.xxx, the framework should give me enough to do what I want, but I waited to see if this issue would be fixed...which it hasn't. I can do work arounds, but it's frustrating and quite interrupts the flow.
It ain't easy being green!