![Failed build Slicer in Windows10 with Visual Studio 2017,Qt 5.10.1 - Development - 3D Slicer Community Failed build Slicer in Windows10 with Visual Studio 2017,Qt 5.10.1 - Development - 3D Slicer Community](https://global.discourse-cdn.com/business7/uploads/slicer/original/3X/1/3/13da421558628a74a7e328d29add67b4a51233c7.png)
Failed build Slicer in Windows10 with Visual Studio 2017,Qt 5.10.1 - Development - 3D Slicer Community
![VS: CMake fails to configure WindowsStore project for VS 2019+ (#24207) · Issues · CMake / CMake · GitLab VS: CMake fails to configure WindowsStore project for VS 2019+ (#24207) · Issues · CMake / CMake · GitLab](https://gitlab.kitware.com/uploads/-/system/user/avatar/2547/avatar.png)
VS: CMake fails to configure WindowsStore project for VS 2019+ (#24207) · Issues · CMake / CMake · GitLab
![How to resolve msbuild is not recognized as internal or external command error in visual studio code - Debajit's Power Apps & Dynamics 365 Blog How to resolve msbuild is not recognized as internal or external command error in visual studio code - Debajit's Power Apps & Dynamics 365 Blog](https://debajmecrm.com/wp-content/uploads/2021/06/image.png)
How to resolve msbuild is not recognized as internal or external command error in visual studio code - Debajit's Power Apps & Dynamics 365 Blog
![CMake Error at CMakeLists.txt:19 (project): Failed to run MSBuild command: to get the value of VCTargetsPath: - Usage - CMake Discourse CMake Error at CMakeLists.txt:19 (project): Failed to run MSBuild command: to get the value of VCTargetsPath: - Usage - CMake Discourse](https://discourse.cmake.org/uploads/default/optimized/2X/8/824a6439e3c89b0460e4e38f11a460514551db4d_2_1024x802.png)