{"id":228535,"date":"2020-03-16T10:30:19","date_gmt":"2020-03-16T17:30:19","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=228535"},"modified":"2020-03-17T12:29:49","modified_gmt":"2020-03-17T19:29:49","slug":"visual-studio-2019-version-16-5","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/visual-studio-2019-version-16-5\/","title":{"rendered":"Visual Studio 2019 version 16.5 is now available"},"content":{"rendered":"

The Visual Studio 2019 team here in Redmond has been living under a perpetually grey, wet winter sky since our last minor release. Thankfully, we are beginning to see the sun making regular appearances.\u00a0 It is our hope this newest release will also brighten your day. Visual Studio 2019 version 16.5 contains anticipated new features from XAML, .NET, C++ and Debugging.\u00a0 In addition, we have addressed several issues found in our Preview releases. We believe this combination is ready to make your developer journey more productive. If you have any additional ideas to contribute to our product, we invite you to participate in our Developer Community<\/a> forum.<\/p>\n

While I elaborate, why not download our latest version to try for yourself? Also keep in mind, a more complete list of all changes are available in the Visual Studio 2019 release notes<\/a>.<\/p>\n

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

.NET Mobile Development<\/h3>\n

Our first feature to discuss is XAML Hot Reload for Xamarin.Forms<\/a>. This feature speeds up your development and makes it easier to build, experiment, and iterate over your mobile app’s user interface. How? You do not need to rebuild your app each time you tweak your UI as changes instantly show while the app is running! Because this updates as you make changes, if you have interacted with the application, the state of the application is not lost as you make the changes.\u00a0 Consequently, you do not have to recreate the repo as you previously did. That’s pretty exciting, isn’t it?<\/p>\n

We heard lots of feedback on a specific need shared via Developer Community Suggestions<\/a>.\u00a0 Due to the fact, you wanted to see changes made to your XAML reload instantaneously on multiple targets such as an iOS simulator and Android emulator, so we have added that capability.<\/p>\n

\u00a0.NET Productivity<\/h3>\n

To help with .NET Productivity several features ship in this Visual Studio 2019 version 16.5 release.<\/p>\n

First of all, you can convert if<\/em> statements to switch<\/em> statements or switch expressions. To do this, place your cursor on the if keyword. Press Ctrl<\/strong>+.<\/strong> to trigger the Quick Actions and Refactorings<\/strong> menu. Finally, select Convert to ‘switch’ statement<\/strong> or Convert to ‘switch’ expression<\/strong>.<\/p>\n

\"Image
Convert if to switch statement in Visual Studio 2019.<\/figcaption><\/figure><\/p>\n
IntelliSense<\/h5>\n

Furthermore, IntelliSense now supports completion for unimported extension methods. To access this ability, you will need to enable this option in Tools<\/strong> > Options<\/strong> > Text Editor<\/strong> > C#<\/strong> > Intellisense<\/strong> > and select Show items from unimported namespaces(experimental)<\/strong>.<\/p>\n

Simplify Interpolation<\/h5>\n

Additionally, we added the ability to <\/span>simplify string interpolation<\/span> refactoring. This will help make your <\/span>string interpolation<\/span> more legible and concise. Place your cursor on the string interpolation. Press <\/span>Ctrl+.<\/span><\/b> to trigger the <\/span>Quick Actions and Refactorings<\/span><\/b> menu and select <\/span>Simplify interpolation<\/span><\/b>.<\/span>\u00a0<\/span><\/p>\n

\"Simplify
You can Simplify Interpolation through the Quick Actions and Refactorings menu.<\/figcaption><\/figure><\/p>\n

 <\/p>\n

The<\/span> Extract local function<\/span> refactoring allows you to turn a fragment of code from an existing method into a local function. Highlight the code you want extracted. Press <\/span>Ctrl+. <\/span><\/b>to trigger the <\/span>Quick Actions and Refactorings<\/span><\/b> menu and select <\/span>Extract local function<\/span><\/b>.<\/span>\u00a0<\/span><\/p>\n

\"Extract
You can Extract Local Function through the Quick Actions and Refactorings menu<\/figcaption><\/figure><\/p>\n

The<\/span> make members static<\/span> code fix helps improve readability by making a non-static member static. Place your cursor on the member name. Press <\/span>Ctrl+.<\/span><\/b> to trigger the <\/span>Quick Actions and <\/span><\/b>Refactorings<\/span><\/b> menu and select <\/span>Make static<\/span><\/b>.<\/span>\u00a0<\/span><\/p>\n

\"Make
You can make a member static through the Quick Actions and Refactorings menu.<\/figcaption><\/figure><\/p>\n

Testing<\/h4>\n

Profiling is an excellent tool for identifying performance <\/span><\/span>i<\/span><\/span>ssues <\/span><\/span>in your code. <\/span><\/span>You can now profile a .NET Core test. To do so your .NET Core projects must be configured to generate full PDB<\/a>\u2019s. We also recommend upgrading to a minimum version of 16.4 for the Microsoft.Test.SDK. This will enable you to profile tests in both x86 and x64 architecture settings. To profile a test, select Profile<\/strong> from the context menu in the Test Explorer. Test profiling is supported through static instrumentation and Performance Explorer<\/a> (.vsp) document in Visual Studio.<\/p>\n

Debugging in C++ and .NET<\/h4>\n

Pinnable Properties <\/span><\/b>has been <\/span>a <\/span>popular <\/span>tool <\/span>for managed code<\/span> debugging. Specifically, this allows<\/span> quick visibility of an object\u2019s property without the need of drilling into an object. This <\/span>feature<\/span> is now <\/span>available in C++ for DataTips and the Autos, Locals, and Watch windows.\u00a0 To use the tool, hover over a property and select the toggle-able pin icon that appears or select the <\/span>Pin Member as Favorite<\/span><\/b> option in the context menu, bubbling your selected property to the top of your debugger display.<\/span>\u00a0<\/span><\/p>\n

\"Pinnable
Pinnable Properties tool in Debugger<\/figcaption><\/figure><\/p>\n

We\u2019ve also added a new capability to assist you in debugging multithreaded applications.\u00a0 <\/span>This helps<\/span> avoid struggling to <\/span>determine the source of a deadlock or other <\/span>thread-related bugs. Subsequently,<\/span> you can now view which managed thread is holding a .NET object lock in the <\/span>Call Stack window, Parallel Stacks window<\/span><\/b> and the location column of the <\/span>Threads window<\/span><\/b>.<\/span>\u00a0<\/span><\/p>\n

\"Call
.NET Object lock in the Call Stack window, Parallel Stacks window<\/figcaption><\/figure><\/p>\n

In a previous update, we made it possible to debug processes running in <\/span>Docker Linux containers. <\/span><\/b>Now, <\/span>you can <\/span>do the same in Docker Windows containers.<\/b> To give this at try, attach and debug that<\/span> .NET Framework, .NET Core, and C++<\/span> process in the <\/span>Attach to Process <\/span><\/b>window by selecting the <\/span>Docker (Windows Container) <\/span><\/b>connection type<\/span>.<\/span><\/b>\u00a0\u00a0<\/span><\/b>\u00a0<\/span><\/p>\n

\"Docker
Docker Window Container Process<\/figcaption><\/figure><\/p>\n

Finally,<\/span> for developers building applications on top of the <\/span>Open Enclave SDK<\/span><\/a> we\u2019ve added debugging support in Visual Studio 2019 version 16.5. So, you can<\/span> now debug those<\/span> applications <\/span>from within<\/span> the product<\/span>, f<\/span>or more info<\/span>rmation<\/span>, go to <\/span>aka.ms\/OpenEnclaveVisualStudio<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

\"Image<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

.NET Object Allocation Tool<\/h4>\n

The <\/span>.<\/span>NET Object Allocation tool has been updated with changes aimed to help you visualize your data more easily and reduce the time you spend on memory investigations.\u00a0<\/span>\u00a0<\/span><\/p>\n

First, the backtrace view has been moved to a separate panel to enable you to more easily distinguish between the allocation type and the functions within the type being called. Additionally, when an allocation type is selected the call tree is oriented from the leaf to root node to more quickly see what specific function is allocating the most memory and needs to be changed. Lastly, a new average size column has been added both to the allocation type panel and backtrace view. This information is helpful if you are trying to investigate what allocation types or functions are taking up a lot of memory per allocation. Furthermore, all of these columns are sortable and can be toggled on or off so that you can customize the tables to look the way you want.<\/span>\u00a0<\/span><\/p>\n

Also, take notice of the new icons added to the allocation, call tree, and functions view, so it is easier to visualize the classes and structures being allocated. The two icons represent value types (blue) and reference types (yellow). By the way, a number of other user experiences such as more icons and performance improvements are coming soon to Visual Studio<\/span>!<\/span>\u00a0<\/span><\/p>\n

\".NET
.NET Object Allocation Tool<\/figcaption><\/figure><\/p>\n

 <\/p>\n

C++ Improvements in Visual Studio 2019 version 16.5<\/h3>\n

Visual Studio 2019 version 16.5 brings several improvements to the C++ cross-platform and CMake development experience<\/span>. Starting with this release, y<\/span>ou\u2019re now able to interact with your stored rem<\/span>ote connections over the command line. This is useful for tasks such as provisioning new development machines or setting up Visual Studio in continuous integration.<\/span>\u00a0<\/span><\/p>\n

\"Interact
Interact with stored remove connections through the Developer Command Prompt<\/figcaption><\/figure><\/p>\n

In addition, this release brings the ability to leverage native support for <\/span>Windows Subsystem for Linux<\/span><\/a> when separating your <\/span>build system from a remote deploy m<\/span>achine<\/span>, allowing you to build natively on WSL and to deploy the build artifacts to a second remote <\/span>machine<\/span> for debugging. This workflow is supported by both CMake projects and <\/span>MSBuild<\/span>-based Linux projects.<\/span>\u00a0<\/span><\/p>\n

Visual Studio version 16.5 makes it easier than ever <\/span>to <\/span>work <\/span>with<\/span> CMake projects in Visual Studio. Specifically, t<\/span>his release brings <\/span>the ability to <\/span>add, remove, and rename source files and targets in your CMake projects from the IDE without manually editing your CMake scripts.<\/span> When<\/span> add<\/span>ing and <\/span>remov<\/span>ing<\/span> files with the Solution Explorer, Visual Studio will automatically edit your CMake project. Furthermore, you can also add, remove, and rename the project\u2019s targets from the Solution Explorer\u2019s <\/span>Targets View, as shown below.<\/span> You can learn more <\/span>about this and r<\/span>elated features <\/span>at the <\/span>C++ Team Blog<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

\"Add,
Add, remove, and rename source files in CMake projects<\/figcaption><\/figure><\/p>\n

New CMake code navigation features such as Go <\/span>To<\/span> Definition and Find All References make it easier to explore and understand complex CMake projects. The navigation feature supports variables, functions, and targets in CMake script files.<\/span> They work across your entire CMake project to offer more productivity than na\u00efve text search across files and folders. Also, they are integrated with other IDE productivity features such<\/span> as <\/span>Peek Definition<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

Download Visual Studio 2019 version 16.5 Today!<\/span><\/h3>\n

As you can see, Visual Studio 2019 version 16.5 gives plenty of new functionality to help you with your development projects. Give it a try today and tell us what you think.<\/p>\n

Additionally, if you would like to try out future features, check out our Preview channel to give our next product iteration a try. This Preview release brings additional changes to WFT\/UWP Tooling, JavaScript\/TypeScript, and Web Tooling. The version 16.6 Preview 1 release notes<\/a> give full details about each of these features.<\/p>\n

As always, we look forward to your feedback!<\/p>\n

Try v16.6 Preview 1<\/a><\/div><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Visual Studio 2019 version 16.5 and 16.6 Preview 1 are available today. Included in this release are updates in .NET Productivity, .NET Mobile development, C++, and debugging.<\/p>\n","protected":false},"author":4513,"featured_media":228543,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1028,155],"tags":[237,354,5,9,467,526,12,475,353],"class_list":["post-228535","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mobile","category-visual-studio","tag-net","tag-announcement","tag-csharp","tag-debug","tag-intellicode","tag-productivity","tag-visual-studio","tag-visual-studio-2019","tag-xamarin"],"acf":[],"blog_post_summary":"

Visual Studio 2019 version 16.5 and 16.6 Preview 1 are available today. Included in this release are updates in .NET Productivity, .NET Mobile development, C++, and debugging.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/228535","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/4513"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=228535"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/228535\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/228543"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=228535"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=228535"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=228535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}