Visual Studio Icon Visual Studio 2019 version 16.4 Release Notes


Developer Community | System Requirements | Compatibility | Distributable Code | License Terms | Blogs | Latest Release Known Issues


Click a button to download the latest version of Visual Studio 2019. For instructions on installing and updating Visual Studio 2019, see the Update Visual Studio 2019 to the most recent release. Also, see instructions on how to install offline.

Community Download Button Professional Download Button Enterprise Download Button


What's New in Visual Studio 2019 version 16.4

Support Timeframe

Visual Studio 2019 version 16.4 is the second supported servicing baseline for Visual Studio 2019. Enterprise and Professional customers needing to adopt a long term stable and secure development environment are encouraged to standardize on this version.  As explained in more detail in our lifecycle and support policy, version 16.4 will be supported with fixes and security updates for one year after the release of the next servicing baseline.

In addition, now that version 16.4 is available, version 16.0, which was the last servicing baseline, will be supported for an additional 12 months and will go out of support in January 2021. Note as well that versions 16.1, 16.2, and 16.3 are no longer under support. These intermediary releases received servicing fixes only until the next minor update released.

You can acquire the latest most secure version of Visual Studio 2019 version 16.4 in the downloads section of my.visualstudio.com.  For more information about Visual Studio supported baselines, please review the support policy for Visual Studio 2019.

Visual Studio 2019 version 16.4 Releases

Archived Release Notes

Visual Studio 2019 Blog

The Visual Studio 2019 Blog is the official source of product insight from the Visual Studio Engineering Team. You can find in-depth information about the Visual Studio 2019 releases in the following posts:

Join the Release Note Discussion


Release Notes Icon Visual Studio 2019 version 16.4.13 New release icon

released September 8, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.13

Security Advisory Notice

CVE-2020-1130 Diagnostics Hub Standard Collector Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector improperly handles data operations. An attacker who successfully exploited this vulnerability could run processes in an elevated context.

CVE-2020-1133 Diagnostics Hub Standard Collector Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector improperly handles file operations. An attacker who successfully exploited this vulnerability could run processes in an elevated context.

CVE-2020-16856 Visual Studio Remote Code Execution Vulnerability

A remote code execution vulnerability exists in Visual Studio when it improperly handles objects in memory. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user.

CVE-2020-16874 Visual Studio Remote Code Execution Vulnerability

A remote code execution vulnerability exists in Visual Studio when it improperly handles objects in memory. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user.

CVE-2020-1045 Microsoft ASP.NET Core Security Feature Bypass Vulnerability

A security feature bypass vulnerability exists in the way Microsoft ASP.NET Core parses encoded cookie names. The ASP.NET Core cookie parser decodes entire cookie strings which could allow a malicious attacker to set a second cookie with the name being percent encoded.

Additional Fixes in 16.4.13

  • Fixed an issue that would sometimes cause Visual Studio or MSBuild to stop responding after cancelling a C++ build.
  • Out of support versions of .NET Core will no longer be reinstalled during a repair or upgrade if they were removed outside of Visual Studio setup.

Release Notes Icon Visual Studio 2019 version 16.4.12

released August 11, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.12

Security Advisory Notice

CVE-2020-1597

A denial of service vulnerability exists when ASP.NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication.


Release Notes Icon Visual Studio 2019 version 16.4.11

released July 14, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.11

Security Advisory Notice

CVE-2020-1393 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Windows Diagnostics Hub Standard Collector Service fails to properly sanitize input, leading to an unsecure library-loading behavior.

CVE-2020-1416 Visual Studio Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists in Visual Studio when it loads software dependencies.

CVE-2020-1147 .NET Core Denial of Service Vulnerability

A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to an ASP.NET Core application, or other application that parses certain types of XML. The security update addresses the vulnerability by restricting the types that are allowed to be present in the XML payload.


Release Notes Icon Visual Studio 2019 version 16.4.10

released June 09, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.10

  • Fixed a bug where there wrong values could be restored after setjmp.

Security Advisory Notice

CVE-2020-1108 / CVE-2020-1108.NET Core Denial of Service Vulnerability

To comprehensively address CVE-2020-1108, Microsoft has released updates for .NET Core 2.1 and .NET Core 3.1. Customers who use any of these versions of .NET Core should install the latest version of .NET Core. See the Release Notes for the latest version numbers and instructions for updating .NET Core.

