Hey, I’m sorry to bump this old thread. However this “bug” still exists in VS2017. Updating to 2019 is not suitable for all of us, especially for people stuck in strict production environments. Is there any Idea how to go fix this?