I encountered the same issue while using Visual Studio version 17.2. To resolve it, I updated to version 17.12.3, which successfully fixed the problem.