CVE-2020-1202 / CVE-2020-1203 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector or the Visual Studio Standard Collector fails to properly handle objects in memory.

CVE-2020-1293 / CVE-2020-1278 / CVE-2020-1257 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly handles file operations.


Release Notes Icon Visual Studio 2019 version 16.4.9

released May 27, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.9

  • This fixes a caching bug in an analysis used by an optimization, the effect being we remove instructions erroneously marked as unneeded. The fix is to detect cases where we would have otherwise stored stale data to the cache. It is difficult to entirely characterize when this manifests, but in the report it was a modulo operator on an index in a loop. For the future, we've added the (unsupported) /d2ssa-bit-estimator- flag to turn off the particular optimization entirely. This flag was added with the fix, and is not present in prior versions.
  • Added support to mitigate the performance impact caused by the Intel Jump Conditional Code (JCC) erratum microcode update in certain Intel processors.
  • False C6244 warnings and crash in cl.exe during code analysis caused by lambda local variables has been fixed.
  • ICE in PREfast 16.5 running against Office code

Release Notes Icon Visual Studio 2019 version 16.4.8

released May 12, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.8

  • Add a change that enables Enterprise IT administrators and deployment engineers to configure tools like Microsoft Update client & SCCM to determine applicability of VS2019 16.4 updates hosted on Microsoft Update Catalog & WSUS.

Security Advisory Notice

CVE-2020-1108 .NET Core Denial of Service Vulnerability

A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the .NET Core application. The security update addresses the vulnerability by correcting how the .NET Core web application handles web requests.

CVE-2020-1161 .NET Core Denial of Service Vulnerability

A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the ASP.NET Core application. The security update addresses the vulnerability by correcting how the ASP.NET Core web application handles web requests.


Release Notes Icon Visual Studio 2019 version 16.4.7

released April 14, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.7

Security Advisory Notice

CVE-2020-0899 Microsoft Visual Studio Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when Microsoft Visual Studio updater service improperly handles file permissions. An attacker who successfully exploited this vulnerability could overwrite arbitrary file content in the security context of the local system.

CVE-2020-0900 Visual Studio Extension Installer Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Visual Studio Extension Installer Service improperly handles file operations. An attacker who successfully exploited the vulnerability could delete files in arbitrary locations with elevated permissions.

CVE-2020-5260 Git for Visual Studio Credential Leak Vulnerability due to insufficient validation on URLs

A credential leak vulnerability exists when specially crafted URLs are parsed and sent to credential helpers. This can lead to credentials being sent to the wrong host.


Release Notes Icon Visual Studio 2019 version 16.4.6

released March 10, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.6

Security Advisory Notice

CVE-2020-0793 & CVE-2020-0810 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector improperly handles file operations, or the Windows Diagnostics Hub Standard Collector Service fails to properly sanitize input.

CVE-2020-0884 Spoofing vulnerability when creating Outlook Web -Add-in

A spoofing vulnerability exists when creating an Outlook Web-Addin if multi-factor authentication is enabled, as it includes a reply URL that is not secured by SSL. An attacker who successfully exploited this vulnerability could compromise the access tokens, exposing security and privacy risks.

CVE-2020-0789 Visual Studio Extension Installer Service Denial of Service Vulnerability

A denial of service vulnerability exists when the Visual Studio Extension Installer Service improperly handles hard links. An attacker who successfully exploited the vulnerability could cause a target system to stop responding.


Release Notes Icon Visual Studio 2019 version 16.4.5

released February 11, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.5


Release Notes Icon Visual Studio 2019 version 16.4.4

released January 30, 2020

Top Issues Fixed in Visual Studio 2019 version 16.4.4


Release Notes Icon Visual Studio 2019 version 16.4.3

released January 14, 2020

Security Advisory Notice

CVE-2020-0602 ASP.NET Core Denial of Service Vulnerability

A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the ASP.NET Core application. The security update addresses the vulnerability by correcting how the ASP.NET Core web application handles web requests.

CVE-2020-0603 ASP.NET Core Remote Code Execution Vulnerability

A remote unauthenticated attacker could exploit this vulnerability by issuing specially crafted requests to the ASP.NET Core application. The security update addresses the vulnerability by correcting how the ASP.NET Core web application handles in memory.

CVE-2020-0605 .NET Core Remote Code Execution Vulnerability

Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of .NET Core. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file.The security update addresses the vulnerability by correcting how .NET Core checks the source markup of a file.

