We hear your feedback, and in Visual Studio 2019 version 16.4 Preview 2 we have addressed one of our top Developer Community issues related to CMake development in Visual Studio by revamping the selection of CMake launch targets. We have also added Overview Pages for CMake to help you get started with CMake and cross-platform development. If you’re not familiar with Visual Studio’s CMake support, be sure to check our CMake Support in Visual Studio introductory page.
Launch Target Selection
In Visual Studio 2019 you can select a CMake target to run via the launch drop-down menu:
With Visual Studio 2019 version 16.4 we have improved this experience based on your feedback. You can now select “Show/Hide Debug Targets” from the top of the drop-down menu to open the following dialog and hide seldom used debug targets from the drop-down menu:
For large CMake projects (like llvm), this will allow you to clean-up the launch drop-down menu dramatically and focus only on the targets you care about. You can always unhide any debug target that has been hidden from the drop-down menu. In the following example, many of the 100+ targets of llvm (listed above) have been hidden from the launch drop-down menu:
The launch drop-down menu also displays your most recently used debug targets at the top of the menu. This is based on feedback that many of you toggle between 2-3 debug targets at a time. In the screenshot above, “Fibonacci.exe” and “bugpoint.exe” are my most recently used debug targets.
Overview Pages for CMake
We also added Overview Pages for CMake projects to help you get started with cross-platform development. These pages are dynamic and help you install the Linux Workload, connect to a remote Linux system or the Windows Subsystem for Linux (WSL), and add a Linux or WSL configuration to your CMake project. If you are just getting started with Linux development in Visual Studio, I recommend trying our native support for WSL.
Give us your feedback!
Do you have feedback on our Linux tooling or CMake support in Visual Studio? We’d love to hear from you to help us prioritize and build the right features for you. We can be reached via the comments below, email (visualcpp@microsoft.com), and Twitter (@VisualC).