{"id":231706,"date":"2021-03-02T09:11:32","date_gmt":"2021-03-02T17:11:32","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=231706"},"modified":"2021-03-11T12:51:13","modified_gmt":"2021-03-11T20:51:13","slug":"vs2019-v16-9-and-v16-10-preview-1","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/vs2019-v16-9-and-v16-10-preview-1\/","title":{"rendered":"Visual Studio 2019 v16.9 and v16.10 Preview 1 are Available Today!"},"content":{"rendered":"

Whenever there is a conference such as Microsoft Ignite<\/a>, there is a tangible excitement throughout our internal teams. We look forward to discovering what new, exciting products, product features, and educational opportunities are available for our customers. Carrying this excitement forward, the Visual Studio team is eager to release Visual Studio 2019 v16.9 and v16.10 Preview 1. We hope you enjoy the new features highlighted from some of teams such as C++, .NET Productivity, Address Sanitizer, XAML Tooling, and IntelliCode teams. \u00a0In addition, Visual Studio 2019 v16.9 is our next long-term servicing release<\/a>.<\/p>\n

While you enjoy some of our virtual conference sessions, feel free to download one of our latest releases<\/a> to give these new features a try.\u00a0 Also, we love to hear your feedback through our improved Developer Community<\/a>. It is the first place our teams look for new ideas or to address any problems you may be experiencing. We look forward to interacting with you through our vibrant online community.<\/p>\n

Install Visual Studio 2019 v16.9<\/a><\/div><\/p>\n

What’s New in Visual Studio 2019 v16.9?<\/h3>\n

Address Sanitizer with C++<\/h4>\n

First up on our announcements is Address Sanitizer support for Windows<\/a> is out of experimental support and now generally available. The highlight change is MSVC can now work out which runtime libraries are needed to use ASan with your project. Consequently, you no longer need to supply them when compiling from the command-line. All you need to do is set\u00a0\/fsanitize=address<\/strong> and our tools will work out the rest of the details.<\/p>\n

Additionally, the IDE integration for ASan-reported exceptions (vcasan.lib<\/strong>) now handles the complete collection of reportable ASan exceptions. If the compiler and linker detect you are building with ASan but not receiving debug information, it will offer the option to emit this information.<\/p>\n

Finally, we have added support for global C variables and\u00a0__declspec(no_sanitize_address)<\/strong>. This makes it possible to opt out of running the Address Sanitizer over specific variables or even entire functions.<\/p>\n

C++ Conformance<\/h4>\n

We have implemented the More Constexpr Containers<\/a> proposals which allows destructors and new expressions to be\u00a0constexpr<\/strong>. We are excited about this as it paves the way for utilities like constexpr std::vector<\/strong> and\u00a0std::string<\/strong>. Included in our implementation in this release are compiler diagnostics for uses which trigger undefined behavior.<\/p>\n

C++ IntelliSense<\/h4>\n

Based on your feedback, we have made many improvements to the stability and functionality of providing imported modules and header units in IntelliSense. We appreciate every report, so please keep them coming! While we were working on stability, we also added extra functionality. As a result, we can highlight\u00a0Go-to-definition<\/strong> on module imports, indexing support for export {…}, and more accurate module reference for those with identical names.<\/p>\n

\"Go-to-definition<\/a>
Go-to-definition on Module Imports in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

As implementation of a top-voted Developer Community suggestion ticket, we added completion for\u00a0make_unique<\/strong>,\u00a0make_shared<\/strong>, and\u00a0emplace_back<\/strong>. These provide text completion based on the specified type parameter.<\/p>\n

Additionally, Visual Studio 2019 can configure IntelliSense in CMake projects based on the value of CMake variables set by toolchain files. This greatly improves IntelliSense for Android and other embedded scenarios. The CMakeSettings.json file is the location to specify your custom IntelliSense options.<\/p>\n

Improved Call Stack Handling of Stack Overflow Scenarios<\/h4>\n

Visual Studio 2019 has a new capability to filter out redundant frames from the call stack when the debugger stops on a Stack Overflow Exception<\/em>. It is now possible to see the base of the stack where an infinite recursion originated. This should make it easier to investigate these types of bugs.<\/p>\n

\"Improved<\/a>
Improved Call Stack Handling in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

 <\/p>\n

New .NET Core Memory Dump Analyzers<\/h4>\n

Deadlocks generally occur when thread A is waiting for thread B to release a lock. Simultaneously, thread B is waiting for thread A to release a lock. This conundrum caused us to add a new Auto Analyzer to inspect the threads in a memory dump to determine if an unresponsive application is due to one of these deadlocks. A blocked finalizer can lead to abnormal memory growth which. This, in turn, can lead to system instability due to out of memory exceptions. Our new Analyzer inspects the .NET Core Finalizer queue to help you identify potential blocking objects in a memory dump.<\/p>\n

\"New<\/a>
New Memory Dump Analyzers in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

To access the Analyzer, open your memory dump in Visual Studio 2019. On the Mini Dump File Summary page, select the\u00a0Run Diagnostics Analysis<\/strong> action.<\/p>\n

IntelliCode: Frictionless Suggestions in the Completions List<\/h4>\n

IntelliCode suggestions<\/a> already helps you find other locations where a repeated edit applies. Comparatively, in Visual Studio 2019 v16.9, you can easily apply suggestions in a more frictionless way and without breaking your editing flow. You can find IntelliCode suggestions right in your IntelliSense completion list. From there, you are also able to find and apply the same change in other locations. This new functionality in the completion list should blend naturally into your editing flow. The edit is added to the completion list in a non-intrusive way. This makes edits easy to find and perform repetitious actions.<\/p>\n

Find out more in the blog post<\/a> from the team who wrote the feature.<\/p>\n

\"IntelliCode:<\/a>
IntelliCode: Frictionless Suggestions in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

<\/h4>\n

.NET Productivity<\/h4>\n

From our .NET team, we bring you several features to help with continual improvements in productivity. First on the list, using directives will now automatically be added when copying and pasting types to a new file. To give this a try, you will need to turn on this option under Tools > Options > Text Editor > C#<\/strong>. You can also access it from\u00a0Basic > Advanced<\/strong> and select\u00a0Add missing using directives on paste<\/strong>.<\/p>\n

\"Using<\/a>
Using Directives Automatically Added in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

<\/h3>\n

We have also added inline type hints that insert adornments for variables with inferred types and lambda parameter types. Like the last feature, you will need to turn this feature on under the menu Tools > Options > Text Editor > C#<\/strong> or again under\u00a0Basic > Advanced > Display inline type hints<\/strong>. This last option is under the Inline Hints section. Hold down Alt+F1<\/strong> to view hints at any time.<\/p>\n

\"Inline<\/a>
Inline Type Hints in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

<\/h3>\n

In addition, there is now IntelliSense completion that automatically inserts a semicolon as a commit character for object creation and method completion.<\/p>\n

\"Automatic<\/a>
Automatic Semicolon Insertion in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

<\/h4>\n

.NET Core Debugging with WSL 2<\/h3>\n

Are you a .NET Core developer who loves working in Windows and Visual Studio, but needs to test your app in Linux? If so, the new .NET Core debugging in WSL 2 feature is something you will want to try out! It enables you to debug your code in WSL 2 using the Linux distro of your choice.<\/p>\n

\".NET<\/a>
.NET Core Debugging with WSL 2 in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

After installing WSL 2<\/a>\u00a0and the\u00a0distribution<\/a> of your choice and opening an ASP.NET Core web app or .NET Core console app in Visual Studio, you\u2019ll see a new Launch Profile named WSL 2<\/strong>.<\/p>\n

\"Adding<\/a>
Adding Launch Profile WSL 2 in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

Selecting this profile will add it to your launchSettings.json. Once the new profile is selected, Visual Studio checks that your WSL 2 distribution is configured to run .NET Core apps, and helps you install any missing dependencies. As soon as all the dependencies are installed, you are ready to debug WSL 2. From here, you can start Debugging as normal, and your app will now be running in your default WSL 2 distribution. Check Environment.OSVersion <\/a>to verify the correct distribution.<\/p>\n

Note: Only Ubuntu and Debian have been tested and are currently supported. Other distributions supported by .NET Core should work but require manually installing the .NET Core Runtime<\/a>\u00a0and\u00a0Curl<\/a>.<\/p>\n

By default, the WSL 2 launch profile will use the default distribution as set in wsl.exe, but you can modify your launch profile to include specific distributions. Adding extra functionality, you can also have multiple launch profiles. For instance, if you need to test your console app on Debian, Ubuntu 18.04, and Ubuntu 20.04, you could modify these settings.<\/p>\n

XAML Tools (WPF, WinUI, UWP & Xamarin.Forms<\/h4>\n

In this release we\u2019ve\u00a0<\/span>made<\/span>\u00a0<\/span>multiple improvements to our XAML toolin<\/span>g, highlight<\/span>s<\/span>\u00a0include<\/span>:<\/span>\u00a0<\/span><\/p>\n

For\u00a0<\/span><\/b>MVVM Tooling<\/span><\/b>\u00a0improvements<\/span><\/b>\u00a0in the XAML code editor w<\/span>e\u2019ve introduced\u00a0<\/span>l<\/span>ightbulbs to<\/span>\u00a0<\/span>set the design\u00a0DataContext\u00a0in XAML to an available\u00a0<\/span>view-model<\/span>. Setting this<\/span>\u00a0enhances IntelliSense<\/span>,<\/span>\u00a0such as the ability to create new\u00a0ViewModel\u00a0properties<\/span>, Go\u00a0To\u00a0Definition and completions<\/span>\u00a0<\/span>right from<\/span>\u00a0the<\/span>\u00a0XAML code<\/span>\u00a0editor<\/span>.\u00a0<\/span>You can even create new\u00a0<\/span>ICommand\u00a0properties\u00a0<\/span>for whichever implementation your solution references.<\/span>\u00a0<\/span><\/p>\n

Xamarin.Forms\u00a0\u201cchanges only\u201d XAML Hot Reload is now GA quality, no longer in preview.\u00a0<\/span><\/b>Apps targeting\u00a0Xamarin.Forms\u00a05.0 or newer will use this new mode by default.\u00a0<\/span>\u00a0<\/span><\/p>\n

The new \u201cchanges only\u201d XAML Hot Reload mechanism makes it possible to update your running app\u2019s UI in real-time and see those changes reflected immediately without requiring the full page to be reloaded, and without having to save the file. \u201cChanges only\u201d Hot Reload also supports the Live Visual Tree, so you can see the runtime UI hierarchy for your app and easily navigate to your XAML source code.\u00a0<\/span>\u00a0<\/span><\/p>\n

\"Live<\/a>
Live Visual Tree in Visual Studio 2019 v16.9<\/figcaption><\/figure><\/p>\n

<\/h4>\n

For those customers who prefer to continue to use the older \u201cfull page\u201d Hot Reload you can still do so even for projects targeting Xamarin.Forms SDK v5 by going to the Hot Reload settings under Tools > Options > Debugging > Hot Reload.<\/p>\n

These are just two of our highlights, for a complete list of<\/span><\/i> XAML tooling<\/span><\/i> improvements please see the release notes.<\/span><\/i><\/p>\n

Ding! Your Test Run is Complete!<\/h4>\n

One of the features we find particularly fun is how Test Explorer can play audio cues after a test run completes. This includes the option for different sounds for test runs with all tests passing and a different for test runs with at least one failing test. You are also able to fully customize these sounds using the Windows 10 sound library or your own audio files. To watch this in action, check out our demo<\/a>.<\/p>\n

Improvements to GitHub Actions Tooling<\/h4>\n

In a previous post, using GitHub Actions in Visual Studio is as easy as right-click and Publish<\/a>, we announced the efforts added to Visual Studio 2019 to extend our Publish experiences. Specifically, we sought to introduce and assist developers to repeatable, predictable continuous integration and deployment (CI\/CD) environments using GitHub Actions. In this release, we bring the following improvements:<\/p>\n