CVE-2020-0606 .NET Core Remote Code Execution Vulnerability

Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of .NET Core. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file.The security update addresses the vulnerability by correcting how .NET Core checks the source markup of a file.

Top Issues Fixed in Visual Studio 2019 version 16.4.3


Release Notes Icon Visual Studio 2019 version 16.4.2

released December 17, 2019

Top Issues Fixed in Visual Studio 2019 version 16.4.2


Release Notes Icon Visual Studio 2019 version 16.4.1

released December 10, 2019

Top Issues Fixed in Visual Studio 2019 version 16.4.1

Security Advisory Notice

CVE-2019-1349 Git for Visual Studio Remote Excecution Vulnerability due to too lax restrictions on submodule names

A remote code execution vulnerability exists when Git runs into collisions of submodule names for directories of sibling submodules. An attacker who successfully exploited this vulnerability could remote execute code on the target machine. The security update addresses the vulnerability by taking a new version of Git for Windows which requires the directory for the submodules’ clone to be empty.

CVE-2019-1350 Git for Visual Studio Remote Excecution Vulnerability due to incorrect quoting of command-line arguments

A remote code execution vulnerability exists when Git interprets command-line arguments with certain quoting during a recursive clone in conjunction with SSH URLs. An attacker who successfully exploited this vulnerability could remote execute code on the target machine. The security update addresses the vulnerability by taking a new version of Git for Windows which fixes the issue.

CVE-2019-1351 Git for Visual Studio Arbitrary File Overwrite Vulnerability due to usage of non-letter drive names during clone

An arbitrary file overwrite vulnerability exists in Git when non-letter drive names bypass safety checks in git clone. An attacker who successfully exploited this vulnerability could write to arbitrary files on the target machine. The security update addresses the vulnerability by taking a new version of Git for Windows which fixes the issue.

CVE-2019-1352 Git for Visual Studio Remote Excecution Vulnerability due to unawareness of NTFS Alternate Data Streams

A remote code execution vulnerability exists in Git when cloning and writing to .git/ directory via NTFS alternate data streams. An attacker who successfully exploited this vulnerability could remote execute code on the target machine. The security update addresses the vulnerability by taking a new version of Git for Windows which has been made aware of NTFS alternate data streams.

CVE-2019-1354 Git for Visual Studio Arbitrary File Overwrite Vulnerability due to not refusing to write out tracked files containing backslashes

An arbitrary file overwrite vulnerability exists in Git when tree entries with backslashes and malicious symlinks could break out of the work tree. An attacker who successfully exploited this vulnerability could write to arbitrary files on the target machine. The security update addresses the vulnerability by taking a new version of Git for Windows which does not allow this usage of backslashes.

CVE-2019-1387 Git for Visual Studio Remote Execution Vulnerability due to too lax validation of submodule names in recursive clones

A remote code execution vulnerability exists in Git when cloning recursively with submodules. An attacker who successfully exploited this vulnerability could remote execute code on the target machine. The security update addresses the vulnerability by taking a new version of Git for Windows which tightens validation of submodule names.

CVE-2019-1486 Live Share extension URL redirection vulnerability

A spoofing vulnerability was detected in the Visual Studio Live Share extension, when a guest connected to a Live Share session was redirected to an arbitrary URL specified by the session host. An attacker would have been able to successfully exploit this vulnerability and cause the guest's computer to open a browser and navigate to a malicious URL without explicit consent. This was part of the "Shared Server" feature of Live Share that allowed auto-port forwarding during an active Live Share session. The latest update addresses this vulnerability by prompting the Live Share guest for consent prior to browsing the host-specified URL.


Release Notes Icon Visual Studio 2019 version 16.4

released December 3, 2019

