I upgraded my project to 4.18 and upgraded my Visual Studio from 2015 to 2017 and now I have this bug too. So it still exists in 4.18.
I upgraded my project to 4.18 and upgraded my Visual Studio from 2015 to 2017 and now I have this bug too. So it still exists in 4.18.