Visual Studio 2019 Update Boosts Debugging, C++, More -- Visual Studio Magazine

Visual Studio 2019 Update Boosts Debugging, C++, More

By David Ramel
04/26/2019

Microsoft released Visual Studio 2019 version 16.1 Preview 2, with improvements to debugging, C++ development, extensibility, NuGet functionality and more.

C++ developers get several enhancements, including:

The Tools menu can now be used to enable C++ IntelliCode, which is now included out-of-the box and features improved accuracy and support for free-functions.
CMake integration now supports the Clang/LLVM toolchain for Windows or Linux projects. Developers can now build, edit and debug CMake projects that use Clang, MSVC or GCC.
In-editor documentation for CMake commands, variables, and properties has been added, and developers can now enjoy IntelliSense autocompletion and quick info tooltips when editing a CMakeLists.txt file. Microsoft said that will save developers time spent referencing documentation outside of the IDE and reduce errors.

Other improvements include:

Any workload that includes C#, XAML or C++ will see IntelliCode installed by default, with it being enabled by default for C# and XAML.
Debugging NuGet packages is easier with the ability to enable NuGet.org Symbol Server from the Debugging\Symbols option. Other debugging-related features include: the Time Travel Debugging preview now includes support for exception stepping; support has been added for Linux remote debugging using a custom program via launch.vs.json.
Source Link can now leverage Windows Authentication to support on-premises TFS Source Control.
Extensibility is enhanced with the ability to use the latest version of the Microsoft.VisualStudio.SDK to target Visual Studio 2019 in and extension. Also, creating new VSIX projects will leverage the 16.0 version of the Microsoft.VisualStudio.SDK NuGet package, and coders can now add tags to project templates to enable categorization and filtering in the Visual Studio 2019 New Project Dialog.
Upon focus, Visual Studio Search will now display the three most recently used actions invoked, functionality added in response to developer feedback.
Mobile developers using Xamarin will see an updated default Android Experience to API 28 for templates, device creation, installers and more. IntelliSense on Windows will show recommendations for design-time attributes when developers code Xamarin.Forms XAML.
Developers can use one-click code cleanup for projects and solutions by right-clicking on projects or the solution in the Solution Explorer and selecting "Run Code Cleanup."

More details on all of the above and dozens of other new features, tweaks and bug fixes and be found in an announcement blog post and the v16.1 Preview 2 release notes.

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.