Summary of What's New in Visual Studio 2019 version 16.4

  • Visual Studio now supports “FIPS compliance mode”
  • XAML Designer zoom/position now defaults to Fit All.
  • Create Data Binding Dialog has been added.
  • Improvements to regions IntelliSense
  • Snippets in XAML IntelliSense
  • Pop-up XAML editor as a separate window from designer
  • Displaying resources for referenced assemblies
  • Just My XAML in Live Visual Tree
  • Merge Resource Dictionary
  • XAML Islands support
  • Edit Template now works with controsl from 3rd party controls.
  • Clang-Tidy support in C++ MSBuild and CMake projects, for both Clang and MSVC.
  • AddressSanitizer support for projects compiled with MSVC on Windows.
  • Support for publishing local Git repositories to GitHub.
  • Change your document tabs to a vertical layout with Vertical Document Tabs.
  • .NET Productivity additions in this release include the ability to configure the severity level of a code style rule directly in the error list, Find All References now has the option to group by type and member, and a refactoring to make a local function static and pass in variables defined outside of the function to the function's declaration and calls.
  • Quickly customize how objects are displayed in debugger windows using the new Pinnable Properties feature.
  • Containers tool window adds the ability to inspect, stop, start, and remove Docker containers and images
  • Option to improve startup peformance by auto hiding tool windows
  • Automatic detection of SQL Server and Azure Storage connections strings when managing publish dependencies or using Connected Services
  • Added support for developing Azure Functions using the 64bit runtime.
  • Added support for .NET Core 3.0 app publishing options: Ready to Run (Crossgen), Linking, and SingleExe
  • .NET Productivity additions in this release include the ability to configure the severity level of a code style rule directly through the editor, navigate easily up the inheritance chain with the new Go To Base command, adding null checks for all parameters, and XML documentation for overriding methods.
  • XAML Hot Reload for Xamarin.Forms
  • Android App Bundle Publishing
  • AndroidX Migration Wizard
  • Android Layout Linting

Details of What's new in Visual Studio 2019 version 16.4

Visual Studio now supports “FIPS compliance mode”

Starting with version 16.4, Visual Studio 2019 now supports “FIPS 140-2 compliance mode” when developing apps and solutions for Windows, Azure, and .NET. When you’re developing apps or solutions for non-Microsoft platforms like Linux, iOS, or Android, these platforms may not use FIPS 140-2 approved algorithms. Third-party software included with Visual Studio or extensions that you install also may not use FIPS 140-2 approved algorithms. In addition, development for SharePoint solutions does not support FIPS 140-2 compliance mode.

To configure FIPS 140-2 compliance mode for Visual Studio, install .NET Framework 4.8 and enable the Windows group policy setting: “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.”

WPF/UWP Tooling

Customers building WPF/UWP applications will see the following improvements in Visual Studio XAML tooling:

Designer

  • XAML Designer zoom/position now defaults to Fit All: Based on customer feedback we’ve reevaluated the default XAML Designer zoom behavior that occurs when you open a XAML window/page/control/etc. The previous experienced stored the zoom level and position for each file across Visual Studio sessions which caused confusion when customers were coming back to a file after some time had passed. Starting with this release we will only store the zoom level and position for the duration of the active session and go back to a “fit all” default once Visual Studio is restarted.
  • Create Data Binding Dialog: Visual Studio has had a data binding dialog available to WPF .NET Framework developers from the right-click of the XAML Designer and Property Explorer, and this dialog was also previously available to UWP developers. In this release we’re bringing back this experience to UWP developers and adding support for WPF .NET Core applications. This feature is still in development and will continue to improve in the future to bring back feature parity with .NET Framework dialog capabilities.

XAML Editor

  • Improvements to #regions IntelliSense: Starting with Visual Studio 2015 #region support has been available for WPF and UWP XAML developers and more recently for Xamarin.Forms. In this release we’ve fixed an IntelliSense bug, with this fix #regions will now show properly as you begin to type <!.
  • Snippets in XAML IntelliSense: IntelliSense has been enhanced to support showing XAML snippets, this will work for both built-in snippets and any custom snippets that you add manually. Starting with this release we’re also including some out-of-the-box XAML snippets: #region, Column definition, Row definition, Setter and Tag.
  • Pop up XAML editor as a separate window from designer: It is now possible to easily split the XAML Designer and its underlying XAML editor into separate windows using the new Pop up XAML button next to the XAML tab. When clicked the XAML designer will minimize its attached XAML tab and pop open a new window for just the XAML editor view. You can move this new window to any display or tab group in Visual Studio. Note that it is still possible to expand the original XAML view but regardless all XAML views of the same file will stay synchronized in real-time.
Pop up XAML code window
Pop up XAML code window
  • Displaying resources for referenced assemblies: XAML IntelliSense has been updated to support displaying XAML resources from a referenced assembly (when source is not available) for WPF Framework and WPF .NET Core projects.

XAML Debugging Tools

  • Just My XAML in Live Visual Tree: The Live Visual Tree is a feature that is available to both UWP and WPF developers when they run their application in debug mode and is part of the live editing tooling related to XAML Hot Reload. Previously the feature would display the full live visual tree of the attached running application with no filter possible to see just the XAML you’ve written in your app. This made for a very noisy experience and based on customer feedback we’ve added a new default called “Just My XAML” which will limit the tree to just controls you wrote in your application. While this is the new default it is still possible to go back to the previous behavior through either the button within tine Live Visual Tree itself or through a new setting (found under: Options > Debugging > General > Enable Just My XAML)
Show Just My XAML in Live Visual Tree
Show Just My XAML in Live Visual Tree

Resources & Templates

  • Merge Resource Dictionary: It is now possible to easily merge an existing resource dictionary within your UWP/WPF project with any valid XAML file using the new feature available through the solution explorer. Simply open the XAML file in which you want to add the merge statement, then find the file you wish to merge in and right-click on it in solution explorer. In the context menu select the option “Merge Resource Dictionary Into Active Window”, which will add the right merge XAML with path.
Merge Resource Dictionary
Merge Resource Dictionary
  • Edit Template now works with controls from 3rd party controls: It is now possible to create a copy of a controls template even when it’s not part of your solution as source code. With this change the “Edit Template” feature will now be available and work as it does for 1st party elements where the source is available today. Note that this feature is applicable to both 3rd party control libraries and 1st party where source isn’t available.

XAML Islands:

  • Improved XAML Island support: We’ve added support for XAML Islands scenario for Windows Forms and WPF .NET Core 3 apps making it easier to add UWP XAML control into these applications. With these improvements a .NET Core 3 project can a reference to UWP project that contains custom UWP XAML controls. Those custom controls can be used by the WindowsXamlHost controls shipped within the Windows Community Toolkit v6 (Microsoft.Toolkit.Wpf.UI.XamlHost v6.0). You can also use the Windows Application Packaging project to generates MSIX for you .NET Core 3 with Islands. To learn how to get started visit our documentation.

C++

  • Code Analysis now natively supports Clang-Tidy for both MSBuild and CMake projects, whether you're using a Clang or MSVC toolset. clang-tidy checks can run as part of background code analysis, appear as in-editor warnings (squiggles), and display in the Error List.
Clang-Tidy warnings in the Error List
Clang-Tidy warnings in the Error List
  • Visual Studio CMake projects now have Overview Pages to help you get started with cross-platform development. These pages are dynamic and help you connect to a Linux system and add a Linux or WSL configuration to your CMake project.
CMake Overview Pages
CMake Overview Pages
  • The launch drop-down menu for CMake projects now displays your most recently used targets and can be filtered.
  • C++/CLI now supports interop with .NET Core 3.1 and higher on Windows.
  • You can now enable ASan for projects compiled with MSVC on Windows for runtime instrumentation of C++ code that helps with detection of memory errors.
  • Updates to MSVC's C++ Standard Library:
    • C++17: Implemented to_chars() general precision, completing P0067R5 Elementary String Conversions (charconv). This completes implementation of all library features in the C++17 Standard.
    • C++20: Implemented P1754R1 Rename concepts to standard_case. To include preview features from the Latest C++ Working Draft, use the compiler flag /std:c++latest; the flag can also be set in the C/C++ > Language project property page via the C++ Language Standard property.
  • A new collection of tools named C++ Build Insights is now available. See the C++ Team Blog for more information.

Publish to GitHub Support

  • The publish to GitHub feature that was a part of the GitHub Extension for Visual Studio is now included in Visual Studio’s GitHub Essentials.
  • You can now publish local Git repositories to GitHub using the Publish to GitHub button on Team Explorer Synchronization page.

Vertical Document Tabs in Visual Studio

Manage your document tabs in a vertical list on either the left or right side of your editor.

Manage your document tabs in a vertical list on either the left or right side of your editor
Vertical Document Tabs in Visual Studio

Pinnable Properties Debugging Tool

You can now quickly identify and inspect objects at debug-time by pinning properties to the top of DataTips or the Watch, Autos, and Locals windows using the Pinnable Properties feature.

Identify and inspect objects by pinning properties using the Pinnable Properties feature
Pinnable Properties in Visual Studio

Containers tool window

  • You can list, inspect, stop, start, and remove containers
  • You can view logs and file contents for running containers, as well as open a terminal window into the containers
  • You can view, inspect, and remove images
You can list, inspect, stop, start, and remove containers through the containers tool window.
Containers tool window in Visual Studio

Autohide tool windows

Enabling this preview feature option allows you to skip startup delays introduced by launching Visual Studio with multiple tool windows opened.

.NET Productivity

  • You can now configure the severity level of a code style rule directly through the error list. Place your cursor on the error, warning, or suggestion. Right click and select Set severity. Then select the severity level you would like to configure for that rule. This will update your existing EditorConfig with the rule’s new severity. This also works for third party analyzers.
Set rule severity directly through the error list
Set rule severity directly through the error list
  • Find All References now allows you to group by type and member.
Group by type and member in Find All References
Group by type and member in Find All References
  • You can now make a local function static and pass in variables defined outside the function to the function’s declaration and calls. Place your cursor on the local function name. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Make local function static.
Make local function static
Make local function static
  • You can now pass a variable explicitly into a local static function. Place your cursor on the variable in the static local function. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Pass variable explicitly in local static function.
Pass a variable into a local static function
Pass a variable into a local static function

.NET Productivity

  • You can now configure the severity level of a code style rule directly through the editor. If a user does not currently have an .editorconfig file, one will be generated for them. Place your cursor on the error, warning, or suggestion and type (Ctrl+.) to open the Quick Actions and Refactorings menu. Select ‘Configure or Suppress issues’. Then select the rule and choose the severity level you would like to configure for that rule. This will update your existing EditorConfig with the rule’s new severity. This also works for third party analyzers.
Set rule severity directly through the editor
Set rule severity directly through the editor
  • You can now use the Go To Base command to navigate up the inheritance chain. Go To Base command is available on the context (right-click) menu of the element you want to navigate the inheritance hierarchy. Or you can type (Alt+Home). If there is more than one result a tool window will open with all of the results that you can choose to navigate to.
Go To Base
Go To Base
  • You can now add null checks for all parameters. This will add if statements that check nullity of all the nullable, non-checked parameters. Place your cursor on any parameter within the method. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select the option to ‘Add null checks for all parameters’.
Add null checks for all parameters
Add null checks for all parameters
  • Methods that have no XML documentation can now automatically inherit XML documentation from the method it is overriding. Place your cursor over the undocumented method that implements a documented interface method. Quick Info will then display the XML documentation from the interface method. You can also inherit xml comments from base classes and interfaces with the tag. Docs example.
XML inherit documentation
XML inherit documentation

Xamarin

XAML Hot Reload for Xamarin.Forms

XAML Hot Reload for Xamarin.Forms speeds up your development and makes it easier to build, experiment, and iterate on your user interface. You no longer have to rebuild your app each time you tweak your UI – it instantly shows you your changes in your running app.

Android App Bundle Publishing

You can now create Android App Bundles when publishing your Android applications in Visual Studio. App Bundles provide users with with optimized APKs per their device specifications when downloading an app from the Google Play Store or various Android App Stores.

Android App Bundle Publishing
Android App Bundle Publishing

AndroidX Migration Wizard

You can now use an AndroidX migration wizard to convert your existing Android application to AndroidX from the Android Support Library.

AndroidX Migration Wizard
AndroidX Migration Wizard

Android Layout Linting

You are now provided a set of common issues when editing your layouts inside the Android designer.

Android Layout Linting
Android Layout Linting

Top Issues Fixed in Visual Studio 2019 version 16.4


Known Issues

See all issues and available workarounds in Visual Studio 2019 version 16.4 by following the below link.

Visual Studio 2019 Known Issues


Feedback and suggestions

We would love to hear from you! For issues, let us know through the Report a Problem option in the upper right-hand corner of either the installer or the Visual Studio IDE itself. The Feedback Icon icon is located in the upper right-hand corner. You can make a product suggestion or track your issues in the Visual Studio Developer Community, where you can ask questions, find answers, and propose new features. You can also get free installation help through our Live Chat support.


Blogs

Take advantage of the insights and recommendations available in the Developer Tools Blogs site to keep you up-to-date on all new releases and include deep dive posts on a broad range of features.


Visual Studio 2019 Release Notes History

For more information relating to past versions of Visual Studio 2019, see the Visual Studio 2019 Release Notes History page.


Top of Page