Chuyển tới nội dung
Home » Visual Studio 2019 16.0 | Visual Studio 2019 Version 16.7.13

Visual Studio 2019 16.0 | Visual Studio 2019 Version 16.7.13

How to install Visual Studio 2019 on Windows 10

Visual Studio 2019 version 16.9.3

released March 30, 2021

Issues Addressed in this Release:

  • Fixed a crash in MSBuild that occurred when trying to build a solution with MSBuild.exe that contains a web site project.
  • Fixed a crash scenario caused by some dependencies on ServiceHub.
  • Fixed a blocking issue where users of XAML Visual Diagnostics Tool on Xbox or IoT devices were prohibited from remote debugging.

From Developer Community

Developer Community has a complete list of all of items shipping in this release.

Here are some of the top voted issues released in 16.9.3:

  • There was an error in web.config.
  • Have to select publish profile before publishing
  • After updating from 16.8 to 16.9 ServiceHub.Host.CLR.X86 stops working
  • Visual Studio 2019 v 16.9.2 crashes when opening XAML editor.
  • Issues with the latest Visual Studio 2019 update

Visual Studio 2019 version 16.9.25

Security Advisory Notice

  • CVE-2022-38013 .NET Denial of Service Vulnerability A denial of service vulnerability exists in ASP.NET Core 3.1 and .NET 6.0 where a malicious client could cause a stack overflow which may result in a denial of service attack when an attacker sends a customized payload that is parsed during model binding.
How to install Visual Studio 2019 on Windows 10
How to install Visual Studio 2019 on Windows 10

Visual Studio 2019 version 16.11.14

released May 10, 2022

Issues Addressed in this release

  • Added the implementation for the remaining C++20 defect reports (a.k.a. backports). All C++20 features are now available under the /std:c++20 switch. For more information about the implemented backports, please see C++20 Defect Reports project on microsoft/STL GitHub repository and this blogpost
  • Updated Git for Windows version consumed by Visual Studio and installable optional component to 2.36.0.1
  • Fixed an issue with git integration, where if pulling/synchronizing branches that have diverged, output window would not show a localized hint on how to resolve it.

From Developer Community

  • Visual Studio 2019 creates bad key vault secret value while configuring Azure Cloud Service remote desktop, breaking VS UI

Security Advisories Addressed

CVE-2022-29117 .NET Denial of Service Vulnerability A vulnerability exists in .NET 6.0, .NET 5.0 and .NET Core 3.1 where a malicious client can manipulate cookies and cause a Denial of Service.

CVE-2022-23267 .NET Core Denial of Service Vulnerability A vulnerability exists in .NET 6.0, .NET 5.0 and .NET Core 3.1 where a malicious client can cause a Denial of Service via excess memory allocations through HttpClient.

CVE-2022-29145 .NET Denial of Service Vulnerability A vulnerability exists in .NET 6.0, .NET 5.0 and .NET Core 3.1 where a malicious client can can cause a Denial of Service when HTML forms are parsed.

CVE-2022-24513 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists when the Microsoft Visual Studio updater service improperly parses local configuration data.

Visual Studio 2019 version 16.7.27

released April 12, 2022

In this Release of Visual Studio 2019 version 16.7.27

Security Advisory Notice

CVE-2022-24765 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists in Git for Windows, in which Git operations could run outside a repository while seraching for a Git directory. Git for Windows is now updated to version 2.35.2.1.

CVE-2022-24767 DLL hijacking vulnerability A potential DLL hijacking vulnerability exists in Git for Windows installer, when running the uninstaller under the SYSTEM user account. Git for Windows is now updated to version 2.35.2.1.

CVE-2022-24513 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists when the Microsoft Visual Studio updater service improperly parses local configuration data.

Getting Started with Visual Studio 2019
Getting Started with Visual Studio 2019

Visual Studio 2019 version 16.11.20

released October 11, 2022

Issues Addressed in this release

  • Made Resource View appear more reliably for projects that are reloaded
  • Administrators will be able to update the VS Installer on an offline client machine from a layout without updating VS.

Security Advisories Addressed

  • CVE-2022-41032 .NET Elevation of Privilege Vulnerability A vulnerability exists in .NET 7.0.0-rc.1, .NET 6.0, .NET Core 3.1, and NuGet clients (NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol) where a malicious actor could cause a user to execute arbitrary code.

Visual Studio 2019 version 16.0.16

released July 14, 2020

Issues fixed in 16.0.16

  • Fixed Compiler CodeGen regression for calling a virtual function with v15.9
  • Fixed a bug in the C++ linker missing imports when using umbrella LIBs with difference casing on postfix of DLL name.
  • Fixed a bug in the ARM64 C++ compiler where the wrong values could be restored after setjmp.

Security Advisory Notice for 16.0.16

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.

Install Visual Studio 2019 (Cài đặt Visual Studio lập trình windows form C#)
Install Visual Studio 2019 (Cài đặt Visual Studio lập trình windows form C#)

Visual Studio 2019 version 16.7.13

released March 09, 2021

In this Release of Visual Studio 2019 version 16.7.13

Security Advisory Notice

CVE-2021-21300 Git for Visual Studio Remote Code Execution Vulnerability A remote code execution vulnerability exists when Visual Studio clones a malicious repository.

CVE-2021-26701 .NET Core Remote Code Execution Vulnerability A remote code execution vulnerability exists in .NET 5 and .NET Core due to how text encoding is performed.

Visual Studio 2019 version 16.0.10

released December 10, 2019

Issues fixed in 16.0.10

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 attacked 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 promopting the Live Share guest from consent prior to browsing the host-specified URL.

How to update Microsoft Visual Studio 2019 on Windows 10
How to update Microsoft Visual Studio 2019 on Windows 10

Bug Fixes

Top Issues Fixed in Visual Studio 2019 version 16.7.0
  • Fixed WMI Provider component installation failure.
  • Fixed an issue where users were not able to see test run progress by clicking the left button at the bottom of the bar.
  • Improved performance of discovering available Visual Studio Codespace billing plans.
  • When creating a Visual Studio Codespace, we changed the default suspend time from 30minutes to 3 hours.
  • Fix bug where the Git Changes window informs the user they have incoming/outgoing commits, when in fact they have none.
  • Improved stability of the Diagnostic Tools and Performance Profiler.
  • Addressed an issue where Azure Sphere Visual Studio extension will not be automatically updated due to a minor version mismatch. With the fix, Azure Sphere will be able to get automatically updated when the VSIX auto updater runs.
From Developer Community
  • An error occured in ‘[Unknown]’ while attempting to open
  • Unable to preview file changes or prevent files from being published since 16.6
  • MSDeploy breaks with upgrade to VS2019 16.6.2
  • ArgumentNullException occurs when you try to set URI property of custom WPF control in VisualStudio
  • Visual Studio Prof 2019, 16.7.0 Preview 4.0, change of Output Window behaviour
  • If in a DSL a Connector exposes the Thickness property, the Get/SetThicknessValue(…) methods are not created by T4 Transformation after switching VS language
  • Publish wizard throws “One or more errors occurred.” message
  • Add New Scaffold Item Fails after update to 16.7
  • IntelliSense for C and C++2a designated initalizers
  • Git checkout branch Object reference not set to an instance of an object.
  • ‘GoogleTestExtensionOptionsPage’ Package did not load correctly if there is a conflicting extension installed
  • Options->Xamarin->Apple Accounts ! Please wait until the local provisioning service is initialized
  • Regression: Test Explorer “Copy All” does not give full unit test output
  • Go to definition brings up from metadata
  • “Show items from unimported namespaces” breaks members suggestions
  • Don’t switch the output window to “Source Control – Git” during build
  • Visual Studio is generating xml file when editing axml files
  • VS 16.4 does full build of the azure functions project every time.
  • Error activating the remote language server
  • Recurring null reference when reopening documents
  • View History on context menu in Solution Explorer doesn’t do anything
  • IDE crash in background after opening new solution
  • Visual Studio 2019 version 16.7 Preview 1 crashes during Aapt2DaemonStart()
  • ServiceHub.Host.CLR.x64 has stopped working
  • Write access violation in destructor of const global object
  • Connection to Mac is lost on every build
  • IntelliSense does not work when creating a new class in a new folder
  • Unable to add Xamarin.Forms Item to .shproj
  • Code Linter for C++ not in Preview Options
  • System.IO.FileNotFoundException Microsoft.VisualStudio.Shell
  • Do not show TODOs in task list from SDK headers
  • Visual Studio 2019 hangs when opening a web.config file
  • After updating to 16.7.0 preview 2 cannot add new Views
  • Fold expression does not work directly in SFINAE expression
  • Visual Studio 2019 crash when menu View->Other windows is opened
  • Team Explorer not loading after update to mandatory latest version of Visual Studio 2019
  • Task Runner Explorer calls Task two times on Project Open
  • Visual Studio 2019 .NET Framework WPF controls are showing multiple times
  • Reattach does not work when connection type was Docker (Windows Containers)
  • Aggregate initialization is not performed on dynamic array
  • Not working option TexEditor/c/c++/Advanced/Enable surround with braces
  • Bogus error C2668: “ambiguous call to overloaded function” for call to overloaded function templates with non-type template parameter
  • Visual Studio 16.4 is busy
  • CMake “auto-configure” always deletes cache after editing CMakeLists.txt
  • Missing initialization for POD types when object create in the heap
  • VC compiler serious bug
  • Internal compiler error with C++/CLI indexed property in Visual Studio 2019 version 16.5
  • UI unresponsive exception is thrown on custom extension
  • Internal compiler error on indexer access
  • Upgrade in C++ runtime from 14.24.28127 to 14.25.28610 breaks building Chromium with clang_cl
  • Git stash error
  • ISetupConfiguration.GetInstanceForCurrentProcess throwing COMException: Element not found
  • Xamarin.IOS fails to build with MessagingRemoteException
  • Template class friend declaration ignored
  • Excluding items from Schema Compare crashes Visual Studio if not done in very small batches
  • Visual Studio 2019 v16.5.1 is extremely slow.
  • Cannot use ClassName::* in function breakpoint to set breakpoints on all methods of C++ class in vs2019
  • Feedback tool has broken sign out image link
  • Compilation error C2737 with valid code

Visual Studio 2019 version 16.9.15

released December 14, 2021

Issues Addressed in this Release:

  • Added Python 3.9.7 to Python workload. Removed Python 3.7.8 due to a security vulnerability.

Security Advisory Notice

CVE-2021-43877 Vulnerability An elevation of privilege vulnerability exists in ANCM which could allow elevation of privilege when .NET core, .NET 5 and .NET 6 applications are hosted within IIS.

Bài 1: Hướng dẫn cài đặt Visual Studio 2019
Bài 1: Hướng dẫn cài đặt Visual Studio 2019

Visual Studio 2019 version 16.11.27

released June 13th, 2023

Issues Addressed in this release

  • ActiveX Control Variable wizard will generate ActiveX properties as well as functions, restoring the functionality from Visual Studio 2015.
  • As part of this update, to address CVE-2023-27909, CVE-2023-27910, and CVE-2023-27911, we are removing .fbx and .dae support. This is a third-party x86 component that is no longer supported by the author. Affected users should use the fbx editor.

Developer Community

  • JSON Schemas don’t work with localized Visual Studio
  • JumpThreading Fix for JT value numbering invalidation

Security Advisories Addressed

  • CVE-2023-24897 Visual Studio Remote Code Execution Vulnerability This security update addresses a vulnerability in the MSDIA SDK where corrupted PDBs can cause heap overflow, leading to a crash or remote code execution.
  • CVE-2023-25652 Visual Studio Remote Code Execution Vulnerability This security update addresses a vulnerability where specially crafted input to git apply –reject can lead to controlled content writes at arbitrary locations.
  • CVE-2023-25815 Visual Studio Spoofing Vulnerability This security update addresses a vulnerability where Github localization messages refer to a hard-coded path instead of respecting the runtime prefix that leads to out-of-bound memory writes and crashes.
  • CVE-2023-29007 Visual Studio Remote Code Execution Vulnerability This security update addresses a vulnerability in which a configuration file containing a logic error results in arbitrary configuration injection.
  • CVE-2023-29011 Visual Studio Remote Code Execution Vulnerability This security update addresses a vulnerability in which the Git for Windows executable responsible for implementing a SOCKS5 proxy is susceptible to picking up an untrusted configuration on multi-user machines.
  • CVE-2023-29012 Visual Studio Remote Code Execution Vulnerability This security update addresses a vulnerability in which the Git for Windows Git CMD program incorrectly searches for a program upon startup, leading to silent arbitrary code execution.
  • CVE-2023-27909 Visual Studio Remote Code Execution Vulnerability This security update addresses an Out-Of-Bounds Write Vulnerability in Autodesk® FBX® SDK where version 2020 or prior may lead to code execution through maliciously crafted FBX files or information disclosure.
  • CVE-2023-27910 Visual Studio Information Disclosure Vulnerability This security update addresses a vulnerability where a user may be tricked into opening a malicious FBX file that may exploit a stack buffer overflow vulnerability in Autodesk® FBX® SDK 2020 or prior which may lead to remote code execution.
  • CVE-2023-27911 Visual Studio Remote Code Execution Vulnerability This security update addresses a vulnerability where a user may be tricked into opening a malicious FBX file that may exploit a heap buffer overflow vulnerability in Autodesk® FBX® SDK 2020 or prior which may lead to remote code execution.
  • CVE-2023-33139 Visual Studio Information Disclosure Vulnerability This security update addresses a OOB vulnerability where the obj file parser in Visual Studios leads to information disclosure.

Visual Studio 2019 version 16.11.30

released September 12th, 2023

Issues Addressed in this release

Security Advisories Addressed

  • CVE-2023-36796This security update addresses a vulnerability in DiaSymReader.dll when reading a corrupted PDB file which can lead to Remote Code Execution.
  • CVE-2023-36794This security update addresses a vulnerability in DiaSymReader.dll when reading a corrupted PDB file which can lead to Remote Code Execution.
  • CVE-2023-36793This security update addresses a vulnerability in DiaSymReader.dll when reading a corrupted PDB file which can lead to Remote Code Execution.
  • CVE-2023-36792This security update addresses a vulnerability in DiaSymReader.dll when reading a corrupted PDB file which can lead to Remote Code Execution.
  • CVE-2023-36759This security update removes pgodriver.sys, where reading a malicious file can lead to Elevation of Privilege
How to install Visual Studio 2019 | Installing Visual Studio 2019 on windows 10 | 2022 | NUH Tech
How to install Visual Studio 2019 | Installing Visual Studio 2019 on windows 10 | 2022 | NUH Tech

Visual Studio 2019 version 16.0.15

released June 09, 2020

Issues fixed in 16.0.15

Security Advisory Notice for 16.0.15

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

Visual Studio 2019 version 16.9.12

released October 12, 2021

Issues Addressed in this Release:

  • Updates to the ARM64 and ARM64EC interfaces between the binary and the POGO instrumentation runtime.

Security Advisory Notice

CVE-2021-41355 Disclosure Vulnerability in .NET 5.0

An Information Disclosure vulnerability exists in .NET where System.DirectoryServices.Protocols.LdapConnection sends credentials in plain text on Linux.

CVE-2020-1971 OpenSSL Denial of Service Vulnerability

A potential denial of service vulnerability exists in OpenSSL library, which is consumed by Git.

CVE-2021-3449 OpenSSL Denial of Service Vulnerability

A potential denial of service vulnerability exists in OpenSSL library, which is consumed by Git.

CVE-2021-3450 OpenSSL Denial of Service Vulnerability

A potential flag bypass exists in OpenSSL library, which is consumed by Git.

How to update Visual Studio 2019 to latest version in windows 10 tutorial
How to update Visual Studio 2019 to latest version in windows 10 tutorial

Visual Studio 2019 version 16.0.20

released November 10, 2020

Security Advisory Notice for 16.0.20

CVE-2020-17100 Visual Studio Tampering Vulnerability

A tampering vulnerability exists when the Python Tools for Visual Studio creates the python27 folder. An attacker who successfully exploited this vulnerability could run processes in an elevated context.

Visual Studio 2019 version 16.11.33

released January 9th, 2024

Issues Addressed in this release

  • Updated MinGit to v2.43.0.1 which comes with OpenSSL v3.1.4 and addresses a regression where network operations were really slow under certain circumstances.

Security Advisories Addressed

  • CVE-2024-20656 A vulnerability exists in the VSStandardCollectorService150 service, where local attackers can escalate privileges on hosts where an affected installation of Microsoft Visual Studio is running.
  • CVE-2023-32027 This advisory is republished to address a Microsoft ODBC Driver for SQL Server Remote Code Execution vulnerability in Visual Studio.
  • CVE-2023-32025 This advisory is republished to address a Microsoft ODBC Driver for SQL Server Remote Code Execution vulnerability in Visual Studio.
  • CVE-2023-32026 This advisory is republished to address a Microsoft ODBC Driver for SQL Server Remote Code Execution vulnerability in Visual Studio.
  • CVE-2023-29356 This advisory is republished to address a Microsoft ODBC Driver for SQL Server Remote Code Execution vulnerability in Visual Studio.
  • CVE-2023-32028 This advisory is republished to address a Microsoft SQL OLE DB Remote Code Execution vulnerability in Visual Studio.
  • CVE-2023-29349 This advisory is republished to address a Microsoft ODBC and OLE DB Remote Code Execution vulnerability in Visual Studio.
Hướng Dẫn Cài Đặt Visual Studio 2019
Hướng Dẫn Cài Đặt Visual Studio 2019

Visual Studio 2019 version 16.11.18

released August 9th, 2022

From Developer Community

  • Coded UI in VS2019 – VS crashing when opening and/or expanding UI maps
  • Launching multiple startup projects fails with the error message

Security Advisories Addressed

  • CVE-2022-34716 .NET Information Disclosure Vulnerability An information disclosure vulnerability exists in .NET 6.0 and .NET Core 3.1 that could lead to unauthorized access of privileged information.
  • CVE-2022-31012 Remote Code Execution Git for Windows’ installer can be tricked into executing an untrusted binary
  • CVE-2022-29187 Elevation of Privilege Malicious users can create a .git directory in a folder that is owned by a super-user
  • CVE-2022-35777 Remote Code Execution Visual Studio 2022 Preview Fbx File parser Heap overflow Vulnerability
  • CVE-2022-35825 Remote Code Execution Visual Studio 2022 Preview Fbx File parser OOBW Vulnerability
  • CVE-2022-35826 Remote Code Execution Visual Studio 2022 Preview Fbx File parser Heap overflow Vulnerability
  • CVE-2022-35827 Remote Code Execution Visual Studio 2022 Preview Fbx File parser Heap OOBW Vulnerability

Visual Studio 2019 version 16.0.9

released October 15, 2019

Security Advisory Notice

CVE-2019-1425 NPM Package Elevation of Privilege Vulnerability (published November 12, 2019)

An elevation of privilege vulnerability exists when Visual Studio fails to properly validate hardlinks when extracting archived files. The vulnerabilities were introduced by NPM packages used by Visual Studio as described in the following two NPM advisories: npmjs.com/advisories/803 and npmjs.com/advisories/886. The updated versions of these NPM packages were included in this version of Visual Studio.

Setting Up Visual Studio 2019 for .NET Core & C#
Setting Up Visual Studio 2019 for .NET Core & C#

Visual Studio 2019 version 16.9.2

released March 16, 2021

Issues Addressed in this Release:

  • Update ARM64X global function pointer names
  • Fix for extracting first OBJ of an ARM64X LIB with link -lib -extract
  • Fixed an error were code compiled with Address Sanitizer and optimzations may produce bad code generation that causes Visual Studio 2019 to crash.
  • Fixed a crash caused by adding functions through the Dialog Editor in the Resource Editor
  • Nuget.org will no longer need to be removed as a package source twice
  • Improved NuGet package parsing performance
  • Fixed an error message about deprecated APIs customer received when using Azure SQL Database node in Server Explorer
  • Fixed an issue causing an error message indicating the CascadePackage did not load correctly
  • Fixed an issue causing a building project with fast deployment enabled to fail deployment or take additional time
  • Fixed an issue causing Hot Reload to now show saved changes under the “Full page” mode
  • Fixed an issue with Hot Reload causing Live Visual Tree to not work or apply changes.

From Developer Community

Developer Community has a complete list of all of items shipping in this release.

Here are some of the top voted issues released in 16.9.2:

  • Escape sometimes no longer cancels inline Find Dialog in c#
  • Xamarin forms application deployed with hot restart to iphone crash
  • Performance Profiler reports incorrect session duration
  • Xamarin.Forms HotReload not working since VS2019 16.9.0

Visual Studio 2019 version 16.11.7

released November 16, 2021

Issues Addressed in this Release

  • Adds Xcode 13.1 support.
  • The bootstrappers now respect the –useLatestInstaller parameter, which causes the latest installer to be integrated into layout. This latest installer, which ships with Visual Studio 2022, enables the scenario where enterprises want to transition their clients from one layout location to another. For more information, refer to the [Visual Studio Administrators Guide](* The bootstrappers now respect the –useLatestInstaller parameter, which causes the latest installer to be integrated into layout. This latest installer, which ships with Visual Studio 2022, enables the scenario where enterprises want to transition their clients from one layout location to another. For more information, refer to the Visual Studio Administrators Guide.).
  • Fixed an issue wehre WAP projects would not appear in the startup projects tool bar combo box.
  • Fixed issue with Windows Application Projects (WAP) where, in certain circumstances, final application bundle contains wrong binaries.
  • Prevent opening “Team Explorer > Manage Connections” or “Git Changes” windows from causing TFVC solutions to be unloaded.

From Developer Community

  • Starting Version 16.8.0 up to 16.9.1 becomes unresponsive and restarts frequently
  • IntelliSense error with std::source_location::current()
  • Visual Studio 2019 version 16.10 – UWP – Xamarin: Runtime exception ‘Could not load file or assembly’ after updating to Visual Studio 16.10
  • Visual Studio 2019 version 16.11.3 – Packaging UWP application fails
  • 16.11.6: Package ‘AndroidImage_x86_API125_Private,version=10.0.0.3’ failed to install
Myra Trần x Quân AP gây sốt với bản mashup hit đêm giao thừa Thu Cuối x Đáp Án Cuối Cùng | Sóng 23
Myra Trần x Quân AP gây sốt với bản mashup hit đêm giao thừa Thu Cuối x Đáp Án Cuối Cùng | Sóng 23

Visual Studio 2019 version 16.7.25

released February 8, 2022

In this Release of Visual Studio 2019 version 16.7.25

Security Advisory Notice

CVE-2022-21871 Diagnostics Hub Standard Collector Runtime Elevation of Privilege Vulnerability An elevation of privilege vulnerability exists if the Diagnostics Hub Standard Collector incorrectly handles data operations.

Visual Studio 2019 version 16.11.0

released August 10, 2021

Summary of What’s New in this Release of Visual Studio 2019 version 16.11.0

Updated Help Menu

  • Updated menu highlights Get Started material and helpful Tips/Tricks. It also provides access to Developer Community, Release Notes, the Visual Studio product Roadmap, and our Social Media pages.
  • New My Subscription menu item allows developers to make the most out of their subscriptions through benefit awareness and additional information!

Git tooling

  • Access additional actions from the overflow menu in the branch picker in Git Changes window and status bar.
  • Hover over a branch name to see last commit details in a tooltip.
  • Access additional actions in the repository picker overflow menu from the status bar.
  • Hover over a repository name to see repository details such as local path and remote URL.

C++

  • LLVM tools shipped with Visual Studio have been upgraded to LLVM 12. See the LLVM release notes for details.
  • Clang-cl support was updated to LLVM 12.

Setup

  • Fixed an issue that affected command line execution of the update command. If the update fails the first time, a subsequent issuing of the update command now causes the update to resume the prior operation where it left off.
  • .NET Hot Reload User Experience for editing managed code at runtime.

Details of What’s New in this Release of Visual Studio 2019 version 16.11.0

.NET Hot Reload User Experience for editing managed code at runtime

In this release we are excited to make available the first release of the new Hot Reload user experience when editing code files for applications such as WPF, Windows Forms, ASP.NET Core, Console, etc. With Hot Reload you can now modify your apps managed source code while the application is running with no need to pause execution or use a breakpoint. Instead, simply make a supported change and use the new “apply code changes” button in the toolbar to apply them immediately.

In this update of Visual Studio this new experience is available when running your application under the debugger (F5) and is powered by the Edit and Continue (EnC) mechanism. Therefore, anywhere that EnC is supported you can now also use Hot Reload alongside any other debugger features. .NET Hot Reload will also work alongside XAML Hot Reload, making it possible to make both UI and code-behind changes in your desktop applications such as WPF or WinUI.

Both EnC and Hot Reload also share the same limitations, so be aware that not every type of edit is currently supported. The complete list of what is or is not supported can be found in our documentation.

To learn more about Hot Reload and our long-term vision you can also read more details in our blog post.

Top Issues Fixed in this Release

  • MSVC C++ 14.29.16.10 SxS Toolset updated to match VS 2019 v16.10.4. MSVC Toolset Version for this update is 14.29.30040.0/19.29.30040.0.
  • Update Azure Branding
  • Fix an issue where a failure during CMake test discovery could cause cache generation to fail.
  • Fixed an issue causing TPv0 tests using CSV or SQLCE as data sources to fail to execute with an ArgumentException.
  • Fixed the “ApplicationVerificationFailed” build error with Hot Restart
  • Fixed a failure to conduct fast up-to-date check on WAP projects which was causing those projects to be built (instead of being skipped), even when project is up-to-date and does not need modifications, further causing increased incremental build times in IDE.
  • Fixed the “Xamarin.iOS does not support running or debugging the previous built version of your project” error.
  • Fixed the “Unable to connect to Mac Server with Address” error when trying to distribute iOS applications
  • “Modules for Standard Library (experimental)” was missing, but has been restored.
  • Fixed an EDG assertion failure on nested co_yield.
  • Fixed an issue causing Microsoft Azure Tools for Visual Studio to trigger other .dlls to load in the About Box.
  • Fixed an accessibility issue causing High Contrast Account Settings to not show.
  • Fixed a formatting issue when using @

    {if(true)}

    .
  • Fixed an accessibility issue with screen readers failing to announce collapsed code headers.
  • Fixed the Luminosity contrast ratio for Country boundary Foreground/background color to be greater or equals to 3:1 so that visually impaired users can identify these controls.
  • Fixed an accessibility issue where Visible name and accessible name are not similar for “Server” edit field, “Site name” edit field and “Target Runtime” combo box.
  • Fixed a bug causing the screen reader to announce the Connecting status message information under Add SQL Server blade.
  • Filter was missing from the completion list in VB projects.
  • Fixed an issue causing Visual Studio to occasionally stop responding when loading Microsoft.Maui-net6.sln.
  • Fixed an error when building IOS project or XF project that showed the warning “Xamarin.iOS.Common.targets”.
  • Fixed branch picker menu grouping.
  • Fixed an issue causing the repository below the selected repository to open instead of the desired repository.
  • Fixed a bug causing warnings for template functions to follow an incorrect ruleset.
  • Fixed a bug causing the Microsoft account dropdown to get truncated when resizing from 125% to 150% or 175% to 200%.
  • Fixed an accessibility bug where the narrator does not announce the label name.
  • Made it easier for users to access the “convert color to resource” button.
  • Made it easier for low vision users to view the focus on the “Select previous gradient stop” and “Select Next gradient stop” buttons.
  • Corrected issues with screen reader users not getting the proper information about buttons.
  • GitHub specific error messages were not always showing when pushing commits.
  • Fixed an issue causing warnings when trying to connect to SharePoint to provision workflow debugging prerequisites.
  • Fixed an issue causing network operations to not work with the Fork and the remote Fork branches in the Git repo window.
  • Fixed a Database Project issue where dragging a file from solution explorer into an opened one is deleting the file from the file system
  • Fixed an issue causing an exception in .cshtml and .razor files.
  • Fixed a slow display of files and icons in the Visual Studio IDE and Solution Explorer.
  • Fixed an error with Git messaging that reported ‘It is not allowed to run multiple bulk file operations at a time.’
  • Improved ease of accessibility when accessing the controls for any path of the selected Profile.
  • Corrected an ‘Error List’ warning when publishing a Cloud Service project with a ‘Single Page Application’ template.
  • Fixes an issue where attempting to close the quick start window can cause Visual Studio to crash
  • Fixed an inability to publish database projects with null values and an ‘str’ parameter name.
  • Added support for SSDT MERGE statements.
  • Fixed an issue with F# Interactive where NuGet package references were no longer working.
  • Added ability to use Previous layout folders searching packages during layout operations.
  • Added additional accessibility improvements for keyboard only users in debugging and menu selection.
  • Fixed a localization error with Test Explorer.
  • Fixed an error causing builds to fail in C# VSIX projects.
  • Fixed an error where publishing failed in an ASP.NET Core App running on Docker (Windows/Linux) to Docker Container with error:”Current context “desktop-linux” is not found on the file system”.
  • Converted to using the new DartLab instance which gives us the latest fixes and simplifies the YAML.
  • Fixed an issue when clicking “Go To Declaration” that resulted in the cursor jumping to an incorrect position.
  • Fixed EnC regression.
  • Fixed an error causing Visual Studio to stop responding when creating a Service Fabric application.
  • Fixed an error where the Container Orchestrator Support context item disappears after adding docker support for an Azure Function project with .NET 5(Isolated) type selected.
  • Fixed a situation where F5/Ctrl+F5 produced an error message, “Docker command failed with exit code1.”
  • Added Service Fabric and Add Orchestra Support dialog.
  • Fixed a failure to restore NuGet deleted packages.
  • Fixed an error causing mstest projects to remove LUT windows after renaming.
  • Fixed formating when providing no container name in a code search.
  • Fixed missing warning messages in CppCoreCheck.
  • Fixed a bug when adding a class in ASP.NET causing a yellow bar with the error message: ‘CSharpSyncNamespaceCodeRefactoringProvider’.
  • Improved performance around using PointerSafetyXtension in CppCoreCheck.
  • Improved localization around VC++ features.
  • Fixed a build error when the solutionPath variable evaluates to undefined.
  • Fixed a rare scenario that could keep Visual Studio instances from closing if the Test Explorer is open in the solution.
  • Fixed a visibility issue with high contrast black in virtual machines shifting focus.
  • Fixed an issue where an error “No such image” occurs when removing multi-selected images that have been tagged.
  • Improved the XAML typing experience on the LiveShare client.
  • Fixed an issue when using the Navigate To with a speech recognition command causing the user to wait for the ToolTip to clear before seeing the result.
  • Fixed an issue causing previously opened documents to not restore when a solution is reopened.
  • Fixed a UWP crash when using the new Sample Data feature.
  • Fixed a bug where there were no project properties provider for “Persistence = AssemblyReference”.
  • Decreased processor consumption of setup.exe.
  • Fixed an issue preventing HRESULT resources from being customized for XBOX.
  • Fixed an unhandled exception after clicking “Debug Tests”.
  • Fixed a build error message “NETSDK1 031” when using a Windows Application Packaging Project.
  • Fixed a crash after ending some LiveShare Sessions.
  • Fixed a bug causing a failure of the “X” button on a page of the First Launch Wizard.
  • Fixed an “Operation not supported” error message in LiveShare.
  • Fixes a bug in Cloud Service (extended support) publish with different settings value in different service configurations.
  • Fixed an issue with C++20 Modules IntelliSense where some language constructs would cause the compiler to crash.
  • Fixed an issue that will cause a small amount of additional memory to leak.
  • Fixed an API breaking change on AudioUnitPropertyIDType.
  • Developers using UWP unit test framework who wish to run their tests on remote devices or emulators were unable to run the tests on remote devices.

Top Voted Issues From Developer Community

  • Code analysis/PREfast performance regression from 16.6.4 to 16.9.4
  • Codeanalysis warning C6285 in STL functional.h in VS 16.10 preview 4. Worked in 16.10 preview 2
  • EnforceProcessCountAcrossBuilds emits code analysis warnings on system headers
  • Compile errors for external headers
  • Incorrect lock warnings by analyzer C26110
  • CMakePresets based generation on Linux Remote fails with “Error: Object reference not set to an instance of an object.”
  • Unable to copy text from git repository view
  • Broken intellisense with template specialization
  • ICE: ARM64 optimizing for /std:c++latest
  • Error adding Apple Developer Account: A Parameter ‘certificateType’ has an invalid value: ‘Unknown value:MAC_INSTALLER_DISTRIBUTION’
  • Functional(813) has warning C6285
  • ICE on C++20 modules + boost::asio
  • 16.9.2 Freezing when working on SQL Server project
  • Build Warning MSB4011 Since Last Xamarin and XCode Updates
  • How enable the multthread to compile source in Visual studio 2019 16.9 with clangcl
  • Incorrect formatting of switch statement with static_casts
  • Visual Studio 2019 16.5.4 internal compiler error when using SSE
  • Noexcept default constructor
  • MSVC Compiler bug on _InterlockedCompareExchange64
  • NativeReference cannot recognize MSBuild property value
  • Incorrect Diagnostic: 26444 NO_UNNAMED_RAII_OBJECTS
  • Incorrect C6240 LOGICALANDNONZERO
  • Diagnostic Tools window loads up in miniature and will not resize properly
  • Coroutine uses promise_type::unhandled_exception with exceptions disabled
  • Bad(noexcept) exception handling information on AMD64
  • ToolTip Blocking Search Results
  • False postivie error C2176 in C++20 mode
  • Operator new provides the wrong arguments to _aligned_malloc when packing is spectified
  • Rejects valid parsing of lambda expression
  • An error ‘Unable to attach. Process ‘SPUCWORKERPROCESS.exe’ is not running’ shows when deploying SharePoint2019 sandbox project
  • Unexpected warning C4834 after updating to 16.10 Preview 2
  • Syntactically invalid with a template code is silently ignored with /std:c++latest.
  • BUG: Backspacing in branch filter removed characters from code
  • StreamJsonRpcRemoteInvocationException: Error enumerating over Github credential store
  • Cannot use arrow keys, cut, copy, or paste in Git branch “type here to filter the list” input box
  • Error adding Apple Developer Account: A parameter ‘certificateType’ has an invald value: ‘Unknown value: MAC_INSTALLER_DISTRIBUTION’
  • Git Integration: Pressing backspace in Visual Studio 2019 branch filter is applied in editor window instead of in branch panel
  • Unable to deploy to emulator or device using .NET MAUI
  • Visual Studio 2019 Professional 16.10.0 – Tabs do not render correctly for SQL files.
  • Cpp targets redirection fails when using DisableInstalledVCTargetsUse=true if MinimumVisualStudioVersion is 16.0
  • Build Warning MSB4011 Since Last Xamarin and XCode Updates
  • CMake Integration: Environments specified in

    CMakeSettings.json

    are not inherited when Visual Studio is used as the generator
  • There was an error activating the remote language server
  • .pdb locked by ServiceHub.DataWarehouseHost.exe after running VS Profiler
  • Visual Studio 2019 Preview can’t launch new MAUI app for Android
  • Blazor save & refresh build hangs Visual Studio
  • Code Map shows method call not existing in the source code
2|15|2024: 5PM: Những bài bình luận chính trị, kinh tế Hoa Kỳ
2|15|2024: 5PM: Những bài bình luận chính trị, kinh tế Hoa Kỳ

What’s New in Visual Studio 2019 version 16.0

Support Timeframe

Visual Studio 2019 version 16.0 is now out of support.

Enterprise and Professional users of Visual Studio 2019 version 16.0 were supported and did receive fixes to security vulnerabilities through January 2021. This timeframe was determined by the fact that in December 2019, Visual Studio 2019 version 16.4 was designated as the next servicing baseline to the Visual Studio 2019 product. For more information about Visual Studio supported baselines, please review the support policy for Visual Studio 2019.

Refer to the latest version of the release notes or visit the Visual Studio site to download the latest supported version of Visual Studio 2019.

Visual Studio 2019 version 16.0 Releases

  • January 12, 2021 — (Final Release) Visual Studio 2019 version 16.0.22
  • December 08, 2020 — Visual Studio 2019 version 16.0.21
  • November 10, 2020 — Visual Studio 2019 version 16.0.20
  • October 13, 2020 — Visual Studio 2019 version 16.0.19
  • September 8, 2020 — Visual Studio 2019 version 16.0.18
  • August 11, 2020 — Visual Studio 2019 version 16.0.17
  • July 14, 2020 — Visual Studio 2019 version 16.0.16
  • June 09, 2020 — Visual Studio 2019 version 16.0.15
  • May 12, 2020 — Visual Studio 2019 version 16.0.14
  • April 14, 2020 — Visual Studio 2019 version 16.0.13
  • March 10, 2020 — Visual Studio 2019 version 16.0.12
  • January 14, 2020 — Visual Studio 2019 version 16.0.11
  • December 10, 2019 — Visual Studio 2019 version 16.0.10
  • October 15, 2019 — Visual Studio 2019 version 16.0.9
  • September 10, 2019 — Visual Studio 2019 version 16.0.8
  • August 13, 2019 — Visual Studio 2019 version 16.0.7
  • July 9, 2019 — Visual Studio 2019 version 16.0.6
  • June 11, 2019 — Visual Studio 2019 version 16.0.5
  • May 14, 2019 — Visual Studio 2019 version 16.0.4
  • April 30, 2019 — Visual Studio 2019 version 16.0.3
  • April 18, 2019 — Visual Studio 2019 version 16.0.2
  • April 09, 2019 — Visual Studio 2019 version 16.0.1
  • April 02, 2019 — Visual Studio 2019

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 there.

Issues fixed in Visual Studio 2019 RC

most recently updated on April 26, 2019

  • Value cannot be null. Parameter name: pUnk when checking in code to TFS.
  • “Subtype Designer” is added unnecessarily to xml-based files like csproj.
  • TLS 1.0: The request was aborted: Could not create SSL/TLS secure channel.
  • Solution Explorer: touch pad gesture scroll is too sensitive.
  • [MSConnect 1173006] Task List with filter set to Entire Solution doesnt display tasks / todos when the file is closed.
  • Xamarin.iOS can’t select image asset for Image View.
  • fatal error C1001: An internal error has occurred in the compiler.
  • Visual Studio 2019 – EF6 edmx文件无法保存-VS 2019 Preview 1 – EF6 edmx file cannot be saved.
  • [WebKit] an undefined class is not allowed as an argument to compiler intrinsic type trait ‘__is_assignable’ (regression).
  • Visaul Studio 2019: nuget package manager has poor contrast.
  • Team Explorer – Changes: panel not sizing to the Team Explorer window.
  • Visual Studio 2017 SQL Server Object Explorer server list not persisting .
  • intellisense problems with linux-x64 mode.
  • Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: index.
  • Visual Studio 2017 UNDO does not work/stops working (reported AGAIN!!!!).
  • Intellisense not working for files created under WSL.
  • Intellisense error: C++11 static constexpr member initialization causes “member may not be initialized”.
  • VS doesn’t restore windows position when switching in/out of debug.
  • Third party toolbox items are reloaded every time VS2019 Preview 2.2 is started.
  • ‘Set as StartUp Project’ crashes the IDE after updating to VS2019 Preview Release 3.
  • Visual Studio 2019 building Visual Studio 2017 C++ projects fail.
  • Fixed Toolbox refresh issue.
  • Toolbox controls are making vssettings file too big.
  • SSDT: Fix for Login failed errors when performing a New Data comparison function .
  • SSDT: Fix for Source is Unavailable error when performing Schema Compare .
  • SSDT: Fix for Schema Compare Generate Script does not generate script .
  • Find in files “Locating next match” UI is annoying.
  • Find files keeps defaulting to current document.
  • Quick references freezes VS 2019 RC.
  • PackageId:MsSqlCmdLnUtils;PackageAction:Install;ReturnCode:1603;.
  • Error List does not show errors because it is scoped to “Current Document”.
  • Cannot use conditional breakpoint on PropertyInfo.Name value.
  • Visual Studio crashes when parsing macros at the end of a file.
  • Search in Visual Studio 2019 is very slow.
  • Visual Studio hangs when starting debugging.
  • vdproj not supported in Visual Studio 2019 RC.
  • Visual Studio installer welcome image contains offensive element for Chinese.
  • VSIX Extension pre-req has been removed in Visual Studio 2019 RC breaking extension compatibility.
  • Create Project from Start Screen Ignores Selected Project Folder.
  • cpp properties is dialog does not show up when using Project menu item or select “Manage configuration” drop down menu.
  • Visual Studio 2019 Build Tools – developer prompt title says “Developer Command Prompt for Visual Studio 2017”.
  • German tranlation regarding the Feedback Tool: Help > Send Feedback > Report a Problem.
  • 自动完成功能,如果双击候选项,会丢失输入焦点,需要单机编辑器才能继续输入-AutoComplete function, if you double-click the candidate, will lose the input focus, need a stand-alone editor to continue to enter.
  • Context menus are sometimes placed on the wrong monitor in a multiple monitor configuration.
  • Visual Studio 2019 conflict with QQ Pinyin.
  • Cannot drag maximized Visual Studio window.
  • Access violation C++ /CLI 15.9.5 ISO C++ Latest Draft Standard since 15.9.5.
  • Modal progress dialog stays open permanently, even when IDE is responsive (‘Preparing Solution’, ‘Creating Project’, Edit and Continue, etc).
  • PackageId:OpenJDKV1;PackageAction:Uninstall;ReturnCode:0;.
  • Visual Studio 2019 – Toolbox always shows Initializing.
  • Intellisense in Razor files (.cshtml) is not working..
  • SSDT schema comparison doesn’t highlight differences in files.
  • Visual Studio exception when opening Razor cshtml files.
  • Failed to initialize extension.
  • Asp Core : Create new view show error.
  • VS 2019 RC — Can’t create Winforms (.Net Core) — multiple errors.
  • Project References Not Loading After Branch Switch.
  • Scaffolding error: There are no scaffolders supported for this item.
  • Load configuration only works before the first installation is completed.
  • Dropdown project type = text is partially hidden when “Make Text Bigger” is used.
  • Wrong localization.
  • Properties Window in Forms Designer shows vertical scrollbar without drag handle with automatic scaling on 4K display in Visual Studio 2019 RC.
  • Razor autocomplete works until you tab/enter then it uses html.
  • VSIXInstaller.exe crashes randomly when installing multiple extensions sequentially in Visual Studio 2019 RC.1.
  • Moving a } crashes Visual Studio.
  • Telerik UI for WPF controls disabled in Visual Studio 2019 Preview 3 and Preview 4.
  • Unhandled System.OperationCanceledException.
  • Visual Studio 2019 RC crashes on startup when using a 3rd party IME (QQ Pinyin, Google IME).
  • Visual Studio 2019 Preview 4 crash if closing undocked Window.
  • Intellisense error: C++11 static constexpr member initialization causes “member may not be initialized”.
  • Start Page “Remove From List” stops working.
  • $(VCIDEInstallDir) is an invalid path. Missing backslash in Microsoft.Cpp.Common.props.
  • Visual Studio 2019 Preview 2.0+ crashes when opening soultion filter.
  • Manage Extensions toolbar throws exception.
  • CMake configuration compiler test fails for LLVM/clang-cl
  • SSDT: Fix to improve performance of loading solutions with multiple projects.
  • SSDT: Fix for SQL files not always being deleted when performing a Schema Compare between a database and a project and a delete table is executed subsequently.
  • SSDT: Accessibility fixes to improve narration capabilities.
  • SSDT: Replaced older sqlncli driver with new Microsoft ODBC Driver for SQL Server.
  • We have fixed slow reload of multiple C# and Visual Basic projects.
  • When IntelliSense is present, when a user types Shift + Enter, the active selection will be completed and a new line inserted.
  • We have fixed a PMA issue where editor tooltips and light bulb doesn’t render properly.
  • Notifications about crashes caused by extensions now show up again.
  • Notifications about performance of Visual Studio have been secured against tampering.
  • We have fixed an issue with toolbar rendering when dragged across displays.
  • We have fixed an issue with Tools Options rendering when running with per-monitor awareness enabled.
  • Various DpiHelper classes has been deprecated (extensibility).
  • We have fixed splash screen scaling to better match the primary monitor scale factor.
  • We have fixed an issue in settings import where warnings/errors were not always reported correctly.
  • We have fixed an issue where Tools Options reported software rendering regardless of rendering tier.
  • We have fixed an issue where the name of the open folder was not displayed in the title bar region.
  • We have fixed an issue with find in files positioning when per-monitor awareness is enabled.
  • We have fixed an issue with dock adorner rendering when per-monitor awareness is enabled.
  • You can now use Time Travel Debugging with the snapshot debugger on ASP.NET Apps running on an Azure VM. Please note that this feature may not work in all Azure regions at release.
  • We have updated the Dockerfile scaffolding in Visual Studio Tools for Kubernetes to use the Microsoft Container Registry instead of Docker Hub.
  • We have fixed an issue in Visual Studio Tools for Kubernetes where modifying Dockerfile.develop does not cause the service to be redeployed.
  • We have fixed an issue in Visual Studio Tools for Kubernetes where a service in an Azure Dev Spaces project could fail to start.
  • We have fixed an issue in Visual Studio Tools for Kubernetes where a service in an Azure Dev Spaces project stops running after debugging is stopped in Visual Studio.
  • We have fixed an issue in Visual Studio Tools for Kubernetes where a null reference error dialog is sometimes displayed when picking accounts in the Azure Dev Spaces Dialog.
  • We have fixed an issue in Visual Studio Tools for Kubernetes where the cluster selection dialog is displayed when adding Kubernetes orchestration support.
  • We have fixed rendering of the Import and Export Settings Wizard when running per-monitor aware
  • We have fixed sizing of the New Project Dialog when running per-monitor aware
  • We have made a set of visual refinements to the start window
🔥10 New Features in Visual Studio 2022
🔥10 New Features in Visual Studio 2022

Visual Studio 2019 version 16.7.2

released August 18, 2020

In This Release of Visual Studio 2019 version 16.7.2

Top Issues Fixed from Developer Community in Visual Studio 2019 version 16.7.2
  • Gold bar following RPC exception in StreamPipeReader.AdvanceTo: No reading operation to complete
  • We have resolved a crashing issue that would occur when typing the comma separating positional records, but before having typed the next character.
  • Visual Studio 2019 v16.7 Xamarin Android crash on start up in debug.

Visual Studio 2022 Preview

A big thank you to everyone who has participated in our Visual Studio 2019 previews! Your engagement with our preview branches helps us deliver a better product and gather valuable feedback on the features we’re building.

We encourage you to join us in the next iteration of our product: Visual Studio 2022. Download the current Visual Studio 2022 preview and use it just like you have been using Visual Studio 2019 (you can install them side-by-side) and let us know how it’s going via Developer Community or Report a problem.

It’s a good time for developers, administrators, and DevOps managers to review their current version usage. And, administrators should plan for migration and consider testing the final release of Visual Studio 2019. Acquire the latest and most secure version of Visual Studio in the downloads tab of the Subscriptions portal.

To experience all that Visual Studio 2019 has to offer, download v16.11 today. Don’t forget to report a problem or give us feedback on Developer Community!

Visual Studio 2019 Preview build (version: 16.0.0 Preview 1) hiện đã bị lộ và có thể tải xuống từ các máy chủ của Microsoft. Link cài đặt đã được tìm thấy bởi @WalkingCat và trước khi Microsoft kịp xóa nó khỏi download server, bạn cũng có thể tải nó về.

Bạn có thể cài đặt Visual Studio 2019 Preview cùng với với Visual Studio 2017. Liên kết tải xuống của installer sẽ ở cuối bài viết này.

Đây là bản early preview đầu tiên của trang bắt đầu cài đặt trong Visual Studio 2019, nơi bạn sẽ được phép chọn có lấy code từ source control repository hay tạo / mở một project hay không. Trang được thiết kế đơn giản để giúp bạn có trải nghiệm bắt đầu trơn tru nhất.

Khi bạn bấm vào”Create a new Project” trên Visual Studio 2019 Start Screen, đây là Project wizard mới sẽ hiện lên trên màn hình.

“Create a new Project” wizard mới cho phép bạn chọn nền tảng mà bạn muốn xây dựng ứng dụng. Chúng tôi có thể thấy một số nền tảng (như: Android, Azure, iOS, Linux, MacOS, tvOS, Windows và Xbox) trong hình dưới đây:

Tiếp theo, Visual Studio 2019 cho phép bạn thực hiện những cái đặt tinh chỉnh cho project. Ở đây bạn sẽ được phép nhập tên dự án, vị trí, tên giải pháp và .NET Framework.

Ngay bây giờ, bạn có thể tải nó về TẠI ĐÂY

Visual Studio 2019 dự kiến sẽ được phát hành trong nửa đầu năm 2019, nhưng phiên bản preview dự kiến sẽ được phát hành vào cuối năm 2018.

Nguồn: Sưu tầm từ internet via kunal-chowdhury

Thiết kế và lập trình Website PHP, Laravel chuyên nghiệp – FullStack
Lập trình ứng dụng trên nền tảng android
Lập trình Ứng dụng với Công nghệ ASP.NET Core MVC, WebAPI, ReactJS – FullStack
Lập trình ứng dụng với WINDOWS FORM
Lập trình ứng dụng với JAVA (FORM)
Thiết kế và lập trình Ứng dụng với công nghệ Java (Java Framework springBoot, hibernate,…) – FullStack
Thiết kế và lập trình website với công nghệ HTML5, CSS3, Javascript, Bootstrapt 4, Jquery
Lập trình frontend với reacjs (Full)

Downloads

Visual Studio 2019 Launch: Write beautiful code, faster
Visual Studio 2019 Launch: Write beautiful code, faster

Visual Studio 2019 version 16.9.11

released September 14, 2021

Issues Addressed in this Release:

  • We have fixed a fatal internal compiler error caused by unnamed structs whose fields are referenced from SAL annotations.
  • Fixes a rare crash when analyzing templated code that uses __uuidof.

Security Advisory Notice

CVE-2021-26434 Visual Studio Incorrect Permission Assignment Privilege Escalation Vulnerability

A permission assignment vulnerability exists in Visual Studio after installing the Game development with C++ and selecting the Unreal Engine Installer workload. The system is vulnerable to LPE during the installation it creates a directory with write access to all users.

From Developer Community

  • PreFast: Fatal error C1001: Internal compiler error
  • WinARM64 Build Failures with MFC/ATL Link issues after migrating from VS 16.8.6 to VS 16.9.5

Servicing Baselines

This is the final servicing baseline for Visual Studio 2019. This version will be supported with fixes and security updates for the duration of the Visual Studio 2019 support timeframe. As a result, we encourage Enterprise and Professional customers to standardize on Visual Studio 2019 16.11 because it will provide a long term stable and secure development environment.

Now that version 16.11 is available, version 16.9 will go out of support in October 2022. Prior minor versions 16.0, 16.1, 16.2, 16.3, 16.5, 16.6, 16.8 and 16.10 are no longer under support. These intermediary releases only received servicing fixes until the next minor update was released. Here are the versions still under support and their end of service dates:

  • 16.4 – October 2021
  • 16.7 – April 2022
  • 16.9 – October 2022
  • 16.11 – April 2029

For more information, see our lifecycle and support policy.

Đóng gói phần mềm C# Visual Studio 2019 để mang đi cài các máy khác
Đóng gói phần mềm C# Visual Studio 2019 để mang đi cài các máy khác

Visual Studio 2019 version 16.11.2

released August 25, 2021

Issues Addressed in this Release

  • Fixed an issue where CMake cache generation would fail, which blocked IntelliSense, build, and debug.
  • Fixed warning “Evaluating the function ‘System.Diagnostics.TraceInternal.Listeners.get’ timed out and needed to be aborted in an unsafe way” when starting debugging on some .NET and dotnet Core application.

From Developer Community

  • CMake cache generation “hangs” after upgrade from vs2019 16.11.0 to 16.11.1
  • Could not find any resources appropriate for the specified culture or the neutral culture. Make sure “Microsoft.VisualStudio.Data.Providers.SqlServer
  • Build Selection stopped working VS 16.11

Visual Studio 2019 version 16.9.4

released April 13, 2021

Issues Addressed in this Release:

  • Fixed a SFINAE bug causing an error with some forms of template names in non-dependent base classes.
  • Fixed case where IntelliCode is trying to log into a temporary directory and access to the temporary directory was denied.
  • An issue where some Visual Studio functionality was limited when third-party privilege management software is also installed has been resolved.
  • Addressed an issue where customers repeatedly start debugging on XBox, more and more kernel resources are consumed. Eventually requiring the XBox to be restarted, which would lose any state.
  • Addressed a hang when debugging native code with Insider Preview builds of Windows.
  • Fixed an accessibility bug with keyboard focus.
  • Added back missing Xamarin templates (iOS/Android Class Library, iOS/Android Bindings Library, Android Wear, Xamarin.UITest) in the New Project dialog. These templates were hidden by mistake.
  • For C++ CMake-based projects targeting Linux using an SSH connection, the destination directory specified in

    CMakeSettings.json

    by the

    remoteCMakeListsRoot

    property has been restored to the previous behavior in VS 16.8, where the destination of the copy corresponds to the source directory’s root. Details in the ticket Connection to remote Linux machine uses incorrect destination path.

Security Advisory Notice

CVE-2021-27064 Visual Studio Installer Elevation of Privilege Vulnerability

A remote code execution vulnerability exists when the Visual Studio installer executes the feedback client in an elevated state.

CVE-2021-28313 / CVE-2021-28321 / CVE-2021-28322 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector incorrectly handles data operations.

From Developer Community

Developer Community has a complete list of all of items shipping in this release.

Here are some of the top voted issues released in 16.9.4:

  • Visual Studio 16.8 upgrade broke linkage dependencies from MakeFile projects.
  • Error “The ‘Environment Package Window Management’ package did not load correctly” when launching Visual Studio 16.9 after an upgrade.
  • Toolset 16.9 regression vcxproj producing static libraries: pdb is not copied to the output anymore.
  • Visual Studo freezes during Win32 debugging.
  • Connection to remote Linux machine uses incorrect destination path.
  • Cannot find Xamarin Android Binding Library template in Visual Studio 2019.
  • Could not start Visual Studio due to an error: System.InvalidOperationException: Controller is not responding to incoming requests.
  • SFINAE bug: ‘Failed to specialize alias template’ in Visual Studio 2019 16.9.
  • ASAN is incompatible with RTC.
  • After updating to vision Visual Studio 2019, I get this error in the editor.
Download and Install Report Viewer For Visual Studio 2019 | FoxLearn
Download and Install Report Viewer For Visual Studio 2019 | FoxLearn

Visual Studio 2019 version 16.7.0

released August 5, 2020

In This Release of Visual Studio 2019 version 16.7.0

C++
  • Our remote C++ support now supports a wider range of Linux distros and shells, including sh, csh, bash, tsch, ksh, zsh, and dash. You can override the choice of a shell for a remote connection by modifying the new “shell” property via ConnectionManager.exe. This support has been tested with both MSBuild-based Linux projects and CMake projects targeting a remote Linux system or WSL.
  • You can now use Ninja (a build system that evaluates incremental builds very quickly) to improve incremental build times for MSBuild-based Linux projects. You can opt into this feature by setting “Enable Incremental Build” to “With Ninja” in the General Property Page. Ninja (ninja-build) must be installed on your remote Linux system or WSL.
  • New C++20 Standard Library features have been implemented. Please refer to the STL Changelog on GitHub for a detailed list.
  • You can now edit and set default remote SSH connections in the Connection Manager. This means you can edit an existing remote connection (e.g. if its IP address changed) and set default connections to be consumed in CMakeSettings.json and launch.vs.json. Remote SSH connections allow you to build and debug C++ projects on a remote Linux system directly from Visual Studio.
  • Enhanced IntelliSense support for Clang on Windows (clang-cl) in Visual Studio. The clang include path now includes the clang libraries, we’ve improved in-editor squiggle display when using the std library, and we’ve added support for C++2a in clang mode.
  • You can now try out underlining code errors and see more suggested quick fixes in C++ projects. Enable this feature under Tools > Options > Text Editor > C/C++ > Experimental > Set ‘Disable Experimental Code Linter’ to false. Learn more on the C++ Team Blog.
  • We’ve added four new code analysis rules to incorporate additional safety features into C++: C26817, C26818, C26819, and C26820.
  • We’ve added first-class support for debugging CMake projects on remote systems with gdbserver.
  • Find memory corruption errors easily with an experimental implementation of AddressSanitizer for C++ in Visual Studio, now available for x64 native projects. We also now support the use of debug runtimes (/MTd, /MDd, /LDd).
  • IntelliSense now has basic support for Concepts, designated initializers, and several other C++20 features.
  • .ixx and .cppm files are now recognised as C++ and will be treated as such by the syntax highlighter and IntelliSense.
Define playlists dynamically

You can now define playlists dynamically based on Project, Class, or Namespace. This means you can configure a playlist to include everything in a certain project/class/namespace; any new test added to that group will automatically be included in your playlist!

  • Create a playlist by right clicking on a project, namespace, or class grouping in the Test Explorer.
  • Edit what groups are included in the playlist by clicking on the edit button in the tool bar. Check boxes will appear. Edit groups as desired.
  • Instead of being a static list of tests these playlists dynamically update based on rules. If you want to better understand what rules are generating your dynamic playlist, save the playlist file to disk with the save button and view the rules generated in the xml.
  • You can continue to include/exclude individual tests and the playlist will be able to either update its dynamic rules or switch back to keeping track of tests as a static list. You can also use traits to define a dynamic group by editing the playlist xml file directly.
Git Productivity

Toggle on the ‘New Git user experience’ Preview Feature in Tools | Options | Environment to use this experience.

  • Create a new Git repository, starting from any folder or a brand new folder
  • Save and close an open folder or solution before starting a new clone operation
  • View commit or stash message errors clearly in the commit text box
  • View and manage Git branches in a tree view within a new Git Repository window
  • Switch between and interact with the history graph of each branch in the Git Repository window
  • View incoming and outgoing commits in the Git Repository window
  • Git Productivity team blog with more details of recent features

Resolve merge conflicts with a Git focused merge editor using:

  • An info bar in files containing merge conflicts that prompts you to open the merge editor
  • More informative titles and captions, and less clutter in the merge editor
  • Diffs within conflicts that align matching lines, show word level differences, and display visible whitespace when it is the only difference.
  • Two-way merges for file level add/add conflicts
  • The ability to resolve all conflicts to one side or the other with a single click
  • A toggle to focus on just conflicts, ignoring non-conflicting differences
JavaScript/TypeScript
  • The implementations of Completion and Quick Info have been updated to better support LiveShare scenarios.
Local Process with Kubernetes

Local Process with Kubernetes allows you to write, test and debug your .NET code on your development workstation while connected to your Kubernetes cluster with the rest of your application or services. By connecting your development workstation to your cluster, you eliminate the need to manually run and configure dependent services on your development machine. Environment variables, connection strings and volumes from the cluster are available to your microservice code running locally. There is no need for extra assets, such as a Dockerfile or Kubernetes manifests. Run, debug, and test your .NET code as you normally would.

To enable Local Process with Kubernetes, go to Tools > Options > Envrionment > Preview Features and select “Enable local debugging for Kubernetes services”.

For .NET console applications, an additional step is required. Install the “Microsoft.VisualStudio.Azure.Kubernetes.Tools.Targets” Nuget Package.

.NET Productivity

There is now a warning and code fix when a suppression operator is present but has no effect. A second code fix suggesting the correct negating expression is also available. Place your cursor on the suppression operator. Press (Ctrl + .) to trigger the Quick Actions and Refactorings menu. Next, select from one of the following:

  • To remove the operator completely, select Remove operator (preserves semantics):
  • To negate the expression, select Negate expression (change semantics):
  • You can also negate the expression with the new C# 9

    not

    pattern if it is available in your project:

You can now generate properties when generating a constructor in a type. Place your cursor on the instance. Press (Ctrl + .) to trigger the Quick Actions and Refactorings menu. Select Generate constructor in

(with properties).

  • Quick Info now displays the diagnostic ID along with a help link where you can easily navigate to our documentation to learn more about warnings and errors in your code.
  • There is now a quick action to add a debugger display attribute to a class. This allows you to pin properties within the debugger programmatically in your code. Place your cursor on the class name. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Add ‘DebuggerDisplay` attribute. This will add the debugger display attribute to the top of your class and generate an auto method that returns ToString() which you can edit to return the property value you want pinned in the debugger.
  • There is now a code fix for accidental assignments or comparisons to the same variable. Place your cursor on the warning. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. For accidental assignments, select Assign to

    .value. For accidental comparisons, select Compare to

    .value.

  • You can now generate comparison operators for types that implement IComparable. Place your cursor either inside the class or on IComparable. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Generate comparison operators. A boiler plate will be generated for you with the comparison operators.
  • You can now generate IEquatable operators when generating .Equals for structs. We already had a refactoring to Generate Equals and GetHashCode for value types. Now with structs we will automatically add the IEquatable as well as the equals and not equals operators for you. Place your cursor within the struct. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Generate Equals(object).
  • You can now create and assign properties or fields for all unused constructor parameters. We already had a quick action that allowed you to do this on an individual parameter, but now you can do it for all unused parameters at once. Place your cursor on any of the remaining parameters. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. To create and initialize properties, select Create and assign remaining as properties. To create and initialize fields, select Create and assign remaining as fields.
  • There is now IntelliSense completion in DateTime and TimeSpan string literals. Place your cursor inside the DateTime or TimeSpan string literal and press (Ctrl+Space). You will then see completion options and an explanation as to what each character means. Both the date time format and an example will be provided.
  • You can now add a parameter within the Change Signature dialog. Place your cursor within the method’s signature. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Change signature. The following dialog will open where you can now select Add to add a parameter. Once you select Add, the new Add Parameter dialog will open. The Add Parameter dialog allows you to add a type name and a parameter name. You can choose to make the parameter required or optional with a default value. You can then add a value at the call site and choose a named argument for that value or you can introduce a TODO variable. The TODO variable puts a TODO in your code so you can visit each error and go through each call site independently and decide what to pass. For optional parameters you have the option to omit the call site completely.
  • Analyzer authors can now use CompletionProviders for IntelliSense completions when shipping their analyzers with NuGet. Before, library authors would have to create a separate VSIX since CompletionProviders was only available in VSIX. Now library authors can implement IntelliSense completions in the NuGet package where their analyzers are, and they don’t need to do it separately. Completion providers implemented in NuGet packages will also provide suggestions specific to individual projects and will automatically work in each IDE supporting the feature.
Razor

Try out the new experimental Language Server Protocol (LSP) powered Razor editor with all Razor files (.cshtml/.razor) by selecting the Enable experimental Razor editor preview feature.

Test Explorer

Run/Debug All Tests In View have been added to the Test Explorer. These commands replace where the Run All Tests and Debug All Tests commands appeared in the Test Explorer. This change clarifies that these commands honor the filters of the Test Explorer so that only tests visible in window are run. This includes both column filters and search box filters.

The Global Run/Debug All commands will now only appear in the top-level Test menu. They are no longer included in the Test Explorer toolbar or context menu of any test window view. When triggered from the Test Explorer, the Analyze Code Coverage for All Tests now applies to the test window views as well.

Short-cut Keys:

  • Ctrl R, A – Run All Test – Global command always runs all tests
  • Ctrl R, V – Run All Tests In View – Only a valid command when a test window (Test Explorer, Playlist, Live Unit Testing Window) are active windows
  • Ctrl R, Ctrl A – Debug All Test – Global command always debugs all tests
  • Ctrl R, Ctrl V – Debug All Tests In View – Only a valid command when a test window (Test Explorer, Playlist, Live Unit Testing Window) are active windows
Debugger

Viewing Managed COM Objects Through Native Pointers

This feature automatically decodes managed COM objects referenced by native pointers allowing you to fully inspect values in the Locals window. You can find more details here at the Visual Studio blog.

Profiler

New .NET Performance Counters Tool

Visualize dotnet counters right from within the Visual Studio Profiler using the .NET Performance Counters Tool. To try out the tool go to Debug -> Performance Profiler -> Checkmark .NET Performance Counters Tool.

Xamarin
  • Code fixers have been introduced for the most common types of problems experienced by users with Android layout files.
  • The Xamarin.Forms template selection experience now has a fresh and more illustrative look, and the Flyout and Tabbed templates now utilize Shell. Read more about Shell here. If for some reason you don’t wish to use Shell, use the Blank template.
XAML Tools (WPF, UWP & Xamarin.Forms)

XAML Hot Reload:

  • In-app Toolbar Improvements: We have further refined the in-app toolbar experience that is part of the XAML Hot Reload tooling workflow for WPF & UWP. Changes include a shorter toolbar so that it no longer covers the running application, and a change in the collapse mechanism which when clicked will now collapse the XAML Hot Reload text first, then collapse the bar fully on the second click.

XAML Designer:

  • Expanded Design-time Data Support for WPF & UWP: In this release we are introducing a new design-time data feature for WPF .NET Core and UWP developers. This new capability will extend the current list of accessible design-time properties through the use of the d: prefix. This feature will be familiar to Xamarin.Forms developers, as it makes available the same approach of using a “d:” prefix to indicate a property that should only be rendered at design-time and never gets compiled into the running app making it very safe to use for design time UI validation. In this release we support all the out-of-the-box controls for WPF and UWP and plan to support 3rd party and custom controls in future releases.
  • XAML Designer Refresh Button: We have added a refresh button to the XAML designer, this new icon can be found in the bottom-left icon area near the zoom level indicator. This refresh action does the equivalent reset of closing the designer view and re-opening it for the rare situations where this is required to resolve a rendering issue. This feature is available for WPF .NET Core and UWP developers.

XAML Code Editor:

  • Color Visualizer: We have further refined our new color visualizer in the XAML code editor for WPF .NET Core, WPF .NET Framework and Xamarin.Froms projects. In this release we have added support for visualizing colors coming from resources, which was previously not supported in the last preview.

Show Toolbox items from a NuGet package without having a package reference

Many control library authors want their controls to be seen in the Toolbox even when the current project hasn’t referenced the library yet, as this helps with discoverability. WPF .NET Framework SDKs have historically accomplished this using registry entries, but this is not supported by .NET Core. For WPF .NET Core, Toolbox can now be populated with controls from VisualStudioToolsManifest.xml files found within WPF .NET Core NuGet packages in NuGet fallback folders. For more details, see the documentation in the XAML Designer Extensibility GitHub repo.

Windows Forms

Windows Forms Designer for .NET Core

The Windows Forms designer for .NET Core projects is now available. To enable the designer in Visual Studio, go to Tools > Options > Environment > Preview Features and select the Use the preview Windows Forms designer for .NET Core apps option.

In this release the following controls are now supported along with other improvements:

  • UserControl and custom controls infrastructure
  • TableLayoutPanel
  • Fundamentals for third-party controls support
  • Fundamentals for data binding support
  • Improvements in designer interaction with the TableLayoutPanel

Visual Studio 2019 version 16.11.3

released September 14, 2021

Issues Addressed in this Release

  • Fixed missing “Remote Device” debug target for Xamarin iOS projects.
  • Fixed a bug that caused a start menu shortcut link to disappear. The bug only happened when updating multiple instances of different product SKUs on the same machine.

From Developer Community

  • Visual Studio UI unresponsive when too much build log output during build (eg: diagnostic verbosity)
  • Live Unit Testing Crashes on start up
  • “Remote device” not listed in devices
  • Designer crashes for 32-bit apps whenever you scroll wheel over it

Security Advisories Addressed

CVE-2021-26434 Visual Studio Incorrect Permission Assignment Privilege Escalation Vulnerability

A permission assignment vulnerability exists in Visual Studio after installing the Game development with C++ and selecting the Unreal Engine Installer workload. The system is vulnerable to LPE during the installation it creates a directory with write access to all users.

Create Basic Reports Crystal Reports + Visual Studio 2019
Create Basic Reports Crystal Reports + Visual Studio 2019

Visual Studio 2019 version 16.0.14

released May 12, 2020

Issues fixed in 16.0.14

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

Security Advisory Notice for 16.0.14

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.

Visual Studio 2019 version 16.7.18

released August 10, 2021

In this Release of Visual Studio 2019 version 16.7.18

  • Fixed an issue that affected command line execution of the update command. If the update fails the first time, a subsequent issuing of the update command now causes the update to resume the prior operation where it left off.

Security Advisory Notice

CVE-2021-26423 .NET Core Denial of Service Vulnerability A denial of service vulnerability exists where .NET (Core) server applications providing WebSocket endpoints could be tricked into endlessly looping while trying to read a single WebSocket frame.

CVE-2021-34485 .NET Core Information Disclosure Vulnerability An information disclosure vulnerability exists when dumps created by the tool to collect crash dumps and dumps on demand are created with global read permissions on Linux and macOS.

CVE-2021-34532 ASP.NET Core Information Disclosure Vulnerability An information disclosure vulnerability exists in where a JWT token is logged if it cannot be parsed.

How to install RDLC Report Designer and Report Viewer in 5 min | Visual Studio 2019 | CODE ENGINEERS
How to install RDLC Report Designer and Report Viewer in 5 min | Visual Studio 2019 | CODE ENGINEERS

Visual Studio 2019 version 16.0.6

released July 9, 2019

Issues fixed in Visual Studio 2019 version 16.0.6

  • Fixed narrator support on systems running on Windows 10 version 1903 or with .NET 4.8 installed.

Security Advisory Notice

CVE-2019-1075 ASP.NET Core Spoofing Vulnerability

.NET Core updates have released today and are included in this Visual Studio update. This release addresses security and other important issues. Details can be found in the .NET Core release notes.

CVE-2019-1077 Visual Studio Extension Auto Update Vulnerability

An elevation of privilege vulnerability exists when the Visual Studio Extension auto-update process improperly performs certain file operations. An attacker who successfully exploited this vulnerability could delete files in arbitrary locations. To exploit this vulnerability, an attacker would require unprivileged access to a vulnerable system. The security update addresses the vulnerability by securing locations the Visual Studio Extension auto-update performs file operations in.

CVE-2019-1113 WorkflowDesigner XOML deserialization allows code execution

A XOML file referencing certain types could cause random code to be executed when the XOML file is opened in Visual Studio. There is now a restriction on what types are allowed to be used in XOML files. If a XOML file containing one of the newly unauthorized types is opened, a message is displayed explaining that the type is unauthorized.

For further information, please refer to https://support.microsoft.com/help/4512190/remote-code-execution-vulnerability-if-types-are-specified-in-xoml.

Visual Studio 2019 version 16.9.10

released August 10, 2021

Issues Addressed in this Release:

  • No longer send paths on disk when reporting which extensions are installed.
  • Fixed an IntelliSense crash that occurred when processing static data members in in-class template specializations.
  • Fixed an issue that affected command line execution of the update command. If the update fails the first time, a subsequent issuing of the update command now causes the update to resume the prior operation where it left off.

Security Advisory Notice

CVE-2021-26423 .NET Core Denial of Service Vulnerability

A denial of service vulnerability exists where .NET (Core) server applications providing WebSocket endpoints could be tricked into endlessly looping while trying to read a single WebSocket frame.

CVE-2021-34485 .NET Core Information Disclosure Vulnerability

An information disclosure vulnerability exists when dumps created by the tool to collect crash dumps and dumps on demand are created with global read permissions on Linux and macOS.

CVE-2021-34532 ASP.NET Core Information Disclosure Vulnerability

An information disclosure vulnerability exists in where a JWT token is logged if it cannot be parsed.

How to Uninstall Visual Studio 2017 / 2019 / 2022  in Window 10 or 11
How to Uninstall Visual Studio 2017 / 2019 / 2022 in Window 10 or 11

Visual Studio 2019 version 16.7.15

released May 11, 2021

In this Release of Visual Studio 2019 version 16.7.15

  • Fixed an issue causing updates to fail when an administrator creates a new layout of Visual Studio for deploying updates. The client machine update will fail since the layout has moved locations.

Security Advisory Notice

CVE-2021-27068 RCE possible when planting python.exe in nested folder A remote code execution vulnerability exists when opening a workspace with python code and that workspace contains a python.exe in a scripts subfolder.

CVE-2021-31204 .NET Core Elevation of Privilege Vulnerability An elevation of privilege vulnerability exists in .NET 5.0 and .NET Core 3.1 when a user runs a single file application on Operating Systems based on Linux or macOS.

Visual Studio 2019 version 16.0.12

released March 10, 2020

Issues fixed in 16.0.12

  • VS Preview 2019 vcruntime.h causes RC4011 warning
  • New Spectre mitigation options in C++ compiler: /Qspectre-load & /Qspectre-load-cf for speculative load hardening.

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

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.

Dependency Injection in .NET Core (.NET 6)
Dependency Injection in .NET Core (.NET 6)

Still want an older version?

Select a product below and click on the download button to log in to your Visual Studio (MSDN) subscription or join the free Dev Essentials program, to gain access to the older versions.

Visual Studio 2019 and other Products

To download any product from the following list, click the download button and log in with your Visual Studio Subscription account when prompted. If you don’t have a Visual Studio Subscription, you can create one for free by clicking on “Create a new Microsoft account” on the login page.

Visual Studio Professional 2019; Visual Studio Enterprise 2019;

Visual Studio 2019 for Mac

Build Tools for Visual Studio 2019

Visual Studio Team Explorer 2019

Agents for Visual Studio 2019

IntelliTrace Standalone Collector for Visual Studio 2019

Performance Tools for Visual Studio 2019

Remote Tools for Visual Studio 2019

Microsoft Visual C++ Redistributable for Visual Studio 2019

Visual Studio 2017 and other Products

To download any product from the following list, click the download button and log in with your Visual Studio Subscription account when prompted. If you don’t have a Visual Studio Subscription, you can create one for free by clicking on “Create a new Microsoft account” on the login page.

Visual Studio Professional 2017; Visual Studio Enterprise 2017;

Visual Studio 2017 for Mac

Visual Studio Test Professional 2017

Build Tools for Visual Studio 2017

Visual Studio Team Explorer 2017

Agents for Visual Studio 2017

Feedback Client for Visual Studio 2017

IntelliTrace Standalone Collector for Visual Studio 2017

Performance Tools for Visual Studio 2017

Remote Tools for Visual Studio 2017

Visual Studio 2015 and other Products

To download any product from the following list, click the download button and log in with your Visual Studio Subscription account when prompted. If you don’t have a Visual Studio Subscription, you can create one for free by clicking on “Create a new Microsoft account” on the login page.

Visual Studio Professional 2015; Visual Studio Enterprise 2015;

Visual Studio Test Professional 2015

Visual C++ Build Tools for Visual Studio 2015; Microsoft Visual Build Tools for Visual Studio 2015

Visual Studio 2015 Language Pack

Visual Studio Test Professional 2015 Language Pack

Visual Studio Team Foundation Server 2015

Visual Studio Team Foundation Server Express 2015

Visual Studio Team Foundation Server Office Integration 2015

Visual Studio 2015 SDK

Agents for Visual Studio 2015

Modeling SDK for Visual Studio 2015

Remote Tools for Visual Studio 2015

Release Management for Visual Studio 2015

Visual Studio 2013 and Other Products

To download any product from the following list, click the download button and log in with your Visual Studio Subscription account when prompted. If you don’t have a Visual Studio Subscription, you can create one for free by clicking on “Create a new Microsoft account” on the login page.

Visual Studio Professional 2013; Visual Studio Premium 2013; Visual Studio Ultimate 2013

Visual Studio Test Professional 2013

Visual Studio 2013 Language Pack

Visual Studio Test Professional 2013 Language Pack

Visual Studio Team Foundation Server 2013

Visual Studio Team Foundation Server Express 2013

Team Explorer for Visual Studio 2013

Visual Studio 2013 SDK

Visual Studio 2013 Modeling SDK

Visual Studio 2013 Agents

Visual Studio Express 2013 for Web

Visual Studio Express 2013 for Windows

Visual Studio Express 2013 for Windows Desktop

Microsoft Visual C++ Redistributable for Visual Studio 2017

This package installs run-time components of Visual C++ libraries and can be used to run such applications on a computer even if it does not have Visual Studio 2017 installed.

Right-click on the following link to copy or bookmark this download: Microsoft Visual C++ Redistributable for Visual Studio 2017

Microsoft Visual C++ 2015 Redistributable Update 3

Install run-time components of Visual C++ libraries that are required to run C++ applications. Microsoft Visual C++ 2015 Redistributable includes bug fixes to the runtime DLLs and also the latest versions for KB 2999226.

Right-click on the following link to copy or bookmark this download: Microsoft Visual C++ 2015 Redistributable Update 3

Visual Studio 2019 v16.11 is Available Now!

We are excited to announce the release of Visual Studio 2019 v16.11 GA. This release improves upon the Git tooling experience in Visual Studio, enables Hot Reload for .NET applications, adds convenient links to the help menu, and upgrades LLVM tools to LLVM 12. For full details, see the Visual Studio 2019 release notes.

Visual Studio 2019 version 16.11.25

released March 14th, 2023

Issues Addressed in this release

  • Git 2.39 has renamed the value for credential.helper from “manager-core” to “manager”. See https://aka.ms/gcm/rename for more information.
  • Updates to mingit and Git for Windows package to v2.39.2, which addresses CVE-2023-22490

Security Advisories Addressed

  • CVE-2023-22490 Mingit Remote Code Execution Vulnerability
  • CVE-2023-22743 Git for Windows Installer Elevation of Privilege Vulnerability
  • CVE-2023-23618 Git for Windows Remote Code Execution Vulnerability
  • CVE-2023-23946 Mingit Remote Code Execution Vulnerability
Visual Studio 2019 (Getting Started)
Visual Studio 2019 (Getting Started)

Visual Studio 2019 version 16.9.24

released August 9, 2022

Issues Addressed in this release:

  • Updates Git for Windows to v2.37.1.1 addressing CVE-2022-31012.

Security Advisory Notice

  • CVE-2022-34716 .NET Information Disclosure Vulnerability An information disclosure vulnerability exists in .NET 6.0 and .NET Core 3.1 that could lead to unauthorized access of privileged information.
  • CVE-2022-31012 Remote Code Execution Git for Windows’ installer can be tricked into executing an untrusted binary
  • CVE-2022-29187 Elevation of Privilege Malicious users can create a .git directory in a folder that is owned by a super-user
  • CVE-2022-35777 Remote Code Execution Visual Studio 2022 Preview Fbx File parser Heap overflow Vulnerability
  • CVE-2022-35825 Remote Code Execution Visual Studio 2022 Preview Fbx File parser OOBW Vulnerability
  • CVE-2022-35826 Remote Code Execution Visual Studio 2022 Preview Fbx File parser Heap overflow Vulnerability
  • CVE-2022-35827 Remote Code Execution Visual Studio 2022 Preview Fbx File parser Heap OOBW Vulnerability

Wondering which tool is best for you? We can help

Visual Studio Code for Mac

Highlights

  • Free code editor
  • Built on open source and runs everywhere
  • Hundreds of programming languages supported

  • Add on the C# DevKit for Visual Studio Code

Visual Studio Code for Windows

Lightweight yet powerful source code editor with tons of
extensions for many languages and runtimes.Download Visual Studio Code

Highlights

  • Free code editor
  • Built on open source and runs everywhere
  • Hundreds of programming languages supported

Visual Studio Code for Mac

Highlights

  • Free code editor
  • Built on open source and runs everywhere
  • Hundreds of programming languages supported

Visual Studio Code for Linux

Highlights

  • Free code editor
  • Built on open source. Runs everywhere
  • Hundreds of programming languages supported

Visual Studio for Windows

A complete array of development tools and features in one
place to elevate and enhance every stage of your
software development.How to install offline Compare editions

Highlights

  • Free for individual use
  • Code faster, test, debug, deploy any app from one place
  • Visual Studio built-in features empower full development cycle.

Visual Studio 2019 winform designer toolbox empty problem!
Visual Studio 2019 winform designer toolbox empty problem!

Visual Studio 2019 version 16.7.23

released December 14, 2021

In this Release of Visual Studio 2019 version 16.7.23

  • Added Python 3.9.7 to Python workload. Removed Python 3.7.8 due to a security vulnerability.

Security Advisory Notice

CVE-2021-43877 Vulnerability An elevation of privilege vulnerability exists in ANCM which could allow elevation of privilege when .NET core, .NET 5 and .NET 6 applications are hosted within IIS.

Visual Studio 2019 version 16.7.19

released September 14, 2021

In this Release of Visual Studio 2019 version 16.7.19

Security Advisory Notice

CVE-2021-26434 Visual Studio Incorrect Permission Assignment Privilege Escalation Vulnerability A permission assignment vulnerability exists in Visual Studio after installing the Game development with C++ and selecting the Unreal Engine Installer workload. The system is vulnerable to LPE during the installation it creates a directory with write access to all users.

CVE-2021-36952 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.

How To Install Visual Studio 2019 (for Free)
How To Install Visual Studio 2019 (for Free)

Visual Studio 2019 version 16.0.18

released September 8, 2020

Issue fixed in 16.0.18

  • Out of support versions of .NET Core will no longer be reinstalled during a repair or upgrade if they were removed outside of VS setup.

Security Advisory Notice for 16.0.18

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.

Visual Studio 2019 version 16.7.7

released October 27, 2020

In this Release of Visual Studio 2019 version 16.7.7

  • Added Xcode 12.1 GM support.
  • Update of MSVC 14.16, 14.20, 14.24, and 14.26 toolsets to match latest servicing releases.
  • Fixed a bug that caused a crash when renaming a type and file currently not open in the editor.
Installing Visual Studio 2019 on Windows 10
Installing Visual Studio 2019 on Windows 10

Visual Studio 2019 version 16.9.26

released October 11, 2022

Issues Addressed in this release:

  • Administrators will be able to update the VS Installer on an offline client machine from a layout without updating VS.

Security Advisory Notice

  • CVE-2022-41032 .NET Elevation of Privilege Vulnerability A vulnerability exists in .NET 7.0.0-rc.1, .NET 6.0, .NET Core 3.1, and NuGet clients (NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.Protocol) where a malicious actor could cause a user to execute arbitrary code.

Visual Studio 2019 version 16.0.11

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.

How to Download And Install Visual Studio 2019 in Windows 10
How to Download And Install Visual Studio 2019 in Windows 10

Visual Studio 2019 version 16.0.1

released April 09, 2019

Issues fixed in Visual Studio 2019 version 16.0.1

  • Add option for Windows (UWP) platform when creating new Xamarin.Forms project from ‘Mobile App (Xamarin.Forms)’ project template.
  • Help > About window title in Visual Studio 2019 still shows ‘RC’ after upgrade.
  • When updating Visual Studio 2019 from RC to GA, RC shortcuts for Visual Studio are left behind.
  • Visual Studio 2019 Preview 1.1 cannot create a UWP xamarin form.
  • Package load failure starting Visual Studio 2019 after upgrade from Preview 4.4 to 16.0.

Visual Studio 2019 version 16.11.11

released March 8, 2022

Issues Addressed in this release

  • Fixed an issue with remote debugging, especially affecting Azure App Service, where authentication failures would sometimes fail with ‘The connection with the remote endpoint was terminated’ and Visual Studio would not prompt for credentials.
  • Improved performance on high refresh rate monitors.

From Developer Community

  • Internal compiler error in fold expression with += operator on 16.11
  • consteval constructor and C7595
  • cl does not make special member functions implicitly constexpr
  • Can’t have freestanding requires expressions
  • There are no configured extension galleries in VS 2019
  • Sql Server object explorer does not show indexes
  • SQL project does not build if it has File storage tables

Security Advisories Addressed

CVE-2020-8927 Vulnerability A Remote code Execution vulnerability exists in .NET 5.0 and .NET Core 3.1 where a buffer overflow exists in the Brotli library versions prior to 1.0.8.

CVE-2022-24464 Vulnerability A denial of service vulnerability exists in .NET 6.0, .NET 5.0, and .NET CORE 3.1 when parsing certain types of http form requests.

CVE-2022-24512 Vulnerability A Remote Code Execution vulnerability exists in .NET 6.0, .NET 5.0, and .NET Core 3.1 where a stack buffer overrun occurs in .NET Double Parse routine.

CVE-2021-3711 OpenSSL Buffer Overflow vulnerability A potential buffer overflow vulnerability exists in OpenSSL, which is consumed by Git for Windows. Git for Windows is now updated to version 2.35.1.2, which addresses this issue.

Su dung Visual Studio 2019
Su dung Visual Studio 2019

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.

Have you tried the latest Visual Studio?

Try the latest 64-bit Visual Studio 2022 to create your ideal IDE, build smarter apps, integrate with the cloud, optimize for performance, and stay ahead of the curve

Check out what’s new in Visual Studio 2022

Visual Studio 2019 version 16.11.24

released February 14th, 2023

Issues Addressed in this release

  • Updated CPython interpreter to version 3.9.13.
  • Updated mingit and Git for Windows package to v2.39.1.1, which addresses CVE-2022-41903

Security Advisories Addressed

  • CVE-2023-21566 Visual Studio Installer Elevation of Privilege Vulnerability
  • CVE-2023-21567 Visual Studio Denial of Service Vulnerability
  • CVE-2023-21808 .NET and Visual Studio Remote Code Execution Vulnerability
  • CVE-2023-21815 Visual Studio Remote Code Execution Vulnerability
  • CVE-2023-23381 Visual Studio Code Remote Code Execution Vulnerability
  • CVE-2022-23521 gitattributes parsing integer overflow
  • CVE-2022-41903 Heap overflow in

    git archive

    ,

    git log --format

    leading to RCE
  • CVE-2022-41953 Git GUI Clone Remote Code Execution Vulnerability
Visual Studio 2019 Preview Update Version 16.0.0 Preview 2.1
Visual Studio 2019 Preview Update Version 16.0.0 Preview 2.1

Visual Studio 2019 version 16.9.0

released March 02, 2021

Summary of What’s New in this Release of Visual Studio 2019 version 16.9.0

C++

  • Address Sanitizer:

    • Our address sanitizer support on Windows is now out of experimental and has hit general availability.
    • Expanded RtlAllocateHeap support, fixed a compatibility issue with RtlCreateHeap and RtlAllocateHeap interceptors when creating executable memory pools.
    • Added support for the legacy GlobalAlloc and LocalAlloc family of memory functions. You can enable these interceptors with

      ASAN_OPTIONS=windows_hook_legacy_allocators=true

      .
    • Updated error messages for shadow memory interleaving and interception failure to make problems and resolutions explicit.
    • The IDE integration can now handle the complete collection of exceptions which ASan can report.
    • The compiler and linker will suggest emitting debug information if they detect you’re building with ASan but not emitting debug information
  • You can now target the LLVM version of the OpenMP runtime with the new CL switch /openmp:llvm. This adds support for the lastprivate clause on #pragma omp sections and unsigned index variables in parallel for loops. The /openmp:llvm switch is currently only available for the amd64 target and is still experimental.
  • Visual Studio CMake projects now have first class support for remote Windows development. This includes configuring a CMake project to target Windows ARM64, deploying the project to a remote Windows machine, and debugging the project on a remote Windows machine from Visual Studio.
  • The version of Ninja shipped with Visual Studio on Windows has been updated to version 1.10. Please see the Ninja 1.10 release notes for details on what is included.
  • The version of CMake shipped with Visual Studio has been updated to version 3.19. Please see the CMake 3.19 release notes for details on what is included.
  • Marked many lock/guard types in the STL as nodiscard: https://github.com/microsoft/STL/pull/1495
  • IntelliSense:

    • Improved the stability and functionality of providing imported modules and header units completion in IntelliSense.
    • Added Go-to-definition on module imports, indexing support for export { … }, and more accurate module reference for modules with the same name.
    • Improved the language compliance of C++ IntelliSense by adding support for Copy-initialization of temporary in reference direct-initialization, __builtin_memcpy and __builtin_memmove, Fixing inconsistencies between constexpr and consteval functions, Lifetime-extended temporaries in constant expressions, and Similar types and reference binding.
    • Added completion for make_unique, make_shared, emplace and emplace_back which provides completion based on the type parameter specified.
  • MSVC now determines the correct address sanitizer runtimes required for your binaries. Your Visual Studio project will automatically get the new changes. When using address sanitizer on the command line, you now only need to pass /fsanitize=address to the compiler.
  • Visual Studio’s Connection Manager now supports private keys using the ECDSA public key algorithm.
  • Updated the versions of LLVM and Clang shipped in our installer to v11. Read the release notes for LLVM and Clang for more information.
  • Visual Studio will now use CMake variables from toolchain files to configure IntelliSense. This will provide a better experience for embedded and Android development.
  • Implementation of the More Constexpr Containers proposal, which allows destructors and new expressions to be constexpr. This paves the way for utilities like constexpr std::vector and std::string.
  • Extended support for C++20 modules IntelliSense, including Go To Definition, Go To Module, and member completion.
  • Abbreviated function templates are now supported in the MSVC compiler.

Javascript/TypeScript

  • There is now support for Edge Chromium based WebView2 JavaScript/TypeScript debugging for applications such as WPF, WinForms and WinUI 3 projects. This can be enabled by selecting the JavaScript debugger from the Project Properties dialog box. Details on how to get started to can be found here

Debugger

  • Added a new Auto Analyzer that inspects threads for deadlocks.
  • Added a new Auto Analyzer that inspects the .NET Core Finalizer queue and detects potentially blocking objects.
  • Visual Studio now filters out redundant repeating frames from the call stack when the debugger stops on a StackOverflow Exception. It is now possible to see the base of the stack where an infinite recursion originated, which hopefully makes it easier to investigate these kinds of bugs.

Profiler

  • Added new dynamic instrumentation scenario that is faster (doesn’t require VSInstr) and allows .NET Core applications to be instrumented without needing PDBs.

F# and F# tools

This release has several productivity features and performance improvements for the F# tools for Visual Studio:

  • .NET Core FSI support
  • Signature Help for function applications
  • 14 new quick fixes
  • Significant performance and responsiveness fixes for F# Tooling

You can read about them in F# and F# tools update for Visual Studio 16.9 or the product release notes.

  • There is now IntelliSense completion for preprocessor symbols.
  • Solution Explorer now displays the new .NET 5.0 Source Generators.
  • Go To All won’t display duplicate results across netcoreapp3.1 and netcoreapp2.0.
  • Quick Info now displays compiler warning IDs or numbers for suppressions.
  • Using directives will now automatically get added when copying and pasting types to a new file.
  • When pressing to accept a method from a completion list, IntelliSense will now automatically insert the parentheses along with a semicolon for object creation and method calls.
  • Semantic colorization for C# 9.0 records.
  • Refactoring that removes unnecessary discards.
  • Refactoring that converts a verbatim and regular string to an interpolated string preserving curly braces that were intended to go in the output.
  • Code fix in Visual Basic that removes the shared keyword when you convert methods that are shared to a module.
  • A refactoring that suggests using

    new(…)

    in non-contentious scenarios
  • A code fix that removes redundant equality expressions for both C# and Visual Basic
  • The .NET Code Style (IDE) analyzers can now be enforced on build
  • The Syntax Visualizer shows the current foreground color for enhanced colors
  • A new tooltip when hovering over the diagnostic ID for pragma warnings
  • When you type the return key from within a comment the new line is now automatically commented out
  • Inline parameter name hints enhancements
  • .NET Core Debugging with WSL 2

Test Explorer audio cues and accessibility updates

  • You can now configure audio cues with the Test Explorer, the Group By menu is more accessible for screen readers, and viewing long test output is easier with clickable links opening log files directly.

Experimental Razor Editor Updates

  • HTML and C# semantic colorization
  • Renames of C# symbols reflected in closed Razor files
  • More C# light bulbs in Razor files
  • Further improvements to mixed content formatting in Razor files
  • Deploy your Steeltoe applications to Azure Spring Cloud using Visual Studio Publish (e.g. right-click > Publish in Solution Explorer).
  • Enhanced .NET support for Azure App Configuration as a Connected Service
  • Manage your application’s configuration settings and feature flags by integrating Azure App Configuration as a Connected Service

XAML Tools (WPF, WinUI, UWP & Xamarin.Forms)

MVVM Tooling

  • Improved MVVM Support: In this release, we have introduced Lightbulbs in the XAML Editor to generate properties and commands in available view-models. We have also added Lightbulbs to help set the design DataContext in XAML to available view-models to improve binding IntelliSense.

Xamarin.Forms

In this release we’ve made multiple improvements for Xamarin.Forms developers:

  • XAML Hot Reload “changes only” mode is now the default for Xamarin.Forms 5.x projects: Starting with Visual Studio 16.9 XAML Hot Reload “changes only” mode is now the default XAML Hot Reload experience for projects targeting Xamarin.Forms 5.x or higher. Projects targeting 4.x will automatically fallback to “full page” XAML Hot Reload as “changes only” is only compatible with Xamarin.Forms 5.x or newer. If you are using Xamarin.Forms 5.x and wish to use the old “full page” Hot Reload mode for some reason, you can do so by going to Hot Reload settings under Tools > Options > Debugging > Hot Reload.

  • XAML Hot Reload status updates in output window: Xamarin.Forms customers using XAML Hot Reload can now see more details on what is happening with the XAML Hot Reload pipeline using the output window. To get started, open the output window with View > Output and select Xamarin Hot Reload under Show output from at the top of the window.

  • Xamarin.Forms + UWP – resolved System.ExecutionEngineException: Starting with the release of Visual Studio 2019 version 16.8 we inadvertently introduced a runtime exception that would trigger System.ExecutionEngineException errors when developers would be debugging Xamarin.Forms app that target Windows (UWP). Starting with this release (16.9 Preview 4) and in combination with an update to Microsoft.NETCore.UniversalWindowsPlatform NuGet (version 6.2.12+) this issue should now be resolved. Note: This fix is not only for Visual Studio 2019 version 16.9. Updating your projects to use the new NuGet package should resolve this issue for Visual Studio version 16.9 as well.

Tools for Unity

  • View root game objects while debugging in the new Active Scene node of the Locals window.
  • View all the components on a GameObject while debugging in the new this.gameObject node of the Locals window.
  • View all children game objects and components using the Children and Components nodes of the Locals window.
  • See the location of a GameObject in the scene when inspecting in the Active Scene property.
  • Support for JobEntityBatch/Lambdas when using Entities with source generators.
  • Improved support for displaying large arrays using index bucketing.
  • Syntax highlighting for raytrace shaders, UXML and USS files.
  • Visual Studio will now detect which components are missing and prompt you to install them when using Unity projects.
  • Unity messages API for all methods used as coroutines updated.
  • We’ve refreshed the Preview Feature flag for the new Git UX with a built-in Give Feedback link that directs you straight to the product team.
  • Team Explorer Home and Connect pages show detailed content to transition to the new Git UX.
  • Support for custom remotes in branch push notifications.
  • Double click a branch in the Git Repository window to checkout.
  • Commit changes with the keyboard shortcut Ctrl+Enter.
  • Push all tags from the Git Changes window.
  • The Visual Studio Installer no longer elevates on launch
  • The Visual Studio Installer now supports HDR displays
  • The Visual Studio Installer supports the Navigator screen reader
  • Installer updates have been streamlined into the Visual Studio update
  • The Visual Studio Installer adds dark theme support

Details of What’s New in Visual Studio 2019 version 16.9.0

Git Productivity
  • Commit changes with the keyboard shortcut Ctrl+Enter
  • Push all tags from the Git Changes window.
.NET Productivity
  • .NET Core Debugging with WSL 2 lets you run and debug your .NET Core console and web applications in WSL 2 from Visual Studio. This allows Windows developers targeting Linux production environments to have a higher fidelity local debugging experience.
  • There is now a refactoring that suggests using

    new(…)

    in non-contentious scenarios. Place your cursor on the field declaration. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Use ‘new(…)’.
  • There is now a code fix that removes redundant equality expressions for both C# and Visual Basic. Place your cursor on the redundant equality expression. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Remove redundant equality.
  • The .NET Code Style (IDE) analyzers can now be enforced on build. You can either install the .NET Code Style analyzers as a NuGet package for C# and Visual Basic or you can enable them in Project Properties. To access the Project Properties right-click on a project within Solution Explorer and select Properties. Next, select the Code Analysis tab where you can select Enforce CodeStyle on build (experimental).
  • The Syntax Visualizer (installed with the .NET Compiler Platform SDK) now shows the current foreground color for enhanced colors. Simply use the visualizer to navigate to the text you want to change colors for, or select in the editor, and then click on the classified color to change it.
  • There is now a tooltip when hovering over the diagnostic ID for pragma warnings. The diagnostic tooltip also has a clickable link that navigates to the documentation.
  • When you type the return key from within a comment you may notice that the new line is now automatically commented out. This is a new option that is on by default. To prevent the new line from automatically being commented out, go to Tools > Options > Text Editor > C# or Basic > Advanced and uncheck Insert // at the start of new lines when writing // comments.

In 16.8 Preview 2 we added inline parameter name hints that inserts adornments for literals, casted literals, and object instantiations prior to each argument in function calls. In this release we added the following enhancements:

  • More customization options for the types of adornments you would like inserted.

  • Inline type hints for variables with inferred types and lambda parameter types.

  • An option to disable inline parameter name hints when parameter names match the method’s intent and when parameter names differ only by suffix.

  • Using directives will now automatically get added when copying and pasting types to a new file. You will first need to turn this option on in Tools > Options > Text Editor > C# or Basic > Advanced and select Add missing using directives on paste.

  • When pressing to accept a method from a completion list, IntelliSense will now automatically insert the parentheses along with a semicolon for object creation and method calls.
  • There is now semantic colorization for C# 9.0 records. You can customize colors in Tools > Options > Environment > Fonts and Colors. In Display items scroll to User Types – Records and select the color that you would like to apply to records.
  • In C# 9.0 discards are unnecessary in certain pattern matching cases. We now fade unnecessary discards and offer a code fix to remove them. Place your cursor on the faded discard. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Remove unnecessary discard.
  • There is now a refactoring that converts a verbatim string and a regular string to an interpolated string that will preserve curly braces that were intended to go in the output. This refactoring is not offered if the string is assigned to a constant. Place your cursor on the string. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu. Select Convert to interpolated string.
  • There is now a code fix in Visual Basic that removes the shared keyword when you convert methods that are shared to a module.

  • There is now IntelliSense completion for preprocessor symbols. Start typing the


    #if

    directive to see the new completion options for symbols that are currently defined in scope.

  • Solution Explorer now displays the new .NET 5.0 Source Generators underneath the Analyzer node so you can easily navigate and view the generated code.
  • The Go To All window will not display duplicate results across netcoreapp3.1 and netcoreapp2.0 as well as results for partial types that exist only to wrap another nested type. This will help declutter the results so you can easily find and navigate to code. The results also now include the filename for partial symbols.
  • Quick Info now displays compiler warning IDs or numbers for suppressions. Hover your cursor over the warning IDs or numbers to view Quick Info for the diagnostic ID.
Thank You

Last but certainly not least, a big Thank You to the following people who contributed this month to .NET Productivity (a.k.a. Roslyn):

  • Youssef Victor (@Youssef1313):
  • Martin Strecker (@MaStr11):
  • Joseph Musser (@jnm2):
  • Huo Yaoyuan (@huoyaoyuan):
  • Jon Senchyna (@TheSench): Feature to disambiguate

    using

    keyword PR #48898
  • Mathias Lykkegaard Lorenzen (@ffMathy): Increase maximum suggestions to 5 PR #49687
  • Alireza Habibi (@alrz): Generate explicit cast for implicit conversions in the

    use pattern matching

    codefix PR #49757
  • Raf (Raffaele Rialdi) (@raffaeler): Added support to normalize auto properties on a single line PR #49495
  • Youssef Victor (@Youssef1313):

    • Implemented Visual Basic code fix to remove Shared from module members PR #48289
    • Support init accessor in CSharpSyntaxFacts PR #48137
    • Raised the default WarningLevel to latest in tests PR #47077
    • Remove unnecessary suppression PR #48277
    • Extract Method refactoring to work with records PR #48531
    • Fix WarningLevel for hidden diagnostics PR #48397
    • Fix target-typed new bug with Find All References counting PR #48434
    • Property parsing when it contains paretheses PR #48598
    • Fix InvalidCastException when exception filter contains a switch expression PR #48260
  • Louis Zanella (@louis-z): Implemented refactoring that converts regular and verbatim strings to an interpolated string that preserve curly braces PR #48502
  • Shimmy (@weitzhandler): Default Constructor suggestion between members PR #48503
  • Kai Jellinghaus (@HurricanKai: Make GreenNode.CreateList static and adjusts all usages PR #48536
  • Jon Senchyna (@TheSench):
  • Petr Onderka (@svick): Fixed documentation comment ID handling for dynamic and tuples PR #48359
  • Huo Yaoyuan (@huoyaoyuan):
  • Rastislav Novotny (@duracellko): Support NotNullIfNotNull in binary operators PR #48490
  • Alireza Habibi (@alrz): Fix nullable type pattern parsing for better error recovery PR #48447
  • Lingling Tong (@LinglingTong): Enable LSP pull model diagnostic for XAML PR #49145
  • David Maas (@PathogenDavid): Fix module-level SkipLocalsInit with top-level statements PR #49435
  • Martin Strecker (@MaStr11): Support warning numbers in Quick Info for suppressions PR #49102
  • Adam Speight (@AdamSpeight2008): Perfomance improvement PR #49459
  • Adam Ralph (@adamralph): Fix invalid code snippet in adding optional parameters to public methods PR #48725
.NET Web Tools
  • Deploy your Steeltoe applications to Azure Spring Cloud using Visual Studio Publish (e.g. right-click > Publish in Solution Explorer). If you are not seeing the option, make sure your project includes the NuGet package Microsoft.Azure.SpringCloud.Client version 1.0.0-preview.1 or later.
Web Tools

Adding App Configuration as a connected service automatically connects your application to your Azure App Configuration Resource. There is now support for generating code automatically for .NET Core Console projects, as well as adding NuGet packages automatically for .NET Framework projects. To integrate this Connected Service into your app, click on Connected Services and add Azure App Configuration as a Service Dependency.

  • The Connected Services tab now supports Azure App Configuration. App Configuration lets you centrally manage application settings and feature flags. When you add this service dependency, your code is automatically updated to connect to your App Configuration resource. This includes installing the most up to date NuGet Packages and storing your secrets locally or in Key Vault.
Visual Studio Installer

The Visual Studio installer has incorporated several new features in response to customer requests.

Many users now use the installer to identify, launch, and manage multiple copies of Visual Studio. To aid this use pattern, the Visual Studio installer no longer requires elevation on launch and only requires elevation to make changes to Visual Studio and the machine. Other activities, like exporting install configurations, navigating news, and viewing update details no longer require the user to elevate first.

Earlier versions of the installer would occasionally ask users to take an additional step to update the installer. With this update, required installer updates are now handled as part of the installation operation, removing the extra step.

The installer now adds a dark mode theme selection. Users can changing the theme of the installer via the sun / moon (☼ / ☽) button in the title bar. Updates started from within the Visual Studio IDE will use the current theme selection of Visual Studio.

Test Explorer audio cues and accessibility updates
  • The Test Explorer can now play a sound when a test run completes. You can select two sounds, one for indicating the test run succeeded with all passing tests and a second sound to indicate the test run completed with at least one failing test. This feature started as a user request and improves the accessibility of the Test Explorer by adding an audio cue which is useful for developers who have a visual impairment. The sound selection uses the default Windows 10 sound dialog where you can also select from the preset sounds or any audio file from your computer!
  • The Group By in the Test Explorer is now more accessible using more concise phrases and word order when read by a screen reader.
  • Viewing long test output from the test details pane in the Test Explorer is now easier with a link to open the log file directly instead of the special document control.
Test Experience
  • Added support for collecting code coverage for .NET Core test projects that use Fakes.
  • Reduced time needed to merge multiple code coverage reports.
IntelliCode
  • IntelliCode now provides repeated edit suggestions directly within the IntelliSense completions list. You can view the Preview of the suggested change, apply at that location or ignore suggestions like these directly from the completion item. Learn more about IntelliCode suggestions.
Experimental Razor Editor Updates
  • HTML and C# semantic colorization
  • Renames of C# symbols reflected in closed Razor files
  • More C# light bulbs in Razor files:

    • Add

      DebuggerDisplay

      attribute
    • Create and assign property
    • Create and assign field
    • Implement interface or abstract class, including support for “with pattern”, i.e. “Implement interface with Dispose pattern”
    • Generate Equals, Hashcode, Constructor
  • Add
  • Add null check & Add all null checks for parameters
  • Further improvements to mixed content formatting in Razor files

To enable the experimental Razor editor, go to Tools > Options > Environment > Preview Features, select Enable experimental Razor editor, and then restart Visual Studio.

From Developer Community

Developer Community has a complete list of all of items shipping in this release.

Here are some of the top voted issues released in 16.9.0:

  • “Quick find” dialog opens in other tab group (left) other than current file in current tab group at right
  • Case sensitivity when parsing months
  • Cannot compile WPF applications targeting .NET 5
  • VisualStudio 16.6.5 crashes after continuing an “edit and continue” operation while debugging
  • Javascript editor syntax/intellisense highlighting bug
  • Start without debugging does not work on MSBuild Linux projects
  • SoftDebuggerSession.cs – Object reference not set at line 1612
  • MSVC 16.7 incorrectly throwing C2355 for use of this pointer on initialization for in class non-static member
  • Since Xamarin Update to V16.7, Build is Cluttered with Warnings
  • Disabling IntelliCode 2.2.733.31896 breaks TypeScript 3.x with a CompositionFailedException when editing a .ts file
  • “Value cannot be null. Parameter name: hierachy”.
  • Typescript intellisense keeps stopping
  • Getting address of inherited member function published with using-declaration fails with C2448
  • The ClickOnce Publish Wizard for .NET Core 3.1 and .NET 5.0 in Visual Studio 2019 16.8 does not generate deployment publish.htm
  • After 16.8 update getting lot of code analysis errors despite certain rules set to warning
  • Incorrect Code Gen / Missing Error
  • Internal compiler error VS 16.7.0
  • 16.7 regression auto constexpr with deduced array #include using std::array; void f() { using A1 = array; auto const v1 = array{
  • Module with partition won’t compile
  • Source Control “Cannot start an operation to change files behind the solution when Build or Debug is in progress” in 16.7.4
  • Regression: c++ internal compiler error in 16.7.0 with /std:c++17 (compiler file ‘msc1.cpp’, line 1591)
  • VS2019 still wipes CMakeBuild directory each time I touch CMakeFiles.txt or CMakeSettings.json
  • Visual Studio 16.8.0 disappears when starting to create a method
  • File isn’t saved after change
  • List initialization of an array with static_cast fails to compile in a constexpr function with VS2019 16.8.0 prevew 1
  • Bug in compiling std with clan clang-cl in latest VS
  • [MSConnect 3093410] std::get_time fails when using formats without separators
  • IntelliSense stops working when using Coroutines-TS with ASIO.
  • IntelliSense stops working when using Coroutines-TS with ASIO.
  • Visual Studio forces the user to use its High Contrast theme when Windows is in High Contrast mode.
  • Visual Studio 2019 produces incorrect code when using an infinite loop construct with explicit continue and break statements.
  • “Validation (CSS 4.0) warnings appear with no option to change to CSS 3.0 validation
  • Intellisense: scss map reports unexpected character sequence
  • Diagnostic Tools pane is blank/corrupted in VS 2019
  • VS for Linux: Build cancel (Ctrl+Break) Not work on complex solutions! VS not closable!
  • A git merge and not commit operation bug
  • Adding a new Report (.rdl) fails with error “Member not found 0x80020003 DISP_E_MEMBERNOTFOUND”
  • Modules and chaiscript: internal compiler error
  • Remote linux debug path broken with shared project reference
  • Task Runner Explorer Broken in 16.8
  • c2833 with operator decltype
  • Default VB.Net Core WinForms Project gets error creating Settings.
  • Microsoft Azure Tools: Method not found: ‘Void Microsoft.WindowsAzure.ServiceModel.Service.set_IsSLBPartialGS(Microsoft.WindowsAzure.ServiceModel.Expr
  • __is_nothrow_constructible intrinsic ignores potentially-throwing argument conversions
  • You can not choose /permissive in “Conformance mode”
  • Linux link fails with project reference
  • Visual Studio forces the user to use its High Contrast theme when Windows is in High Contrast mode
  • After 16.8 update getting lot of code analysis errors despite certain rules set to warning
  • A .NET Core 3.1 or .NET 5.0 application installed by ClickOnce may fail to start after being installed.
  • C33005 false positive with _variant_t
  • Git merge and commit operation bug
  • Unable to view Task or parallel stacks information with net5.0-windows* TFM
  • Clicking update on SQL Schema Compare does not save changes to sqlproj file
  • Database Project: Dragging a file from solution explorer into an opened one is deleting the file from the file system!
  • Intellicode model training fails on Visual Studio 2019
  • Open LiveShare collaboration sessions fail

Visual Studio 2019 version 16.0.22

released January 12, 2020

Security Advisory Notice for 16.0.22

CVE-2021-1651 / CVE-2021-1680 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector incorrectly handles data operations.

CVE-2020-26870 Visual Studio Installer Remote Code Execution Vulnerability

A remote code execution vulnerability exists when the Visual Studio Installer attempts to show malicious markdown.

How to download and Install Visual Studio 2019 Enterprise
How to download and Install Visual Studio 2019 Enterprise

Visual Studio 2019 version 16.7.9

released December 08, 2020

In this Release of Visual Studio 2019 version 16.7.9

Security Advisory Notice

CVE-2020-17156 Visual Studio Remote Code Execution Vulnerability A remote code execution vulnerability exists when Visual Studio clones a malicious repository.

  • Internal compiler error VS 16.7.0
  • Internal compiler error regression from 16.4
  • MSVC 16.7 incorrectly throwing C2355 for use of this pointer on initialization for in class non-static member
  • Wrong Output of attached Code in x86-release current VS2019
  • Update of MSVC 14.16, 14.20, 14.24, 14.27, and 14.28 toolsets to match latest servicing releases.

Visual Studio 2019 version 16.9.13

released November 09, 2021

Issues Addressed in this Release:

  • Fixed a bug that caused a start menu shortcut link to disappear. The bug only happened when updating multiple instances of different product SKUs on the same machine.

Security Advisory Notice

CVE-2021-42319 Elevation of Privilege Vulnerability An Elevation of Privilege vulnerability exists in the WMI Provider that is included in the Visual Studio installer.

CVE-2021-42277 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector incorrectly handles file operations.

VS 2019-22 Installation Migration Guide | Keep Install Config EASY
VS 2019-22 Installation Migration Guide | Keep Install Config EASY

Visual Studio 2019 version 16.11.6

released November 09, 2021

Issues Addressed in this Release

  • Address occasional instance where VSInstr would not exit when instrumenting a binary with volatile metadata.
  • Fix for “value of range” errors when using C++ IntelliSense.
  • Under certain conditions with an international locale selected fsi would crash when run from Visual Studio. This release fixes the issue and fsi should now operate correctly.
  • Fixes an issue that could cause Visual Studio to build, debug, or run tests against binaries that weren’t brought up to date with your latest code changes.
  • Fixes a thread pool leak during Cloud Services local debugging.
  • Add support for Android 12 APIs.
  • Fixes a potential deadlock when closing Performance Profiler or Diagnostic Tools on Windows Server machines.
  • Fixes a delay in VS startup.

Security Advisories Addressed

CVE-2021-42319 Elevation of Privilege Vulnerability An Elevation of Privilege vulnerability exists in the WMI Provider that is included in the Visual Studio installer.

CVE-2021-42277 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector incorrectly handles file operations.

Visual Studio 2019 version 16.9.14

released November 16, 2021

Issues Addressed in this Release:

  • The bootstrappers now respect the –useLatestInstaller parameter, which causes the latest installer to be integrated into layout. This latest installer, which ships with Visual Studio 2022, enables the scenario where enterprises want to transition their clients from one layout location to another. For more information, refer to the [Visual Studio Administrators Guide](* The bootstrappers now respect the –useLatestInstaller parameter, which causes the latest installer to be integrated into layout. This latest installer, which ships with Visual Studio 2022, enables the scenario where enterprises want to transition their clients from one layout location to another. For more information, refer to the Visual Studio Administrators Guide.).

Visual Studio 2019 version 16.7.6

released October 13, 2020

In this Release of Visual Studio 2019 version 16.7.6

  • Get the message “Working on it” when switching to a tab
  • Visual Studio Feedback – new Web-Browser based Version crashes due to proxy failure
  • Unable to build xamarin.ios library project with .xib interface declaration on specific version of VS
  • Cannot generate shim for System.DateTime
  • IntelliCode suggestion, filtering compilation errors
  • Inserting .NET Core SDK 3.1.403 into Visual Studio 2019
  • Fixed a bug that affects debugging https enabled Service Fabric Application.
  • Support Service Fabric nuget packages with external dependencies.

Visual Studio 2019 version 16.9.9

released July 13, 2021

Issues Addressed in this Release:

  • Fixed an ARM64X issue where Outlook crashes when using addins.
  • Fixed an issue in the C++ compiler will incorrectly perform if-conversions.
  • Fixed an ASan issue with compatibility on the latest Windows update.
  • ASan no longer reports a false-positive memcpy memory regions overlap error.
  • A function template with an unnamed function parameter of array type caused the parser to skip subsequent function definitions, resulting in a spurious constexpr error that a function is undefined when evaluating a call to it in a constant expression. The fix reenables the parsing of the skipped function definition.
  • We have fixed performance problem and false positives caused by one of the checker extensions that finds bugs in misuse of VARIANTs.
  • We have fixed performance problem caused by one of the checker extensions that finds bugs in misuse of enum values as index.
  • Fixed an Out of Memory leak when compiling multiple TUs.
  • Concurrency analyzer should no longer produce false warnings C26110 (failure to acquire lock) with auto-lock patterns.
  • This fix restores the behavior for external headers by skipping analysis of external headers and suppressing warnings from external headers.
  • The concurrency checks in code analysis got smarter. They are harder to fool with complex control flow.
  • Fixed issue related to layout creation.
  • Fixed an issue where updates could fail due to missing update channel information.

From Developer Community

  • Developer Community has a complete list of all of items shipping in this release.
  • Incorrect lock warnings by analyzer C26110
  • EnforceProcessCountAcrossBuilds emits code analysis warnings on system headers
  • Codeanalysis warning C6285 in STL functional.h in VS 16.10 preview 4. Worked in 16.10 preview 2
  • Functional(813) has warning C6285
  • C28301 warning in lmaccess.h/bcrypt.h
  • C33005 false positive with _variant_t/VARIANT
  • Incorrect C28251 messages in Microsoft headers following upgrade to VS 2019 16.10
  • Tons of bogus C28251 and C28301 warnings when running /analyze on C code

Visual Studio 2019 version 16.9.23

released June 14, 2022

Issues Addressed in this release:

  • Updated LibraryManager to accommodate changes to cdnjs API

Security Advisory Notice

  • CVE-2022-30184 .NET Information Disclosure Vulnerability A vulnerability exists in .NET 6.0 and .NET Core 3.1 within NuGet where a credential leak can occur.
  • CVE-2022-24513 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists when the Microsoft Visual Studio updater service improperly parses local configuration data.

Visual Studio 2019 version 16.11.1

released August 16, 2021

Issues Addressed in this Release

  • Fixes an issue installing the Microsoft.VisualStudio.ScriptedHost.Registry package during Visual Studio installation, which would cause the entire installation to fail.
  • Unblocked Adding a new SSH Connection through Tools Options

From Developer Community

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 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.

Visual Studio 2019 version 16.0.17

released August 11, 2020

Issue fixed in 16.0.17

Security Advisory Notice for 16.0.17

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

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.

Visual Studio 2019 version 16.7.11

released February 09, 2021

In this Release of Visual Studio 2019 version 16.7.11

Bug in optimization compiler of Visual Studio 2019 version 16.7.6

Security Advisory Notice

CVE-2021-1639 TypeScript Language Service Remote Code Execution Vulnerability A remote code execution vulnerability exists when Visual Studio loads a malicious repository containing JavaScript or TypeScript code files.

CVE-2021-1721 .NET Core Denial of Service Vulnerability A denial-of-service vulnerability exists when creating HTTPS web request during X509 certificate chain building.

CVE-2021-24112 .NET 5 and .NET Core Remote Code Execution Vulnerability A remote code execution vulnerability exists when disposing metafiles when a graphics interface still has a reference to it. This vulnerability only exists on systems running on MacOS or Linux.

  • Compiler crashes with fatal error C1001:An internal error has occurred in the compiler.
  • Bug in optimization compiler of Visual Studio 2019 version 16.7.6
  • Problem with loop auto-vectorizer
  • C++ Optimizer causes accumulation to fail if additional assignment takes place in same loop

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 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.

Visual Studio 2019 version 16.7.22

released November 16, 2021

In this Release of Visual Studio 2019 version 16.7.22

  • The bootstrappers now respect the –useLatestInstaller parameter, which causes the latest installer to be integrated into layout. This latest installer, which ships with Visual Studio 2022, enables the scenario where enterprises want to transition their clients from one layout location to another. For more information, refer to the [Visual Studio Administrators Guide](* The bootstrappers now respect the –useLatestInstaller parameter, which causes the latest installer to be integrated into layout. This latest installer, which ships with Visual Studio 2022, enables the scenario where enterprises want to transition their clients from one layout location to another. For more information, refer to the Visual Studio Administrators Guide.).

What’s New in Visual Studio 2019 version 16.11

Support Timeframe

Visual Studio 2019 version 16.11 is the fifth and final 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.11 will be supported with fixes and security updates through April 2029, which is the remainder of the Visual Studio 2019 product lifecycle.

In addition, now that version 16.11 is available, version 16.9, which was the last servicing baseline, will be supported for an additional 12 months and will go out of support in October 2022. Note as well that versions 16.10 is no longer under support either. 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.11 by clicking one of the buttons above, by visiting the Visual Studio site, or by going to the downloads section of my.visualstudio.com. You can get updates from the Microsoft Update catalog. For more information about Visual Studio supported baselines, please review the support policy for Visual Studio 2019.

Visual Studio 2019 version 16.11 Releases

  • February 13, 2024 — Visual Studio 2019 version 16.11.34
  • January 9, 2024 — Visual Studio 2019 version 16.11.33
  • November 14, 2023 — Visual Studio 2019 version 16.11.32
  • October 12, 2023 — Visual Studio 2019 version 16.11.31
  • September 12, 2023 — Visual Studio 2019 version 16.11.30
  • August 8, 2023 — Visual Studio 2019 version 16.11.29
  • July 25, 2023 — Visual Studio 2019 version 16.11.28
  • June 13, 2023 — Visual Studio 2019 version 16.11.27
  • April 11, 2023 — Visual Studio 2019 version 16.11.26
  • March 14, 2023 — Visual Studio 2019 version 16.11.25
  • February 14, 2023 — Visual Studio 2019 version 16.11.24
  • January 10, 2023 — Visual Studio 2019 version 16.11.23
  • December 13, 2022 — Visual Studio 2019 version 16.11.22
  • November 8, 2022 — Visual Studio 2019 version 16.11.21
  • October 11, 2022 — Visual Studio 2019 version 16.11.20
  • September 13, 2022 — Visual Studio 2019 version 16.11.19
  • August 9, 2022 — Visual Studio 2019 version 16.11.18
  • July 12, 2022 — Visual Studio 2019 version 16.11.17
  • June 14, 2022 — Visual Studio 2019 version 16.11.16
  • May 17, 2022 — Visual Studio 2019 version 16.11.15
  • May 10, 2022 — Visual Studio 2019 version 16.11.14
  • April 19, 2022 — Visual Studio 2019 version 16.11.13
  • April 12, 2022 — Visual Studio 2019 version 16.11.12
  • March 8, 2022 — Visual Studio 2019 version 16.11.11
  • February 8, 2022 — Visual Studio 2019 version 16.11.10
  • January 11, 2022 — Visual Studio 2019 version 16.11.9
  • December 14, 2021 — Visual Studio 2019 version 16.11.8
  • November 16, 2021 — Visual Studio 2019 version 16.11.7
  • November 09, 2021 — Visual Studio 2019 version 16.11.6
  • October 12, 2021 — Visual Studio 2019 version 16.11.5
  • October 05, 2021 — Visual Studio 2019 version 16.11.4
  • September 14, 2021 — Visual Studio 2019 version 16.11.3
  • August 25, 2021 — Visual Studio 2019 version 16.11.2
  • August 16, 2021 — Visual Studio 2019 version 16.11.1
  • August 10, 2021 — Visual Studio 2019 version 16.11.0

Visual Studio 2019 Archived Release Notes

  • Visual Studio 2019 version 16.10 Release Notes
  • Visual Studio 2019 version 16.9 Release Notes
  • Visual Studio 2019 version 16.8 Release Notes
  • Visual Studio 2019 version 16.7 Release Notes
  • Visual Studio 2019 version 16.6 Release Notes
  • Visual Studio 2019 version 16.5 Release Notes
  • Visual Studio 2019 version 16.4 Release Notes
  • Visual Studio 2019 version 16.3 Release Notes
  • Visual Studio 2019 version 16.2 Release Notes
  • Visual Studio 2019 version 16.1 Release Notes
  • Visual Studio 2019 version 16.0 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:

  • Visual Studio 2019 v16.11 is Available Now!
  • Visual Studio 2019 v16.10 and v16.11 Preview 1 are Available Today!
  • Enhanced Productivity with Git in Visual Studio
  • Available Today! Visual Studio 2019 v16.9 and v16.10 Preview 1
  • Visual Studio 2019 v16.9 Preview 3 is Available Today!
  • Visual Studio 2019 v16.9 Preview 2 and New Year Wishes Coming to You!
  • Visual Studio 2019 v16.8 and v16.9 Preview Available Today
  • New Features in Visual Studio 2019 v16.8 Preview 3.1
  • Visual Studio 2019 v16.8 Preview 2 Releases New Features Today!
  • Visual Studio 2019 v16.7 and v16.8 Preview 1 Release Today!
  • Visual Studio 2019 v16.7 Preview 2 Available Today!
  • Exciting new updates to the Git experience in Visual Studio
  • Releasing Today! Visual Studio 2019 v16.6 & v16.7 Preview 1
  • Visual Studio 2019 version 16.6 Preview 2 Releases New Features Your Way
  • Visual Studio 2019 version 16.5 is now available!
  • ‘Tis the Season for Visual Studio 2019 v16.4 Release
  • Visual Studio 2019 v16.4 Preview 2, Fall Sports, and Pumpkin Spice
  • .NET Core Support and More in Visual Studio 2019 version 16.3 – Update Now!
  • Visual Studio 2019 version 16.3 Preview 2 and Visual Studio 2019 for Mac version 8.3 Preview 2 Released!
  • Visual Studio 2019 version 16.2 and 16.3 Preview 1 now available
  • Visual Studio 2019 version 16.2 Preview 2
  • Visual Studio 2019 version 16.1 and Preview 16.2 Preview
  • Visual Studio 2019: Code faster. Work smarter. Create the future.

Visual Studio 2019 version 16.11.26

released April 11th, 2023

Issues Addressed in this release

  • Fixed an issue in IIS Express that could cause a crash when updating telemetry data.
  • Fixed a crash when invalid input is sent to the driver used during PGO training for kernel mode drivers.

Developer Community

Security Advisories Addressed

  • CVE-2023-28296 Visual Studio Remote Code Execution Vulnerability
  • CVE-2023-28299 Visual Studio Spoofing Vulnerability
  • CVE-2023-28262 Visual Studio Elevation of Privilege Vulnerability
  • CVE-2023-28263 Visual Studio Information Disclosure Vulnerability

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.

Product Name
Agents for Visual Studio 2019
Agents for Visual Studio 2019 (version 16.0)
Agents for Visual Studio 2019 (version 16.9)
Agents for Visual Studio 2019 Test Controller (version 16.0)
Build Tools for Visual Studio 2019
Build Tools for Visual Studio 2019 (version 16.0)
Intellitrace Standalone Collector for Visual Studio 2019
Performance Tools for Visual Studio 2019
Performance Tools for Visual Studio 2019 (version 16.0)
Remote Tools for Visual Studio 2019
Remote Tools for Visual Studio 2019 (version 16.0)
Visual C++ Redistributable for Visual Studio 2019
Visual C++ Redistributable for Visual Studio 2019 (version 16.0)
Visual Studio Community 2019
Visual Studio Enterprise 2019
Visual Studio Enterprise 2019 (version 16.0)
Visual Studio Enterprise Edition 2019 (version 16.0)
Visual Studio Professional 2019
Visual Studio Professional 2019 (version 16.0)
Visual Studio Professional Edition 2019 (version 16.0)
Visual Studio Team Explorer 2019
Visual Studio Team Explorer 2019 (version 16.0)

Copyright © 2017-2021 by HeiDoc.net

Visual Studio 2019 version 16.7 Release Notes

Developer Community | System Requirements | Compatibility | Distributable Code | Release History | License Terms | Blogs | Whats New in Visual Studio Docs

Note

This is not the latest version of Visual Studio. To download the latest release, please visit the Visual Studio site.

Support Timeframe

Visual Studio 2019 version 16.7 is now out of support.

Enterprise and Professional users of Visual Studio 2019 version 16.7 were supported and did receive fixes to security vulnerabilities through April 2022. This timeframe was determined by the fact that in March 2021, Visual Studio 2019 version 16.9 was designated as the next servicing baseline to the Visual Studio 2019 product. For more information about Visual Studio supported baselines, please review the support policy for Visual Studio 2019.

Refer to the latest version of the release notes or visit the Visual Studio site to download the latest supported version of Visual Studio 2019.

Visual Studio 2019 version 16.7 Releases

  • April 19, 2022 — Visual Studio 2019 version 16.7.28
  • April 12, 2022 — Visual Studio 2019 version 16.7.27
  • March 8, 2022 — Visual Studio 2019 version 16.7.26
  • February 8, 2022 — Visual Studio 2019 version 16.7.25
  • January 11, 2022 — Visual Studio 2019 version 16.7.24
  • December 14, 2021 — Visual Studio 2019 version 16.7.23
  • November 16, 2021 — Visual Studio 2019 version 16.7.22
  • November 09, 2021 — Visual Studio 2019 version 16.7.21
  • October 12, 2021 — Visual Studio 2019 version 16.7.20
  • September 14, 2021 — Visual Studio 2019 version 16.7.19
  • August 10, 2021 — Visual Studio 2019 version 16.7.18
  • July 13, 2021 — Visual Studio 2019 version 16.7.17
  • June 08, 2021 — Visual Studio 2019 version 16.7.16
  • May 11, 2021 — Visual Studio 2019 version 16.7.15
  • April 13, 2021 — Visual Studio 2019 version 16.7.14
  • March 09, 2021 — Visual Studio 2019 version 16.7.13
  • February 10, 2021 — Visual Studio 2019 version 16.7.12
  • February 09, 2021 — Visual Studio 2019 version 16.7.11
  • January 12, 2021 — Visual Studio 2019 version 16.7.10
  • December 08, 2020 — Visual Studio 2019 version 16.7.9
  • November 10, 2020 — Visual Studio 2019 version 16.7.8
  • October 27, 2020 — Visual Studio 2019 version 16.7.7
  • October 13, 2020 — Visual Studio 2019 version 16.7.6
  • September 29, 2020 — Visual Studio 2019 version 16.7.5
  • September 21, 2020 — Visual Studio 2019 version 16.7.4
  • September 8, 2020 — Visual Studio 2019 version 16.7.3
  • August 18, 2020 — Visual Studio 2019 version 16.7.2
  • August 11, 2020 — Visual Studio 2019 version 16.7.1
  • August 5, 2020 — Visual Studio 2019 version 16.7.0

Visual Studio 2019 Archived Release Notes

  • Visual Studio 2019 version 16.6 Release Notes
  • Visual Studio 2019 version 16.5 Release Notes
  • Visual Studio 2019 version 16.4 Release Notes
  • Visual Studio 2019 version 16.3 Release Notes
  • Visual Studio 2019 version 16.2 Release Notes
  • Visual Studio 2019 version 16.1 Release Notes
  • Visual Studio 2019 version 16.0 Release Notes

Visual Studio Blog

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

Visual Studio 2019 version 16.0.13

released April 14, 2020

Security Advisory Notice for 16.0.13

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.

Visual Studio 2019 version 16.11.12

released April 12, 2022

Issues Addressed in this release

  • Fixed an issue that would cause some animations for test execution to run in the background even when the associated test executions were complete. This causes slowdowns that were especially noticeable on high refresh rate monitors. The fix should improve the experience of using VS on high refresh rate monitors.
  • Removed an unnecessary warning when connecting to a LiveShare server that didn’t offer certain functionality used by the client.

From Developer Community

  • Optimized Qt applications crash on startup on ARM64
  • I get an error Live Share: The user of the output channel works with limited functionality due to the absence of a dependent service.
  • Find in IVsTextImage does not work in VisualStudio 2019

Security Advisories Addressed

CVE-2022-24765 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists in Git for Windows, in which Git operations could run outside a repository while seraching for a Git directory. Git for Windows is now updated to version 2.35.2.1.

CVE-2022-24767 DLL hijacking vulnerability A potential DLL hijacking vulnerability exists in Git for Windows installer, when running the uninstaller under the SYSTEM user account. Git for Windows is now updated to version 2.35.2.1.

CVE-2022-24513 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists when the Microsoft Visual Studio updater service improperly parses local configuration data.

Visual Studio 2019 version 16.11.22

released December 13th, 2022

Security Advisories Addressed

  • CVE-2022-41089 Remote Code Execution A remote code execution vulnerability exists in .NET Core 3.1, .NET 6.0, and .NET 7.0, where a malicious actor could cause a user to run arbitrary code as a result of parsing maliciously crafted xps files.

Visual Studio 2019 version 16.0.4

released May 14, 2019

Issues fixed in Visual Studio 2019 version 16.0.4

  • Attach to iis prompt to attach multiple times.
  • WPF applications broken after FW 4.8 update.
  • installing typescript 3.3 disables version 2.2 compilation.
  • Unable to attach debugger when attaching multiple startup projects on Visual Studio 2019.
  • Known issue: Application tab of VB project property pages is broken when isntalling the .NET Framework 4.8 Developer Pack.
  • Visual Studio extensions may fail to install attempting to overwrite core NuGet files.
  • microsoft.diagnosticshub.dotnetobjectalloc.vsix missing from offline installer.

Security Advisory Notice

CVE-2019-0727 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly performs certain file operations. An attacker who successfully exploited this vulnerability could delete files in arbitrary locations. To exploit this vulnerability, an attacker would require unprivileged access to a vulnerable system. The security update addresses the vulnerability by securing locations the Diagnostics Hub Standard Collector performs file operations in.

Visual Studio 2019 version 16.11.13

released April 19, 2022

Issues Addressed in this release

  • Fixed vctip.exe regression from 16.11.12
  • Fixed a bug that prevented some applications built with Address Sanitizer (ASAN) to load in Windows 11.
  • Fixed another ASAN issue where multi-threaded applications with heap contention may experience deadlocks, false “wild pointer freed” reports, or a deadlock during process exit.

Visual Studio 2019 version 16.11.8

released December 14, 2021

Issues Addressed in this Release

Bidirectional text control character rendering

To prevent a potentially malicious exploit that allows code to be misrepresented, the Visual Studio editor will no longer allow bidirectional text control characters to manipulate the order of characters on the editing surface. A new option will cause these bidirectional text control characters to be shown with placeholders. The bidirectional text control characters will still be present in the code as this behavior only impacts what is rendered in the code editor.

This functionality is controlled in Tools\Options. Under the Text Editor\General page there is an option for “Show bidirectional text control characters”, which will be checked by default. When checked, all bidirectional text control characters will be rendered as placeholders. Unchecking the option will revert to the previous behavior where these characters are not rendered.

A Unicode character is considered a bidirectional text control character if it falls into any of the following ranges: U+061c, U+200e-U+200f, U+202a-U+202e, U+2066-U+2069.

  • Corrected an issue in C++ compiler where a templated destructor involved in a class hierarchy with data member initializers may be instantiated too early, potentially leading to incorrect diagnostics about uses of undefined types or other errors.
  • Fixed an issue in ATL’s CString comparisions under C++20 and C++Latest language modes.
  • Added Python 3.9.7 to Python workload. Removed Python 3.7.8 due to a security vulnerability.

From Developer Community

  • Referenced DacPac file causes deployment to process refactorlog even if IncludeCompositeObjects is false
  • CString with spaceship operator <=> returns incorrect result (affects std::map, std::set, etc.)
  • Visual Studio sqldb project unable to create primary key with (statistics_incremental = on) on table
  • Template inheritance sometimes forces improper instantiation.
  • Visual Studio 2019 freezes when comparing aspx/aspx.vb files
  • Microsoft.Azure.Compute.Emulator.EXE will not be updated

Security Advisories Addressed

CVE-2021-43877 .NET Vulnerability An elevation of privilege vulnerability exists in ANCM which could allow elevation of privilege when .NET core, .NET 5 and .NET 6 applications are hosted within IIS.

CVE-2021-42574 Bidirectional Text Vulnerability Bidirectional text control characters can be used to cause code to be rendered in the editor differently from what is contained on disk.

Visual Studio 2019 version 16.9.16

released January 11, 2022

Issues Addressed in this Release:

  • Fixed intermittent crash with link.exe when building large projects with Visual Studio 16.8.5 or later.
  • Fixed an issue with being unable to debug applications multiple times when Windows Terminal is used as the default terminal.
  • Setup fix to unblock customers on restricted configurations
  • Fixed an issue that prevented a client from being able to update a more current bootstrapper. Once the client is using the bootstrapper and installer that shipped January 2022 or later, all updates using subsequent bootstrappers should work for the duration of the product lifecycle.

From Developer Community

  • Console application runs only once when the Windows Terminal is selected as Default Terminal Application

Visual Studio 2019 version 16.11.4

released October 05, 2021

Issues Addressed in this Release

  • Windows 11 SDK support.
  • Add AMD64 math functions to ARM64X CRT.
  • Updates to the ARM64 and ARM64EC interfaces between the binary and the POGO instrumentation runtime.
  • Fixed several problems with IntelliSense responsiveness and correctness affecting C++20 concepts, ranges, and abbreviated function templates.
  • Fixed a false positive in local lifetime checks.
  • Corrected an issue where arrays allocated with a constant of size > 32bits could allocate less memory than requested.
  • Ensures that ATL string initialization occurs during static variable initialization, in the default AppDomain.
  • Fixed a bug in C++ Concurrency::parallel_for_each that was crashing the calling process due to integer overflow.
  • Fixed a bug in the STL’s iterator debugging machinery that could cause crashes in multithreaded programs using STL containers.
  • We have fixed a fatal internal compiler error caused by unnamed structs whose fields are referenced from SAL annotations.
  • Fixes a rare crash when analyzing templated code that uses __uuidof.
  • Fixed an issue that caused C++ static analysis results to sometimes not display correctly in the FixIt action.
  • Fixed opening .uitest extension files in Coded UI project
  • Fire component change events for non-component objects also in WinForms .NET designer
  • Fix for crash on deleting ContextMenuStrip control in Windows Forms .NET designer.
  • Guard against crashes when the Windows Forms designer reloads when dragging.
  • Fix for intermittent VS crash while interacting with WinForms .NET designer during solution or project rebuild.
  • Fixed a bug causing .NET 5 projects to be reported as out of date when they should have been up to date, causing slower builds.
  • Automatically disable asset-indexing for large scale Unity projects.
  • Adds Xcode 13.0 support.
  • This release fixes an issue with deploying certain Windows Application Packaging projects where deployment is unnecessarily copying unmodified files.

From Developer Community

  • Comparing CComPtr with CComPtr results in an error
  • Structured binding in lambda in lambda cause a invalid compile error
  • Bad codegen with operator new
  • WinARM64 Build Failures with MFC/ATL Link issues after migrating from VS 16.8.6 to VS 16.9.5
  • The unity codelens provider still requires a huge amount of memory and could be OOMed in large scale Unity project in version 16.11.
  • Error C3493 with /std:c++latest using structured binding in Lambda

Visual Studio 2019 version 16.9.19

released April 12, 2022

Issues Addressed in this release:

Security Advisory Notice

CVE-2022-24765 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists in Git for Windows, in which Git operations could run outside a repository while seraching for a Git directory. Git for Windows is now updated to version 2.35.2.1.

CVE-2022-24767 DLL hijacking vulnerability A potential DLL hijacking vulnerability exists in Git for Windows installer, when running the uninstaller under the SYSTEM user account. Git for Windows is now updated to version 2.35.2.1.

CVE-2022-24513 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists when the Microsoft Visual Studio updater service improperly parses local configuration data.

Visual Studio 2019 version 16.9.7

released June 08, 2021

Issues Addressed in this Release:

  • Fixed a bug in the SSA instruction cloner.
  • Fixed an issue causing an mspdbcore.dll crash.
  • Fixed a long running/time out build of customer code bases.
  • Fixed an issue preventing developers to build PyTorch.
  • Fixes an internal MSBuild error (MSB0001) that arose when a large codebase was built with a 32-bit MSBuild.exe process.
  • Fixed an issue in the Container Tool Window causing a Visual Studio 2019 crash when developers tried to view mapped ports and then switch to a different container.

Security Advisory Notice

CVE-2021-31957 ASP.NET Denial of Service Vulnerability

A denial of service vulnerability exists when ASP.NET Core improperly handles client disconnect.

From Developer Community

Developer Community has a complete list of all of items shipping in this release.

Here are some of the top voted issues released in 16.9.7:

All Downloads

Visual Studio 2019 version 16.9 Release Notes

Developer Community | System Requirements | Compatibility | Distributable Code | Release History | License Terms | Blogs | Whats New in Visual Studio Docs

Note

This is not the latest version of Visual Studio. To download the latest release, please visit the Visual Studio site.

Visual Studio 2019 version 16.9.17

released February 8, 2022

Issues Addressed in this Release:

Security Advisory Notice

CVE-2022-21986 Vulnerability A Denial of Service vulnerability exists in .NET 5.0 and .NET 6.0 when the Kestrel web server processes certain HTTP/2 and HTTP/3 requests

CVE-2022-21871 Diagnostics Hub Standard Collector Runtime Elevation of Privilege Vulnerability An elevation of privilege vulnerability exists if the Diagnostics Hub Standard Collector incorrectly handles data operations.

Visual Studio 2019 version 16.11.21

released November 8th, 2022

Issues Addressed in this release

  • Added conditional guards to fix incorrect references in AMD64 optimizations for boost, stl_interfaces.

Security Advisories Addressed

  • CVE-2022-41119 Remote Code Execution Heap Overflow Vulnerbaility in Visual Studio
  • CVE-2022-39253 Information Disclosure Local clone optimization dereferences symbolic links by default

Visual Studio 2019 version 16.7.24

released January 11, 2022

In this Release of Visual Studio 2019 version 16.7.24

  • Fixed an issue with being unable to debug applications multiple times when Windows Terminal is used as the default terminal.
  • Setup fix to unblock customers on restricted configurations
  • Fixed an issue that prevented a client from being able to update a more current bootstrapper. Once the client is using the bootstrapper and installer that shipped January 2022 or later, all updates using subsequent bootstrappers should work for the duration of the product lifecycle.

From Developer Community

  • Console application runs only once when the Windows Terminal is selected as Default Terminal Application

Visual Studio 2019 version 16.7.14

released April 13, 2021

In this Release of Visual Studio 2019 version 16.7.14

  • Optimizer wrongly removing active code
  • NuGet will report package source and package content hash when restoring packages at normal output verbosity
  • NuGet will save package source in package’s .nupkg.metadata file in the global packages folder. Existing packages in the global packages folder will not get this additional information. Your global packages folder can be cleared to collect package source information for all packages.

Security Advisory Notice

CVE-2021-27064 Visual Studio Installer Elevation of Privilege Vulnerability A remote code execution vulnerability exists when the Visual Studio installer executes the feedback client in an elevated state.

CVE-2021-28313 / CVE-2021-28321/ CVE-2021-28322 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector incorrectly handles data operations.

Visual Studio 2019 version 16.7.3

released September 08, 2020

In this Release of Visual Studio 2019 version 16.7.3

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 Issues Fixed in this Release
  • Fixed a compiler crash for switch statements or switch expressions that use pattern matching.
  • Restored the “Stop Debugging(Shift +F5)” workflow for Unit Testing by terminating the test run.
  • Prevent VS crash on switching project configuration when WinForms .NET Core designer has unsaved changes.
  • Out of support versions of .NET Core will no longer be reinstalled during a repair or upgrade if they were removed outside of VS setup.
  • Fixed an issue where External Dependencies weren’t accurately searched in Find in Files.
  • Reintroduced the “Commit…” button in the Git submenu in Solution Explorer’s context menu.
  • Fixed a bug that caused the TFVC Check-in Notes label to be invisible.
  • Fix crash when using WinForm designer in SDK-style csproj with multiple target frameworks.
  • Fixed issue where

    was reporting an invalid markup error.
Top Issues Fixed from Developer Community in Visual Studio 2019 version 16.7.3
  • VS 2019 cannot find the commit code function after the modified commit code
  • WinForms Designer not load Forms with visual inheritance. VS CRASH!
  • Find in Files–Some *.h files are not included in the search even though they clearly belong to a project
  • Regression c++ background intellisense hangs on opensslconf.h fron a unc path in 16.7
  • C++ refactoring by change signature forgets header files
  • TFVC check-in notes not displayed in vs 2019
  • WPF XAML Designer – Style Data Context Design Time
  • Stop Debugging (Shift+ F5) does not stop the test run VS 2019 update 16.7.2.
  • VS2019 won’t open folder with CMake project

Visual Studio 2019 version 16.11.29

released August 8th, 2023

Issues Addressed in this release

  • Addressed an issue where VSWhere’s all switch would not return instances in an un-launchable state.

Security Advisories Addressed

  • CVE-2023-36897 Visual Studio 2010 Tools for Office Runtime Spoofing Vulnerability This security update addresses a vulnerability where unauthenticated remote attacker can sign VSTO Add-ins deployments without a valid code signing certificate.

Visual Studio 2019 version 16.0.8

released September 10, 2019

Issues fixed in Visual Studio 2019 version 16.0.8

  • Assembly does not match code for function
  • Visual Studio stops responding on creating a new SSIS project
  • Fixed UI freezes occurring after extended usage of the editor.

Security Advisory Notice

CVE-2019-1232 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly impersonates certain file operations. An attacker who successfully exploited this vulnerability could gain elevated privileges. An attacker with unprivileged access to a vulnerable system could exploit this vulnerability. The security update addresses the vulnerability by ensuring the Diagnostics Hub Standard Collector Service properly impersonates file operations.

Visual Studio 2019 version 16.11.10

released February 8, 2022

Issues Addressed in this Release

  • Fixed an issue that has caused sporadic C++ linker crashes.
  • Silent bad codegen issue with x64.
  • An issue that prevented files from being deleted while they were being processed by background C++ static analysis.
  • Resolved an issue in C++ ATL CString equality operator under C++20 mode.
  • Fixed an issue that could have prevented an initializer from running in a load test scenario.

From Developer Community

  • Missing comparison operators between LPCWSTR and CString in VS 16.11.8
  • x64 optimizer bug VC++2019 16.11.4

Security Advisories Addressed

CVE-2022-21986 Vulnerability A Denial of Service vulnerability exists in .NET 5.0 and .NET 6.0 when the Kestrel web server processes certain HTTP/2 and HTTP/3 requests.

Visual Studio 2019 version 16.11.15

released May 17, 2022

Issues Addressed in this release

  • Fixed connections for Azure SQL Managed Instance in SQL Server Data Tools, including Schema Compare and SQL Server explorer. Note: Support for Azure Arc enabled Managed Instance is pending a future release (In the Community)

From Developer Community

Visual Studio 2019 version 16.11.19

released Septemenber 13, 2022

Issues Addressed in this release

  • Made Resource View appear more reliably for projects that are reloaded

Security Advisories Addressed

  • CVE-2022-38013 .NET Denial of Service VulnerabilityA denial of service vulnerability exists in ASP.NET Core 3.1 and .NET 6.0 where a malicious client could cause a stack overflow which may result in a denial of service attack when an attacker sends a customized payload that is parsed during model binding.

Visual Studio 2019 version 16.7.20

released October 12, 2021

In this Release of Visual Studio 2019 version 16.7.20

Security Advisory Notice

CVE-2021-41355 Disclosure Vulnerability in .NET 5.0 An Information Disclosure vulnerability exists in .NET where System.DirectoryServices.Protocols.LdapConnection sends credentials in plain text on Linux.

CVE-2020-1971 OpenSSL Denial of Service Vulnerability A potential denial of service vulnerability exists in OpenSSL library, which is consumed by Git.

CVE-2021-3449 OpenSSL Denial of Service Vulnerability A potential denial of service vulnerability exists in OpenSSL library, which is consumed by Git.

CVE-2021-3450 OpenSSL Denial of Service Vulnerability A potential flag bypass exists in OpenSSL library, which is consumed by Git.

Visual Studio 2019 version 16.7.21

released November 09, 2021

In this Release of Visual Studio 2019 version 16.7.21

  • Fixed a bug that caused a start menu shortcut link to disappear. The bug only happened when updating multiple instances of different product SKUs on the same machine.

Security Advisory Notice

CVE-2021-42319 Elevation of Privilege Vulnerability An Elevation of Privilege vulnerability exists in the WMI Provider that is included in the Visual Studio installer.

CVE-2021-42277 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector incorrectly handles file operations.

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.

16.11.34 February 13, 2024 16.11.34601.136 Enterprise Professional BuildTools Release notes 16.11.33 January 9, 2024 16.11.34407.143 Enterprise Professional BuildTools Release notes 16.11.32 November 14, 2023 16.11.34301.259 Enterprise Professional BuildTools Release notes 16.11.31 October 10, 2023 16.11.34114.132 Enterprise Professional BuildTools Release notes 16.11.30 September 12, 2023 16.11.34031.81 Enterprise Professional BuildTools Release notes 16.11.29 August 8, 2023 16.11.33927.289 Enterprise Professional BuildTools Release notes 16.11.28 July 25, 2023 16.11.33920.266 Enterprise Professional BuildTools Release notes 16.11.27 June 13, 2023 16.11.33801.447 Enterprise Professional BuildTools Release notes 16.11.26 April 11, 2023 16.11.33529.622 Enterprise Professional BuildTools Release notes 16.11.25 March 14, 2023 16.11.33423.256 Enterprise Professional BuildTools Release notes 16.11.24 February 14, 2023 16.11.33328.57 Enterprise Professional BuildTools Release notes 16.11.23 January 10, 2023 16.11.33214.272 Enterprise Professional BuildTools Release notes 16.11.22 December 13, 2022 16.11.33130.400 Enterprise Professional BuildTools Release notes 16.11.21 November 8, 2022 16.11.33027.164 Enterprise Professional BuildTools Release notes 16.11.20 October 11, 2022 16.11.32929.386 Enterprise Professional BuildTools Release notes 16.11.19 September 13, 2022 16.11.32901.82 Enterprise Professional BuildTools Release notes 16.11.18 August 9, 2022 16.11.32802.440 Enterprise Professional BuildTools Release notes 16.11.17 July 12, 2022 16.11.32630.194 Enterprise Professional BuildTools Release notes 16.11.16 June 14, 2022 16.11.32602.291 Enterprise Professional BuildTools Release notes 16.11.15 May 17, 2022 16.11.32510.428 Enterprise Professional BuildTools Release notes 16.11.14 May 10, 2022 16.11.32428.217 Enterprise Professional BuildTools Release notes 16.11.13 April 19, 2022 16.11.32413.511 Enterprise Professional BuildTools Release notes 16.11.12 April 12, 2022 16.11.32407.337 Enterprise Professional BuildTools Release notes 16.11.11 March 8, 2022 16.11.32228.343 Enterprise Professional BuildTools Release notes 16.11.10 February 8, 2022 16.11.32126.315 Enterprise Professional BuildTools Release notes 16.11.9 January 11, 2022 16.11.32106.194 Enterprise Professional BuildTools Release notes 16.11.8 December 14, 2021 16.11.32002.261 Enterprise Professional BuildTools Release notes 16.11.7 November 16, 2021 16.11.31911.196 Enterprise Professional BuildTools Release notes 16.11.6 November 9, 2021 16.11.31829.152 Enterprise Professional BuildTools Release notes 16.11.5 October 12, 2021 16.11.31729.503 Enterprise Professional BuildTools Release notes 16.11.4 October 5, 2021 16.11.31727.386 Enterprise Professional BuildTools Release notes 16.11.3 September 14, 2021 16.11.31702.278 Enterprise Professional BuildTools Release notes 16.11.2 August 25, 2021 16.11.31624.102 Enterprise Professional BuildTools Release notes 16.11.1 August 16, 2021 16.11.31613.86 Enterprise Professional BuildTools Release notes 16.11.0 August 10, 2021 16.11.31605.320 Enterprise Professional BuildTools Release notes 16.10.4 July 20, 2021 16.10.31515.178 Enterprise Professional BuildTools Release notes 16.10.3 June 29, 2021 16.10.31424.327 Enterprise Professional BuildTools Release notes 16.10.2 June 15, 2021 16.10.31410.357 Enterprise Professional BuildTools Release notes 16.10.1 June 8, 2021 16.10.31402.337 Enterprise Professional BuildTools Release notes 16.10.0 May 25, 2021 16.10.31321.278 Enterprise Professional BuildTools Release notes 16.9.26 October 11, 2022 16.9.32930.78 Enterprise Professional BuildTools Release notes 16.9.25 September 13, 2022 16.9.32901.84 Enterprise Professional BuildTools Release notes 16.9.24 August 9, 2022 16.9.32802.399 Enterprise Professional BuildTools Release notes 16.9.23 July 12, 2022 16.9.32630.195 Enterprise Professional BuildTools Release notes 16.9.22 June 14, 2022 16.9.32602.290 Enterprise Professional BuildTools Release notes 16.9.21 May 10, 2022 16.9.32428.249 Enterprise Professional BuildTools Release notes 16.9.20 April 19, 2022 16.9.32413.69 Enterprise Professional BuildTools Release notes 16.9.19 April 12, 2022 16.9.32407.336 Enterprise Professional BuildTools Release notes 16.9.18 March 8, 2022 16.9.32228.547 Enterprise Professional BuildTools Release notes 16.9.17 February 8, 2022 16.9.32126.311 Enterprise Professional BuildTools Release notes 16.9.16 January 11, 2022 16.9.32106.192 Enterprise Professional BuildTools Release notes 16.9.15 December 14, 2021 16.9.32002.222 Enterprise Professional BuildTools Release notes 16.9.14 November 16, 2021 16.9.31910.168 Enterprise Professional BuildTools Release notes 16.9.13 November 9, 2021 16.9.31828.109 Enterprise Professional BuildTools Release notes 16.9.12 October 12, 2021 16.9.31728.308 Enterprise Professional BuildTools Release notes 16.9.11 September 14, 2021 16.9.31702.126 Enterprise Professional BuildTools Release notes 16.9.10 August 10, 2021 16.9.31529.145 Enterprise Professional BuildTools Release notes 16.9.9 July 13, 2021 16.9.31501.217 Enterprise Professional BuildTools Release notes 16.9.8 June 15, 2021 16.9.31409.214 Enterprise Professional BuildTools Release notes 16.9.7 June 8, 2021 16.9.31328.270 Enterprise Professional BuildTools Release notes 16.9.6 May 18, 2021 16.9.31313.79 Enterprise Professional BuildTools Release notes 16.9.5 May 11, 2021 16.9.31229.75 Enterprise Professional BuildTools Release notes 16.9.4 April 13, 2021 16.9.31205.134 Enterprise Professional BuildTools Release notes 16.9.3 March 30, 2021 16.9.31129.286 Enterprise Professional BuildTools Release notes 16.9.2 March 16, 2021 16.9.31112.23 Enterprise Professional BuildTools Release notes 16.9.1 March 9, 2021 16.9.31105.61 Enterprise Professional BuildTools Release notes 16.9.0 March 2, 2021 16.9.31025.194 Enterprise Professional BuildTools Release notes 16.8.7 March 9, 2021 16.8.31025.109 Enterprise Professional BuildTools Release notes 16.8.6 February 22, 2021 16.8.31019.35 Enterprise Professional BuildTools Release notes 16.8.5 February 9, 2021 16.8.31005.135 Enterprise Professional BuildTools Release notes 16.8.4 January 12, 2021 16.8.30907.101 Enterprise Professional BuildTools Release notes 16.8.3 December 8, 2020 16.8.30804.86 Enterprise Professional BuildTools Release notes 16.8.2 November 19, 2020 16.8.30717.126 Enterprise Professional BuildTools Release notes 16.8.1 November 12, 2020 16.8.30711.63 Enterprise Professional BuildTools Release notes 16.8.0 November 10, 2020 16.8.30709.132 Enterprise Professional BuildTools Release notes 16.7.28 April 19, 2022 16.7.32413.119 Enterprise Professional BuildTools Release notes 16.7.27 April 12, 2022 16.7.32407.390 Enterprise Professional BuildTools Release notes 16.7.26 March 8, 2022 16.7.32228.349 Enterprise Professional BuildTools Release notes 16.7.25 February 8, 2022 16.7.32125.265 Enterprise Professional BuildTools Release notes 16.7.24 January 11, 2022 16.7.32105.279 Enterprise Professional BuildTools Release notes 16.7.23 December 14, 2021 16.7.32002.127 Enterprise Professional BuildTools Release notes 16.7.22 November 16, 2021 16.7.31910.167 Enterprise Professional BuildTools Release notes 16.7.21 November 9, 2021 16.7.31828.227 Enterprise Professional BuildTools Release notes 16.7.20 October 12, 2021 16.7.31727.298 Enterprise Professional BuildTools Release notes 16.7.19 September 14, 2021 16.7.31701.349 Enterprise Professional BuildTools Release notes 16.7.18 August 10, 2021 16.7.31528.273 Enterprise Professional BuildTools Release notes 16.7.17 July 13, 2021 16.7.31429.392 Enterprise Professional BuildTools Release notes 16.7.16 June 8, 2021 16.7.31327.30 Enterprise Professional BuildTools Release notes 16.7.15 May 11, 2021 16.7.31229.181 Enterprise Professional BuildTools Release notes 16.7.14 April 13, 2021 16.7.31205.176 Enterprise Professional BuildTools Release notes 16.7.13 March 9, 2021 16.7.31026.100 Enterprise Professional BuildTools Release notes 16.7.12 February 10, 2021 16.7.31009.191 Enterprise Professional BuildTools Release notes 16.7.11 February 9, 2021 16.7.30928.143 Enterprise Professional BuildTools Release notes 16.7.10 January 12, 2021 16.7.30816.78 Enterprise Professional BuildTools Release notes 16.7.9 December 8, 2020 16.7.30802.117 Enterprise Professional BuildTools Release notes 16.7.8 November 10, 2020 16.7.30704.19 Enterprise Professional BuildTools Release notes 16.7.7 October 27, 2020 16.7.30621.155 Enterprise Professional BuildTools Release notes 16.7.6 October 13, 2020 16.7.30611.23 Enterprise Professional BuildTools Release notes 16.7.5 September 29, 2020 16.7.30523.141 Enterprise Professional BuildTools Release notes 16.7.4 September 21, 2020 16.7.30517.126 Enterprise Professional BuildTools Release notes 16.7.3 September 8, 2020 16.7.30503.244 Enterprise Professional BuildTools Release notes 16.7.2 August 18, 2020 16.7.30413.136 Enterprise Professional BuildTools Release notes 16.7.1 August 11, 2020 16.7.30406.217 Enterprise Professional BuildTools Release notes 16.7.0 August 5, 2020 16.7.30330.147 Enterprise Professional BuildTools Release notes 16.6.5 July 21, 2020 16.6.30320.27 Enterprise Professional BuildTools Release notes 16.6.4 July 14, 2020 16.6.30309.148 Enterprise Professional BuildTools Release notes 16.6.3 June 30, 2020 16.6.30225.117 Enterprise Professional BuildTools Release notes 16.6.2 June 9, 2020 16.6.30204.135 Enterprise Professional BuildTools Release notes 16.6.1 June 1, 2020 16.6.30128.74 Enterprise Professional BuildTools Release notes 16.6.0 May 19, 2020 16.6.30114.105 Enterprise Professional BuildTools Release notes 16.5.5 May 12, 2020 16.5.30104.148 Enterprise Professional BuildTools Release notes 16.5.4 April 14, 2020 16.5.30011.22 Enterprise Professional BuildTools Release notes 16.5.3 April 7, 2020 16.5.30002.166 Enterprise Professional BuildTools Release notes 16.5.2 March 31, 2020 16.5.29926.136 Enterprise Professional BuildTools Release notes 16.5.1 March 24, 2020 16.5.29920.165 Enterprise Professional BuildTools Release notes 16.5.0 March 16, 2020 16.5.29911.84 Enterprise Professional BuildTools Release notes 16.4.27 October 12, 2021 16.4.31728.76 Enterprise Professional BuildTools Release notes 16.4.26 September 14, 2021 16.4.31701.291 Enterprise Professional BuildTools Release notes 16.4.25 August 10, 2021 16.4.31528.272 Enterprise Professional BuildTools Release notes 16.4.24 July 13, 2021 16.4.31429.391 Enterprise Professional BuildTools Release notes 16.4.23 June 8, 2021 16.4.31327.141 Enterprise Professional BuildTools Release notes 16.4.22 May 11, 2021 16.4.31229.387 Enterprise Professional BuildTools Release notes 16.4.21 April 13, 2021 16.4.31205.175 Enterprise Professional BuildTools Release notes 16.4.20 March 9, 2021 16.4.31026.101 Enterprise Professional BuildTools Release notes 16.4.19 February 10, 2021 16.4.31009.304 Enterprise Professional BuildTools Release notes 16.4.18 February 9, 2021 16.4.30928.142 Enterprise Professional BuildTools Release notes 16.4.17 January 12, 2021 16.4.30816.121 Enterprise Professional BuildTools Release notes 16.4.16 December 8, 2020 16.4.30802.185 Enterprise Professional BuildTools Release notes 16.4.15 November 10, 2020 16.4.30703.110 Enterprise Professional BuildTools Release notes 16.4.14 October 13, 2020 16.4.30607.51 Enterprise Professional BuildTools Release notes 16.4.13 September 8, 2020 16.4.30427.197 Enterprise Professional BuildTools Release notes 16.4.12 August 11, 2020 16.4.30406.169 Enterprise Professional BuildTools Release notes 16.4.11 July 14, 2020 16.4.30308.118 Enterprise Professional BuildTools Release notes 16.4.10 June 9, 2020 16.4.30204.51 Enterprise Professional BuildTools Release notes 16.4.9 May 27, 2020 16.4.30120.98 Enterprise Professional BuildTools Release notes 16.4.8 May 12, 2020 16.4.30107.140 Enterprise Professional BuildTools Release notes 16.4.7 April 14, 2020 16.4.30011.19 Enterprise Professional BuildTools Release notes 16.4.6 March 10, 2020 16.4.29905.134 Enterprise Professional BuildTools Release notes 16.4.5 February 11, 2020 16.4.29806.167 Enterprise Professional BuildTools Release notes 16.4.4 January 31, 2020 16.4.29728.190 Enterprise Professional BuildTools Release notes 16.4.3 January 14, 2020 16.4.29709.97 Enterprise Professional BuildTools Release notes 16.4.2 December 17, 2019 16.4.29613.14 Enterprise Professional BuildTools Release notes 16.4.1 December 10, 2019 16.4.29609.76 Enterprise Professional BuildTools Release notes 16.4.0 December 3, 2019 16.4.29519.181 Enterprise Professional BuildTools Release notes 16.3.10 November 20, 2019 16.3.29519.87 Enterprise Professional BuildTools Release notes 16.3.9 November 12, 2019 16.3.29509.3 Enterprise Professional BuildTools Release notes 16.3.8 November 5, 2019 16.3.29503.13 Enterprise Professional BuildTools Release notes 16.3.7 October 29, 2019 16.3.29424.173 Enterprise Professional BuildTools Release notes 16.3.6 October 22, 2019 16.3.29418.71 Enterprise Professional BuildTools Release notes 16.3.5 October 15, 2019 16.3.29411.108 Enterprise Professional BuildTools Release notes 16.3.4 October 10, 2019 16.3.29409.12 Enterprise Professional BuildTools Release notes 16.3.3 October 8, 2019 16.3.29403.142 Enterprise Professional BuildTools Release notes 16.3.2 October 1, 2019 16.3.29326.143 Enterprise Professional BuildTools Release notes 16.3.1 September 25, 2019 16.3.29324.140 Enterprise Professional BuildTools Release notes 16.3.0 September 23, 2019 16.3.29318.209 Enterprise Professional BuildTools Release notes 16.2.5 September 10, 2019 16.2.29306.81 Enterprise Professional BuildTools Release notes 16.2.4 September 5, 2019 16.2.29230.47 Enterprise Professional BuildTools Release notes 16.2.3 August 20, 2019 16.2.29215.179 Enterprise Professional BuildTools Release notes 16.2.2 August 13, 2019 16.2.29209.62 Enterprise Professional BuildTools Release notes 16.2.1 August 6, 2019 16.2.29201.188 Enterprise Professional BuildTools Release notes 16.2.0 July 24, 2019 16.2.29123.88 Enterprise Professional BuildTools Release notes 16.1.6 July 9, 2019 16.1.29102.190 Enterprise Professional BuildTools Release notes 16.1.5 July 2, 2019 16.1.29025.244 Enterprise Professional BuildTools Release notes 16.1.4 June 25, 2019 16.1.29020.237 Enterprise Professional BuildTools Release notes 16.1.3 June 11, 2019 16.1.29009.5 Enterprise Professional BuildTools Release notes 16.1.2 June 5, 2019 16.1.29001.49 Enterprise Professional BuildTools Release notes 16.1.1 May 24, 2019 16.1.28922.388 Enterprise Professional BuildTools Release notes 16.1.0 May 21, 2019 16.1.28917.181 Enterprise Professional BuildTools Release notes 16.0.22 January 12, 2021 16.0.28803.916 Enterprise Professional BuildTools Release notes 16.0.21 December 8, 2020 16.0.28803.902 Enterprise Professional BuildTools Release notes 16.0.20 November 10, 2020 16.0.28803.868 Enterprise Professional BuildTools Release notes 16.0.19 October 13, 2020 16.0.28803.846 Enterprise Professional BuildTools Release notes 16.0.18 September 8, 2020 16.0.28803.826 Enterprise Professional BuildTools Release notes 16.0.17 August 11, 2020 16.0.28803.806 Enterprise Professional BuildTools Release notes 16.0.16 July 14, 2020 16.0.28803.791 Enterprise Professional BuildTools Release notes 16.0.15 June 9, 2020 16.0.28803.753 Enterprise Professional BuildTools Release notes 16.0.14 May 12, 2020 16.0.28803.735 Enterprise Professional BuildTools Release notes 16.0.13 April 14, 2020 16.0.28803.718 Enterprise Professional BuildTools Release notes 16.0.12 March 10, 2020 16.0.28803.697 Enterprise Professional BuildTools Release notes 16.0.11 January 14, 2020 16.0.28803.653 Enterprise Professional BuildTools Release notes 16.0.10 December 10, 2019 16.0.28803.631 Enterprise Professional BuildTools Release notes 16.0.9 October 15, 2019 16.0.28803.598 Enterprise Professional BuildTools Release notes 16.0.8 September 10, 2019 16.0.28803.584 Enterprise Professional BuildTools Release notes 16.0.7 August 13, 2019 16.0.28803.571 Enterprise Professional BuildTools Release notes 16.0.6 July 9, 2019 16.0.28803.540 Enterprise Professional BuildTools Release notes 16.0.5 June 11, 2019 16.0.28803.514 Enterprise Professional BuildTools Release notes 16.0.4 May 14, 2019 16.0.28803.452 Enterprise Professional Build Tools Release notes 16.0.3 April 30, 2019 16.0.28803.352 Enterprise Professional Build Tools Release notes 16.0.2 April 18, 2019 16.0.28803.202 Enterprise Professional Build Tools Release notes 16.0.1 April 9, 2019 16.0.28803.156 Enterprise Professional Build Tools Release notes 16.0.0 April 2, 2019 16.0.28729.10 Enterprise Professional Build Tools Release notes

Visual Studio 2019 version 16.11 Release Notes

Developer Community | System Requirements | Compatibility | Distributable Code | Release History | License Terms | Blogs | Whats New in Visual Studio Docs

Note

This is not the latest version of Visual Studio. To download the latest release, please visit the Visual Studio site.

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.

Visual Studio 2019 version 16.11.23

released January 10th, 2023

Security Advisories Addressed

  • CVE-2023-21538 .NET Denial of Service Vulnerability A denial of service vulnerability exists in .NET 6.0 where a malicious client could cause a stack overflow which may result in a denial of service attack when an attacker sends an invalid request to an exposed endpoint.

Visual Studio 2019 version 16.9.1

released March 09, 2021

Security Advisory Notice

CVE-2021-21300 Git for Visual Studio Remote Code Execution Vulnerability

A remote code execution vulnerability exists when Visual Studio clones a malicious repository.

CVE-2021-26701 .NET Core Remote Code Execution Vulnerability

A remote code execution vulnerability exists in .NET 5 and .NET Core due to how text encoding is performed.

Issues Addressed in this Release:

  • Fix for emission of incorrect ARM64EC metadata to OBJs.
  • Fixed an issue where C++ with FixIts turned on which is the default option, would see error squiggles upon opening code.
  • In some cases, C++ IntelliSense tries to use extremely large numbers of include paths and becomes non-responsive.
  • Increased stability of Live Share in C++ scenarios.
  • Fixed an issue where IntelliCode would stop loading symbols.
  • Improves solution load and close time in scenarios when users have the new experimental Razor editor enabled.
  • Fixed a crash scenario in ServiceHub that could happen after opening the Extensions and Updates dialog and then shutting down Visual Studio.
  • Fixed an error that would give a message that no updates were available when checking for updates on slower machines.
  • Improves performance of launching WAP projects from Visual Studio during incremental changes.
  • Fixed an issue causing setup to fail launching when using the Italian locale.
  • Fixed an upgrade scenario that would cause the installer to stop responding for a very long time while the .NET core tempalte cache is intialized.

From Developer Community

Developer Community has a complete list of all of items shipping in this release.

Here are some of the top voted issues released in 16.9.1:

  • Optimizer wrongly removing active code
  • -d1initall11 is causing C26019
  • Install takes a long time to complete during upgrade to Visual Studio 2019 16.9

Visual Studio 2019 version 16.7.8

released November 10, 2020

In this Release of Visual Studio 2019 version 16.7.8

Security Advisory Notice

CVE-2020-17100 Visual Studio Tampering Vulnerability A tampering vulnerability exists when the Python Tools for Visual Studio creates the python27 folder. An attacker who successfully exploited this vulnerability could run processes in an elevated context.

  • ICE during cppcorecheck analysis with compiler version 16.4.9
  • OACR fatal error C1001: Internal compiler error
  • ICEs during cppcorecheck analysis with compiler version 16.7.1
  • ICE in PREfast 16.7.1 running against Office code (ppt)
  • ClickOnce prerequisite VC++ 14 wont install due to different public key. This fix may have an increased chance of requiring a reboot of the machine in order to install an updated VC++ Redistributable package.
  • Optimizer incorrectly removes EH information causing some exceptions to crash
  • _InterlockedExchangeAdd64 is unresolved on x86
  • Fixed a bug in the C++ compiler of incorrect initialization of an aggregate with an alignment bitfield

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 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.

Visual Studio 2019 version 16.11.9

released January 11, 2022

Issues Addressed in this Release

  • Fixed an issue with being unable to debug applications multiple times when Windows Terminal is used as the default terminal.
  • Setup fix to unblock customers on restricted configurations
  • Fixed an issue that prevented a client from being able to update a more current bootstrapper. Once the client is using the bootstrapper and installer that shipped January 2022 or later, all updates using subsequent bootstrappers should work for the duration of the product lifecycle.
  • Addressed occasional instance where VSInstr would not exit when instrumenting a binary with volatile metadata causing Instrumentation Profiling to fail.
  • Fixed an issue were compiling C++ code with very large functions using /Og or #pragma optimize(“g”) can generate invalid code (bad codegen)
  • Fixed a bug in C++ Concurrency::parallel_for_each that was crashing the calling process due to integer overflow

From Developer Community

  • Console application runs only once when the Windows Terminal is selected as Default Terminal Application

Visual Studio 2019 version 16.7.26

released March 8, 2022

In this Release of Visual Studio 2019 version 16.7.26

Security Advisory Notice

CVE-2020-8927 Vulnerability A Remote code Execution vulnerability exists in .NET 5.0 and .NET Core 3.1 where a buffer overflow exists in the Brotli library versions prior to 1.0.8.

CVE-2022-24464 Vulnerability A denial of service vulnerability exists in .NET 6.0, .NET 5.0, and .NET CORE 3.1 when parsing certain types of http form requests.

CVE-2022-24512 Vulnerability A Remote Code Execution vulnerability exists in .NET 6.0, .NET 5.0, and .NET Core 3.1 where a stack buffer overrun occurs in .NET Double Parse routine.

CVE-2021-3711 OpenSSL Buffer Overflow vulnerability A potential buffer overflow vulnerability exists in OpenSSL, which is consumed by Git for Windows. Git for Windows is now updated to version 2.35.1.2, which addresses this issue.

Visual Studio 2019 version 16.9.21

released May 10, 2022

Issues Addressed in this release:

  • Updated Git for Windows version consumed by Visual Studio and installable optional component to 2.36.0.1
  • Fixed an issue with git integration, where if pulling/synchronizing branches that have diverged, output window would not show a localized hint on how to resolve it.

Security Advisory Notice

CVE-2022-29117 .NET Denial of Service Vulnerability A vulnerability exists in .NET 6.0, .NET 5.0 and .NET Core 3.1 where a malicious client can manipulate cookies and cause a Denial of Service.

CVE-2022-23267 .NET Core Denial of Service Vulnerability A vulnerability exists in .NET 6.0, .NET 5.0 and .NET Core 3.1 where a malicious client can cause a Denial of Service via excess memory allocations through HttpClient.

CVE-2022-29145 .NET Denial of Service Vulnerability A vulnerability exists in .NET 6.0, .NET 5.0 and .NET Core 3.1 where a malicious client can can cause a Denial of Service when HTML forms are parsed.

CVE-2022-24513 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists when the Microsoft Visual Studio updater service improperly parses local configuration data.

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 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.

Visual Studio 2019 version 16.9.6

released May 18, 2021

Issues Addressed in this Release:

  • Fixes “Cannot access a disposed object. Object name:’System.Net.Http.StringContent'” when trying to create a certificate or running Automatic Provisioning.
  • Fixed a problem that prevents the iOS Hot Restart feature to work correctly.

From Developer Community

Developer Community has a complete list of all of items shipping in this release.

Here are some of the top voted issues released in 16.9.6:

  • Bad code generated with /O2
  • Error adding Apple Developer Account: authentication service is unavailable
  • fatal error C1001: Internal compiler error (compiler file ‘D:\a01_work\4\s\src\vctools\Compiler\Utc\src\p2\main.c’, line 213)
  • VS 16.9.5 cannot deploy iOS app

Visual Studio 2019 version 16.7.1

released August 11, 2020

In This Release of Visual Studio 2019 version 16.7.1

Top Issues Fixed from Developer Community in Visual Studio 2019 version 16.7.1
  • SQL Server Project is crashing when editing columns using design panel.
  • SQL Server Database project : Fast scrolling in Design View of a table crashes VS
  • CImage::Draw() has ambiguous call to DrawImage() in 16.7.0 Preview1
  • Compiler Error when lowering x86 switch statements
  • arm64: function too large after upgrade from 15.9.16 to 16.4.11
  • Arm64: Indirect register (x8) contains invalid value at start of function
  • Unexpected error C2027: use of undefined type when using templates with /permissive-
  • Fixed a bug causing the C++ compiler to crash when building NanoRange

Visual Studio 2019

released April 02, 2019

Summary of What’s New in Visual Studio 2019

Install
  • Be more efficient now that Visual Studio updates will now be downloaded in the background.
  • Control installation mode for Visual Studio updates.
IDE
  • Collaborate with others using Visual Studio Live Share, which is installed by default. Additional language support for C++, VB.NET, and Razor gives guests a solution view and sharing of source control diffs.
  • Open code you recently worked on or start from one of the most commonly used flows like clone, open, or create a project through the new start window.
  • Create new projects with an improved search experience and filters using the new list of templates sorted by popularity.
  • Have more vertical room for your code and a modernized look and feel through a set of new visual changes in the shell.
  • View a sharper version of your IDE regardless of your display configuration and/or scaling, as we have improved support for per monitor awareness.
  • Use an improved search capability in Visual Studio for menus, commands, options, and installable components.
  • Quickly understand your code file’s ‘health’ with a document indicator. Run and configure through a one-click code cleanup from the indicator.
  • Easily manage the preview features you are opted in to with a new Preview Features page in the Options dialog.
  • Create new projects with improvements in tag-based search and an easily accessible “Recent project templates” list.
  • Create new items directly from Visual Studio Search and find results faster with improved relevance.
  • Stay informed of important information, such as Visual Studio Live Share requests, with a new notifications experience.
  • Save a collection of code cleanup fixers as a profile to easily select the fixers you want run during code cleanup.
  • Trigger new .NET refactoring and code fixes.
  • Configure .NET Core projects more easily with first-class project files.
  • See the status of your extensions with Preview, Paid, and Trial tags in the Extensions and Updates dialog.
  • Check and configure which Preview features you want active since the defaults have been reset in this Preview.
  • Keep your extensions up-to-date by excluding certain Test Window APIs that have been marked as deprecated in this release.
  • Sign in, browse, and one-click clone or connect to your hosted repositories from Azure DevOps through the start window.
  • Install extensions for other source control hosts to view repositories owned by you and your organization.
  • Experience an improved Blue theme experience that addresses feedback by dialing down the luminosity, improving overall contrast and addressing other usability issues.
  • Apply code style preferences from the command-line with the dotnet format global tool.
  • MSBuild and Visual Studio now target .NET Framework 4.7.2 by default.
  • We have removed Azure App Service-related features from Server Explorer; equivalent functionality is instead available in Cloud Explorer.
Performance
  • Take control of how solutions load by using Visual Studio’s new performance improvements that affect stepping speed, branch switching speed, and more.
  • See solution load progress in the Task Status Center.
  • Choose which projects to load on solution open with solution filter files.
  • Improve your typing performance by limiting the impact of auxiliary components.
  • Toggle the new option to disable restoring of your project hierarchy state and tool window state.
  • Learn the new shortcut for Build Selection and quickly Build All in CMake with the new Build All command.
  • Code faster with improved performance of IntelliSense for C++ files in CMake projects.
  • Load larger .NET Core solutions and enjoy significant memory reductions when working with them over time.
  • Load project dependencies quickly with a new project context menu command.
  • See performance tips in the performance center.
General Debugging and Diagnostics
  • Search keywords within the Watch, Autos, and Locals windows while debugging to improve your ability to find objects or values.
  • View a dropdown of format specifiers in the Watch, Autos, and Locals windows when inspecting data.
  • Use a custom visualizer, now compatible with .NET Core.
  • Debug very large applications with large numbers of modules and PDBs.
  • Launch Google Chrome with custom arguments and debug your JavaScript applications all within the Visual Studio IDE.
  • Use Hot Path Highlighting for CPU and DotNet Object Allocation tools in the Performance Profiler.
  • Break when a specific object’s property value changes in .NET Core 3.0+ applications using data breakpoints, a feature that was originally exclusive to C++.
  • Since Preview 1, we have updated the UI for searching in the Autos, Locals, and Watch windows with a simpler interface. The Search Deeper function has been changed to a dropdown so you can quickly select how deep you want your initial and subsequent searches to be.
Source Control and Team Explorer
  • Temporarily store changes so you can work on another task by using Team explorer’s Git tools support for Git stash.
  • Check out the optional extension available on the Visual Studio Market Place, Pull Requests for Visual Studio, that integrates Pull Request reviews into Visual Studio.
  • Use the new Azure DevOps work item experience that focuses on developer workflows, including user-specific work item views, creating a branch from a work item, searching for work items with #mentions, and inline editing.
Extensibility
  • Use a single, unified Visual Studio SDK in the NuGet package Microsoft.VisualStudio.SDK.
  • Take advantage of our update to the VSIX Project to now include an AsyncPackage.
  • Experiment with a new Empty VSIX Project template that we have added.
  • Know if an extension is Free, Paid, or Trial, as it is now indicated inside the Extensions and Updates dialog.
Programming Languages
C#

Experience a preview of the 8.0 language features that the C# compiler now supports, including:

  • Nullable reference types: When the feature is turned on (for example, with

    #nullable enable

    or at the project-level with


    enable


    ), reference types are treated as nullable if annotated with, and as non-nullable otherwise. The compiler then analyzes where null values flow and warns about likely unsafe usages.

  • switch

    expressions: Offers

    switch

    -like semantics in an expression context.
  • Recursive pattern matching: New patterns allow testing fields/properties and positional elements (from tuples or deconstruction).
  • Support for

    Range

    and

    Index

    types being used in CoreFX for slicing, including the

    x..y

    literal syntax for ranges.
  • Asynchronous streams represented by

    IAsyncEnumerable

    can be enumerated asynchronously with

    await foreach

    and can be produced with

    async IAsyncEnumerable

    iterator methods.

  • using

    declarations: Dispose at the end of the current block, without increasing the level of nesting.

    ref

    structs can be disposed by implementing a public

    Dispose()

    method.

  • static

    local functions: Local functions marked with

    static

    cannot reference

    this

    or variables in the enclosing functions.
  • Local functions and lambdas can now declare parameters and locals that shadow names of variables of the enclosing functions.
  • Null-coalescing assignment:

    x ??= y;

    only assignstoifwas

    null

    .

Find out more in Mads’ overview of C# 8.0.

See the C# language feature status and breaking changes for more details.

Additionally, you can use more modern C# language features in Visual Studio by default.

C++
  • Save time when writing C++ and XAML code by using Visual Studio IntelliCode, an optional extension that gives AI-assisted recommendations for your code.
  • Experience in-editor code analysis warnings. Code analysis runs automatically in the background and warnings display as green squiggles.
  • Try the new Template Bar, which uses the Peek Window UI and supports nested templates.
  • Run the new, updated implementation of the C++ Lifetime profile checker.
  • Configure your CMake projects using the new CMake Settings Editor, which provides an alternative to CMakeSettings.json.
  • Try out a host of backend improvements including OpenMP SIMD vectorization, link-time speedups, and more aggressive inlining.
  • Open existing CMake caches generated by external tools, such as CMakeGUI, or customized meta-build systems.
  • Improve analysis with /Qspectre for providing mitigation assistance for Spectre Variant 1 (CVE-2017-5753). For more information, see the Visual C++ Team Blog post.
  • Quickly switch between your previous sample arguments now that the Template Bar for Template IntelliSense has a Most Recently Used dropdown.
F#
  • F# 4.6 is released, along with various other compiler improvements.
  • Experience performance improvements for larger solutions and various bug fixes for F# and the F# tools.
  • Learn about some of the awesome work done by open source contributors to the F# language and tools.
JavaScript/TypeScript
  • Debug unit tests in Node.js projects.
  • Experience additional support for users who are building TypeScript projects from NuGet and npm packages.
Python
  • Easily add Python virtual and conda environments using the Python Add Environment dialog.
  • Work more easily with Python environments, including improved support for Open Folder workspaces using a new Python environment selector toolbar.
  • Create Visual Studio Live Share sessions and collaborate on Python code with other Visual Studio users.
Web Technologies
  • Take advantage of the added support for working with .NET Core 3.0 projects.
  • Check out CPU profiling of ASP.NET.
  • Use snapshot debugger for .NET web apps running on Virtual Machines, Virtual Machine Scale Sets, and Azure Kubernetes Service.
  • Develop container applications for Kubernetes with the Visual Studio Kubernetes Tools
  • Experience enhancements to the Azure DevOps work item experience that include inline support of assigning work items and an improved #mentions experience.
  • Work with project files more easily and experience a better console app for .NET Core tooling.
  • Experience enhancements to the publish profile summary for all apps. Additionally, a new section called Dependencies is now available when an app is published to Azure App Service.
  • Experience visual enhancements when creating a new ASP.NET application
  • Re-supply publish credentials for an existing Azure Functions publish profile
Container Tools
  • Experience a more streamlined single project for containerizing and debugging.
  • Make use of added support for debugging Alpine and additional base images.
Mobile Development with Xamarin
  • Get started quicker with a reduced Xamarin workload size and improved performance when creating new projects.
  • See more detailed build progress information.
  • Use IntelliCode with Xamarin.Forms XAML.
  • See your XAML previewed without building your project first with the new Basic Preview Mode in the Xamarin.Forms Previewer.
  • Preview your Xamarin.Forms XAML on different devices with the new Xamarin.Forms Previewer device drop-down.
  • Check out the new property panel for Xamarin.Forms controls.
  • Use the newly-added Shell template for Xamarin.Forms.
  • Experience improvements to Xamarin.Android initial and incremental build performance.
  • Create new Android emulators using the deploy target menu.
  • Speed up your build times with our improvements for build in Xamarin.Android.
  • Experience Enhanced Fast Deployment and d8/r8 support for Xamarin.Android.
  • Take advantage of enhanced productivity in the Xamarin.Android Designer.
  • Try out Xamarin.Android Designer improvements with initial support for constraint layouts.
  • Be more productive with the Xamarin.Android Designer by using Go-To-Definition and enhanced XML IntelliSense/Autocompletion for Android Resource files.
Universal Windows Platform (UWP)
  • Preserve comments, spacing, namespaces, and any other text changes when making edits from the designer. The package manifest designer now maintains strict fidelity to xml changes in the Package.appxmanifest file.
  • Use the Windows Application Packaging project for .NET Core projects to produce MSIX packages.
  • Use the Package Creation Wizard for direct Microsoft Store submissions.
  • Deployment to Windows Mobile devices is no longer supported in Visual Studio 2019. Attempts to deploy to a Windows 10 Mobile device will result in an error saying “Deployment to Windows Mobile devices is not supported in Visual Studio 2019”. If you need to continue working on an application for Windows 10 Mobile devices, continue to use Visual Studio 2017.

XAML Debugging Tools:

  • XAML Edit & Continue now supports x:bind (UWP): XAML Edit & Continue now supports editing data bindings created with x:bind for paths containing public properties, element name, indexed property paths (collections), attached properties, and cast properties. Other changes are not supported. This enhancement is available to any app where the minimum and maximum versions target Windows 10 SDK version 1809 (build 10.0.17763) or higher. (Note: XAML Edit & Continue is now known as XAML Hot Reload starting with Visual Studio 2019 Update 2+).
SQL Server Data Tools
  • Experience an updated SSDT and DacFX that now includes UTF-8 collation support.

Details of What’s New in Visual Studio 2019

Install
  • You can now choose how to install Visual Studio updates. The default mode is ‘Download all, then install’ which allows you to continue using Visual Studio while updates are being downloaded. Note that, if you select ‘Download all, then install’, you’ll need to finish up the installation by opening the Visual Studio Installer and selecting Continue.
  • Visual Studio updates will now be downloaded in the background. These downloads will occur only when your machine is idle. When the downloads complete, you will get a notification inside Visual Studio that your download is now ready to install.
  • You can now control your update installation mode and whether to download updates or not through the Tools > Options menu by changing the settings on Product Updates page.
Start window

The new start window provides a streamlined launch experience to help you quickly get to your code upon starting up Visual Studio.

  • View your recent projects and folders, and open them with a single click. Pin and remove items from the list through the context menu.
  • Clone or check out code by using any public or private git URL, which will also automatically open the folder in the IDE.
  • Sign in, browse, and one-click clone or connect to your hosted repositories from Azure DevOps or install extensions for other source control hosts to view repositories owned by you and your organization.
  • Browse your local disk or network share for projects, solutions, or any folders containing code, and open them in the IDE.
  • Select a project template that provides you with code scaffolding to help you get started with a new project or solution.
  • Search for project templates by their title, description, and tags or filter through available languages, platforms, and project types. The default list shows all available templates, while a list of your top 10 recently used project templates appears on the left pane for quick access. A two-page wizard allows you to concentrate on one decision at a time.
Shell and platform
  • Quickly spot which version of Visual Studio you’re opening and using via the new, improved product icon. The new icon is also more visible against a variety of backgrounds.
  • Experience a modernized look and feel of Visual Studio with our refreshed blue theme that gives you a cleaner user interface while still meeting our accessibility standards.
  • See more of your code, through our changes that target compactness and reclaim vertical space in the IDE. We have combined the title bar and the menu bar while also preserving existing functionality.
  • Use Visual Studio as a Per-Monitor Awareness application through a new, experimental setting. When on, this setting helps parts of Visual Studio, such as the shell and the editor, render more sharply regardless of your display configuration and/or scaling.
  • Experience an enhanced search experience across menus, commands, options, and installable components. Our new search now displays results dynamically, accommodates spelling errors, and provides relevant information (such as keyboard shortcuts) inside the search results.
  • View health information associated with your currently open file through the Document Health Indicator feature.
  • If you are a C# developer, you can quickly clean up some of the most common coding suggestions using Code Cleanup.
  • Select the set of fixers you’d like to have run by configuring Code Cleanup.
  • See the contents of your clipboard history via a context menu that extends the Clipboard Ring (Ctrl + Shift + V).
  • We’ve improved your search experience by:

    • Adding filters for Menus, Components, and Templates
    • Incorporating your search selections to give you the most relevant search results
    • Enabling you to create and add new projects/items to your solution directly from Visual Studio Search
  • The improved Per-Monitor Awareness (PMA) experience is now turned on by default for users that meet the minimum set of requirements (.NET 4.8 Preview & and Windows 10 April 2018 Update or newer). Tool windows such as Toolbox, Breakpoints, Watch, Locals, Autos & Call Stack have been converted to PMA and thus render sharply regardless of your display configuration and/or scaling.
  • A new notification experience adds:

    • A new icon and counter experience to the status bar
    • A new toast notification mechanism
    • Visual Studio Updates & Visual Studio licensing expiration notifications
  • A revised Blue theme experience that addresses feedback by dialing down the luminosity, improving contrast and addressing other usability issues.
  • Enhanced window-dragging capabilities by leveraging available free space in the toolbar region as a draggable region.
  • You can now save a collection of Code Cleanup fixers as a profile so you can quickly select the set of fixers you want run during Code Cleanup.
  • We’ve added tags in the Extensions and Updates dialog to help you quickly understand whether an extension is in Preview, is a Paid extension, or is in a Trial period.
  • The recommended way to implement data tooltips in Visual Studio 2019 and later is now IAsyncQuickInfoSourceProvider. Legacy Editor Quick Info APIs IVsTextTipData and TextTipData are deprecated in Visual Studio 2019 Preview 1.
  • The Editor Smart Tags (ISmartTag* family of interfaces in Microsoft.VisualStudio.Language.Intellisense namespace) have been deprecated in favor of the LightBulb API and are no longer supported starting with Visual Studio 2019 Preview 1.
  • The solution options Show advanced build configurations, Always show solution, and Save new projects when created have been removed due to low usage. These values have been set to their default value of True.
  • Opt in or out of certain preview features using the new Preview Features page found in Tools > Options > Environment > Preview Features.
Performance
  • We have added a new shortcut for Build Selection for folders and solutions: Ctrl + B.
  • Quickly open large solutions by loading your solution with all projects unloaded.
  • Choose which projects to load on solution open with Solution Filter Files.

    • Create a Solution Filter File by unloading projects you don’t want opened automatically, right-clicking the solution, and selecting Save As Solution Filter. You can then use the filter file to open the solution for subsequent uses.
  • Create a Solution Filter File by unloading projects you don’t want opened automatically, right-clicking the solution, and selecting Save As Solution Filter. You can then use the filter file to open the solution for subsequent uses.
  • We have added a command to Build All for CMake files: Ctrl + Shift + B.
  • We’ve improved IntelliSense performance in C++ files in CMake projects.
  • We’ve added a command to load unloaded project dependencies to the project and solution context menus.
  • Notification tips to improve performance of Visual Studio are now persisted in the performance center, accessible via Help > Manage Visual Studio Performance.
  • You can now see your solution load progress in the Task Status Center, as well as alerts when your solution loads finish.
  • Choose which projects to load on solution open with Solution Filter Files.

    • Create a Solution Filter File by unloading projects you don’t want opened automatically, right-clicking the solution, and selecting Save As Solution Filter. You can then use the filter file to open the solution for subsequent uses.
  • Experience improved build asset discovery and file search when you Ctrl+T in Open Folder scenarios.
  • Notice performance improvements now that the Visual Studio editor will limit the impact of auxiliary components on typing performance. Particularly, it will auto-cancel any long-running, nonessential operations when typing.
  • You can configure the Visual Studio auxiliary component limitation behavior via Tools > Options > Text Editor > Advanced:
  • You can now disable the restoration of the project hierarchy state from the previous session in the Solution Explorer tool window. We implemented this change because restoring the project hierarchy from previous session at solution open can delay solution load.

    • Toggle this option in Tools > Options > Projects and Solutions > General.
General Debugging and Diagnostics
General Debugging
  • Highlight, find, and navigate with keywords using our new search feature that we integrated into the Watch, Autos, and Locals windows.
  • View a dropdown of specifiers and options to format data in the Watch, Autos, and Locals windows by appending a comma to a listed item.
  • You can now use custom and DataSet visualizer support for .NET Core.
  • For C++ applications running on Windows, PDB now load in a separate 64-bit process. This change addresses a range of crashes caused by the debugger running out of memory when debugging applications that contain a large number of modules and PDBs.
Managed data breakpoints

You can now break when a specific object’s property value changes in .NET Core (3.0 or higher) applications using data breakpoints, a feature that was originally exclusive to C++. They are a great alternative to simply placing a breakpoint on a property’s setter because a data breakpoint can focus on a specific object’s property even when it’s out of scope, whereas the former option may result in constant, irrelevant breaks if you have hundreds of objects calling that function.

Watch window Search UX Updates

We have updated the UI for searching in the Autos, Locals, and Watch windows with a simpler interface. The Search Deeper function has been changed to a dropdown so you can quickly select how deep you want your initial and subsequent searches to be.

Apply code style preferences
  • You can now apply code style preferences from the command-line with the dotnet format global tool. To install, you will need .NET Core 2.1 SDK or later. Run the following command in your favorite terminal:

    dotnet tool install -g dotnet-format --version 3.0.0-beta4-19105-10
Extensibility
  • You will no longer be able to install extensions built with the V1 vsixmanifest extension format in Visual Studio 2019. V1 was introduced in Visual Studio 2010 and was deprecated in Visual Studio 2017 because it could cause reliability issues with Visual Studio. In Visual Studio 2019, the support for V1 has been completely removed. Extensions targeting Visual Studio 2019 should be rebuilt V2 or V3 of the vsixmanifest format.
  • You will now be notified when an extension is synchronously auto-loaded. Note, the extension will load and work as normal in this release, but is at risk of not functioning in the next Visual Studio 2019 update. More details can be found on our blog post about improving the responsiveness of critical scenarios by updating auto load behavior for extensions.
Unified SDK NuGet package

In the past, extension authors had to make many separate references to the individual NuGet packages of the Visual Studio SDK they needed to use in their extension. The versions of the various packages weren’t always aligned and that often resulted in dependency conflicts at compile time as well as runtime issues.

To solve these issues, use a new package called Microsoft.VisualStudio.SDK which contains dependencies on all the packages that make up the Visual Studio SDK. It solves the issue of version mismatches as well as makes it easy to know which version to use. Simply use the version of the package that corresponds to the lowest version of Visual Studio your extension supports and you will have access to the entire SDK.

Right now, only version 15.9 of the SDK package exists, but more will be released in the months to come all the way to version 14.0.

New and updated project templates

The VSIX Project template has gone through multiple updates to simplify it and make it better:

  • Uses the new, unified SDK NuGet package
  • Includes an AsyncPackage class
  • No longer requires a .resx file to compile a package
  • Targets .NET Framework 4.7.2

A new Empty VSIX Project template has been created and it is the same as the VSIX Project template but without the AsyncPackage class. It also references the unified SDK NuGet package providing a good starting point for MEF extensions and other package-less extension types.

Free/Paid/Trial

There hasn’t been an easy way to see if an extension was marked as free, paid, or a trial. This now changes so that inside the Extensions and Updates dialog, each extension that is either a trial or paid will be marked clearly as such. Extensions that don’t have a trial/paid label are free.

Testing tools

Additional APIs in the Test Window that were previously undocumented but marked as public have been added to the deprecation list.

Source Control
  • Temporarily store changes so you can work on another task now that Team Explorer’s Git tools support Git stash.
  • Review, run, and even debug pull requests from Azure Repos without leaving the IDE using our brand-new pull request experience in Visual Studio 2019. To get started, you can download the Pull Requests for Visual Studio extension from the Visual Studio Marketplace.
MSBuild
  • The MSBuild toolset version has been changed from

    15.0

    to

    Current

    .

    MSBuild.exe

    is now in

    %VSINSTALLDIR%\MSBuild\Current\Bin\MSBuild.exe

    .
  • MSBuild (and Visual Studio) now targets .NET Framework 4.7.2. If you wish to use new MSBuild API features, your assembly must also upgrade, but existing code will continue to work.
C#

For every release prior to Visual Studio 2019, the default C# language version was always equivalent to Latest Major. In Visual Studio 2017, C# evolved and released three minor versions: 7.1, 7.2, and 7.3. However, new projects were still defaulting to C# 7.0. This proved frustrating for C# developers who wanted to use new features, but had to manually change the language version for each new project.

To address this problem, the default C# language version is determined by its target framework:

  • If you are targeting .NET Core 3.0 preview, the C# language version will be C# 8.0 Preview.
  • If you are targeting .NET Framework or any non-preview of .NET Core, the C# language version will by C# 7.3.

This allows the use of the latest stable C# language features by default, and when using .NET Core previews, the use of C# 8.0 preview language features that align with .NET Core 3.0 Preview.

If you specify a language version via

LangVersion

in a project or props file, that language version overrides the previously described default.

C++
  • Collaborate in real time now that Visual Studio Live Share supports C++.
  • Save time by by using IntelliCode, an optional extension that uses its extensive training and your code context to put what you’re most likely to use at the top of your completion list. For C++, IntelliCode offers the most help when you are using popular libraries like STL.
  • We have modified several project template names and descriptions to fit with the updated New Project dialog.
  • We have removed the Clang/C2 experimental component. Use the MSVC toolset for full C++ standards conformance with /permissive- and/or /std:c++17, or the Clang/LLVM toolchain for Windows. See the Visual C++ Team Blog for more details.
  • We have deprecated the C++ Compiler /Gm switch. Consider disabling the /Gm switch in your build scripts if it’s explicitly defined. Alternatively, you can also safely ignore the deprecation warning for /Gm as it will not be treated as error when using “Treat warnings as errors” (/WX).
  • The C++ Android experience now defaults to Android SDK 25 and Android NDK 16b.
Productivity
  • Code analysis now runs automatically in the background. Warnings display as green squiggles in-editor as you type.
  • The Template Bar now utilizes the Peek Window UI rather than a modal window, supports nested templates, and prepopulates any default arguments into the Peek Window.
  • An automatic fix-it for the NULL->nullptr code analysis warning (C26477 USE_NULLPTR_NOT_CONSTANT) is available via the lightbulb menu on relevant lines, enabled by default in the C++ Core Check Type Rules ruleset. Additional quick fixes in the IDE include adding missing #include directives, fixing missing semicolons, and fixing incorrect uses of ‘*’ versus ‘&’.
  • Precompiled headers are no longer generated by default for C++ console and desktop apps.
  • Go to Definition now works on #include directives, opening the corresponding file. This includes the F12 shortcut, providing an easy way to navigate around your code.
  • Hovering over a closing brace of a code block provides some helpful information about the context of that block.
  • We’ve added support in ConcurrencyChecker for well-known STL types from the

    header.
  • An updated partial implementation of the Lifetime profile checker is available for detecting dangling pointers and references.
  • We’ve added initial support in the compiler for the C++20 operator <=> (“spaceship”) for three-way comparison.
CMake
  • We’ve improved performance of IntelliSense for C++ files in CMake projects.
  • Visual Studio helps bootstrap your C++ development with CMake on Linux by detecting if you have a compatible version of CMake on your Linux machine. If not, it offers to install it for you.
  • The CMake Settings Editor provides an alternative to CMakeSettings.json and provides some parity with CMakeGUI.
  • The CMake menu has been removed and reorganized for closer parity with projects and solutions.
  • Incompatible settings in CMakeSettings, such as mismatched architectures or incompatible CMake generator settings, show squiggles in the JSON editor and errors in the Error List.
  • The vcpkg toolchain is automatically detected and enabled for CMake projects that are opened in the IDE once

    vcpkg integrate install

    has been run. This behavior can be turned off by specifying an empty toolchain file in CMakeSettings.
  • CMake projects now enable Just My Code debugging by default.
  • Static analysis warnings can now be processed in the background and displayed in the editor for CMake projects.
  • We’ve added clearer build and configure ‘begin’ and ‘end’ messages for CMake projects and support for Visual Studio’s build progress UI. Additionally, there is now a CMake verbosity setting in Tools > Options to customize the detail level of CMake build and configuration messages in the Output Window.
  • The ‘cmakeToolchain’ setting is now supported in CMakeSettings to specify toolchains without manually modifying the CMake command line.
Backend
  • We’ve implemented build throughput improvements, including the linker’s handling of File I/O and link time in PDB type merging and creation.
  • We’ve added basic support for OpenMP SIMD vectorization. This can be enabled with the new CL switch -openmp:experimental. This allows loops annotated with “#pragma omp simd” to potentially be vectorized. The vectorization is not guaranteed, and loops annotated but not vectorized will get a warning reported. If no SIMD clauses are supported, they will simply be ignored and a warning will be reported.
  • We’ve added a new inlining command line switch -Ob3, which is a more aggressive version of -Ob2. -O2 (optimize the binary for speed) still implies -Ob2 by default; if you find the compiler is under-inlining, consider passing -O2 -Ob3.
  • To support hand vectorization of loops containing calls to math library functions and certain other operations like integer division, we’ve added support for Short Vector Math Library (SVML) intrinsic functions that compute the 128-bit, 256-bit or 512-bit vector equivalents. See the Intel Intrinsic Guide for definitions of the supported functions.
  • New and improved optimizations:

    • Constant-folding and arithmetic simplifications for expressions using SIMD (vector) intrinsics, for both float and integer forms
    • A more powerful analysis for extracting information from control flow (if/else/switch statements) to remove branches always proven to be true or false
    • Improved memset unrolling to use SSE2 vector instructions
    • Improved removal of useless struct/class copies, especially for C++ programs which pass by value
    • Improved optimization of code using memmove, such as std::copy or std::vector and std::string construction
Deprecations
  • The Managed C++ Test Project template is no longer available. You can continue using the Managed C++ Test framework in your existing projects but, for new unit tests, consider using one of the native test frameworks for which Visual Studio provides templates (MSTest, Google Test) or the Managed C# Test Project template.
  • The Windows 8.1 SDK is no longer available in the Visual Studio installer. Please upgrade your C++ projects to the latest Windows 10 SDK. If you have a hard dependency on 8.1, you can download it from the Windows SDK archive.
  • Windows XP targeting will no longer be available for the latest C++ toolset. XP targeting with VS 2017-level MSVC compiler & libraries is still supported and can be installed via “Individual components”.
  • Our documentation actively discourages usage of Merge Modules for Visual C++ Runtime deployment. We are taking the extra step this release of marking our MSMs as deprecated. Consider migrating your VCRuntime central deployment from MSMs to the redistributable package.
  • The following C++ ATL/MFC wizards are no longer available: ATL COM+ 1.0 Component Wizard, ATL Active Server Pages Component Wizard, ATL OLE DB Provider Wizard, ATL Property Page Wizard, ATL OLE DB Consumer Wizard, MFC ODBC Consumer, MFC class from ActiveX control, and MFC class from Type Lib. Sample code for these technologies is archived at the VCSamples GitHub repository.
F#

F# improvements in Visual Studio 2019 are in three major areas:

  • F# 4.6
  • Major performance improvements for medium and larger solutions
  • Lots of open source work by our excellent open source community
F# 4.6

This release contains the F# 4.6 language:

  • Anonymous Record types have been added to the language, including full tooling support and the ability to emit them types into JavaScript objects via the Fable compiler.
  • ValueOption type and ValueOption module function parity with Option type.
  • tryExactlyOne function for arrays, lists, and sequences, contributed by Grzegorz Dziadkiewicz.
F# compiler and FSharp.Core improvements

The F# and compiler and FSharp.Core have seen numerous improvements, especially from open source contributors:

  • fsi.exe and fsc.exe now defaults to .NET Framework 4.7.2, allowing the loading of components targeting this framework or lower (#4946).
  • We optimized methods on structs and struct records to perform as well as methods on classes and class-based records (#3057).
  • We optimized the emitted IL for combined Boolean logic in F# code (#635).
  • We’ve optimized the use of with strings in F# to call the minimal amount of

    String.Concat

    calls as possible (#5560).
  • We fixed an issue in the FSharp.Core package where some extra directories with test assets were included. FSharp.Core 4.5.5 and 4.6.1 should have the fix (#5814).
  • When a user-defined attribute does not inherit from the

    Attribute

    class, you will now receive a warning, by Vasily Kirichenko.
  • The

    AssemblyInformationVersionAttribute

    value in a project file now supports arbitrary values to support scenarios such as SourceLink (#4822).
  • A bug where illegal syntax with Active Patterns would cause an internal compiler error has been fixed by Steffen Forkmann (#5745).
  • A bug where the

    Module

    suffix was erroneously added to a module in a recursive module to match a type where the only difference is a generic parameter was fixed by BooksBaum (#5794).
  • An improvement to the error message when type parameters are not adjacent to a type name has been improved by Alan Ball (#4183).
  • The

    uint16

    literal suffix is listed correctly in the error messages for invalid numeric literals, by Teo Tsirpanis (#5712).
  • Error messages for computation expressions no longer state

    async

    in the message and instead refer to “computation expression(s)”, by John Wostenberg (#5343).
  • An error message when incorrectly referencing

    .dll

    s in F# interactive was fixed by Bartoz Sypytkowski (#5416).
  • A bug where Statically Resolved Type Parameters couldn’t handle calling a member that hides an inherited member was fixed by Victor Peter Rouven Müller (#5531).
  • Various smaller performance improvements to the compiler have been added by Steffen Forkmann and Robert Jeppesen.
F# performance improvements

Another big focus area for F# in Visual Studio 2019 has been performance for medium and large solutions. We addressed some very long-standing issues, some of which dating back to the very first edition of F# tools for Visual Studio. We also got some help from the excellent F# open source community.

  • We’ve revamped how the F# language service is initialized by Roslyn. Type colorization for larger solutions should generally appear sooner.
  • We changed our representation of source text to avoid large allocations over time, especially with bigger files (#5935, #5936, #5937, #4881).
  • We changed our build caches for small edits to files to use significantly less memory (#6028).
  • We modified a compiler feature that suggests names when unrecognized tokens are typed to only compute these suggestions on-demand, resulting in significant CPU and memory reductions when typing slowly in larger solutions (#6044).
  • We changed IntelliSense so that it will no longer show symbols from unopened namespaces by default. This notably improves performance for IntelliSense in projects with many references. This feature can be turned back on in the settings via Tools > Options > Text Editor > F# > IntelliSense.
  • We improved memory usage when using Type Providers to generate very large amounts of provided types in a completion list (#5599).
  • A reduction to CPU and memory usage to an internal string comparison algorithm for suggesting unrecognized names has been fixed by Avi Avni (#6050).
  • A notable source of large string allocations, particularly for IDE tooling, was fixed by Avi Avni (#5922).
  • A notable source of Large Object Heap allocations coming from computing IntelliSense has been fixed by Chet Husk (#6084)
F# tooling improvements

In addition to performance improvements, various other improvements to F# tooling for Visual Studio 2019 have been made:

  • The Add

    open

    statement code fix will now default to adding the

    open

    statement at the top of the file.
  • We fixed a bug where

    match!

    in user code invalidated structure guidelines and code outlining nodes for subsequent scopes (#5456).
  • The editor will now correctly color

    byref

    ,

    outref

    , and

    ref

    values as record fields with the mutable value colorization (#5579).
  • We fixed a bug where the rename refactoring did not recognize the character in symbol names (#5604).
  • We’ve fixed a longstanding bug where renaming F# script files resulted in a loss of colorization data (#1944).
  • We cleaned up IntelliSense so that it doesn’t show unrelated items in the list when pressing backspace.
  • With “Smart” indentation on, pasting F# code into the editor will now format it to match an appropriate scope based on the current cursor position, implemented by Saul Rennison (#4702).
  • An issue where F# editor options weren’t syncing has been fixed by Jakob Majocha (#5997, #5998).
  • A bug where IntelliSense in a constructor within an

    inherit

    clause wouldn’t show the primary constructor has been fixed by Eugene Auduchinok (#3699)
  • Various smaller improvements to the F# language service have been made by Eugene Auduchinok
F# open source infrastructure

We’ve fully migrated the F# and F# tools codebase to use the .NET SDK. This dramatically simplifies the contribution process for developers, especially if they are not using Windows. Additionally, Jakob Majocha has helped in cleaning up documents for new contributors in light of the changes to the codebase.

Python

Based on customer feedback, Visual Studio 2019 includes an overhauled experience for managing Python environments:

  • We added a new Add environment dialog that simplifies the experience of creating and adding virtual environments and conda environments in your project.
  • The Visual Studio installer no longer installs full versions of Anaconda to reduce the size of Visual Studio installs and avoid errors during upgrades.
  • Miniconda is bundled with Python workload as an optional component, enabling you to create conda environments without having to install Miniconda/Anaconda.
  • You will now be automatically prompted to add an environment if a requirements.txt (virtual environment) or environment.yml (conda environment) is present at the root of your project.
  • A new Python Environments toolbar is available when editing Python files. The new toolbar enables you to switch between different Python interpreters when working with projects, Open Folder workspaces or loose Python files in other projects.
  • Improvements to the quality of auto-completions in Python IntelliSense, including improved detection of relative and namespace imports.
  • Django project templates have been updated to support Django 2.x.
  • Function return values are now shown in the Python debugger.
  • You can now create VS Live Share sessions and collaborate on Python code with other Visual Studio users. Previously, Python was only supported when joining sessions created from Visual Studio Code.
JavaScript/TypeScript
  • We have added support for enabling JavaScript debugging within unit tests in Node.js projects. This was a long-requested feature from our Node.js customers.
  • The JavaScript/TypeScript language service will now be automatically loaded in projects that have the TypeScript NuGet package or npm package installed (TypeScript 3.2 and up is supported from the NuGet package and TypeScript 2.1 and up is supported from the npm package).
  • We have implemented performance improvements in the language service as a result of increasing the memory cap on the language service to handle larger projects.
  • We no longer show diagnostics of closed JavaScript/TypeScript files in the error list by default.
  • The legacy JavaScript language service is no longer available. Previously, users had the option of restoring the legacy JavaScript language service. Users will now have the new JavaScript language service out-of-the-box. The new language service is based on the TypeScript language service, which is powered by static analysis. This enables better tooling, so your JavaScript code can benefit from richer IntelliSense based on type definitions. The new service is lightweight and consumes less memory than the legacy service, providing users with better performance as their code scales.
Team Explorer and Azure DevOps

We have made improvements to the Git Work Items experience with Azure DevOps.

  • Assign work items to yourself or others with the new identity picker. By default, you will be shown a list of the people you have most recently used. Or, use the search ability to search and find others in your organization.
  • We have improved the #mentions experience in the commit message. As you select a work item from the #mention picker, it will automatically be added to the Related Work Items list.
Hot Path Highlighting
  • We have added support for hot path highlighting in both the CPU Usage and DotNet Object Allocation tools in the Performance Profiler. Select any function in the call tree and press the hot path button to expand the CPU Usage or Dot Net Object Allocation hot path. This feature allows you to easily identify the function calls which use the highest percentage of the CPU or that allocate the most objects.
.NET and ASP.NET Tools
  • We have implemented various small UX improvements to the publish profile summary page (new section headers and actions/shortcuts) for all applications.
  • When publishing ASP.NET applications to Azure App Service, the publish profile summary page now has a new section called “Dependencies”. This new section currently allows you to associate Azure Storage and Azure SQL resources with your app service instance. Expect more Azure services to be surfaced through this mechanism in the future.
  • Use code metrics with .NET Core projects with our added compatibility.
  • Export editor settings to an Editorconfig file through Tools > Options > Text Editor > C# > Code Style with the button “Generate .editorconfig file from settings”.
  • Use C# and Visual Basic’s new Regex parser support. Regular expressions are now recognized, and language features are enabled on them. Regex strings are either recognized when a string is passed to the Regex constructor or when a string is immediately preceded with a comment containing the string

    language=regex

    . The language features included in this release are classification, brace matching, highlight references, and diagnostics.
  • You can now use dead code analysis for unused private members with an optional code fix to remove unused member declaration.
  • The Find References feature on an accessor now only returns results for that accessor.
  • We have added a code fix for generating a deconstruct method.
  • “Using” statements can be added when code is pasted into a file. A code fix appears after pasting recognized code that prompts you to add relevant missing imports.
  • There are now more refactoring and quick actions available by using “Ctrl + .” or “Alt + Enter”:

    • For cases where “await” is implied but omitted, there is now a compiler warning.
    • For converting a local function to a method.
    • For converting a tuple to a named-struct.
    • For converting an anonymous type to a class.
    • For converting an anonymous type to a tuple.
    • For a foreach loop to LINQ query or to LINQ method.
  • You now have added support for ASP .NET Core applications running in an Azure Kubernetes Service. To get started, see this docker example over on GitHub.
  • ASP.NET is now supported in the CPU Usage tool of the Performance Profiler.
  • You can now use Find All References (Shift-F12) and CodeLens to show results from Razor (.cshtml) files in .NET Core projects. You can then navigate to the identified code in the relevant Razor files.
  • We’ve added support for targeting ASP .NET (core and desktop) applications running on Windows Virtual Machines (VM) and VM Scale Sets.
  • You will now receive a warning when running code analysis using FxCop. .NET Compiler analyzers are the recommended way to perform code analysis going forward. Read more on migrating to .NET compiler platform analyzers.
  • Portable Class Library (PCL) project templates are no longer available, and project support will not be installed by default. New projects intended to target multiple platforms should use the .NET Standard project type. Customers who require PCL project support must install the component separately from the Individual Components tab in the Visual Studio installer.
  • The “Project.CopyWebSite” command is no longer available. This feature was only available on the “Web Site” project type for .NET. It provided the ability to synchronize two web sites so that they have the same version of each file. In Visual Studio 2019, you can copy the files from the remote destination outside of Visual Studio and then open the project.
  • The ability to open a Web Site project from a remote FTP location has been removed. FTP users can copy the files from the remote destination outside of Visual Studio, open the project and make changes, and then use publish to push them back to the remote FTP location.
  • The ASP.NET and Web workload no longer installs a custom CoffeeScript editing experience. Visual Studio’s TextMate bundles provide a superior experience for working with CoffeeScript.
  • CSS and CoffeeScript errors that are currently generated by built-in copies of CSSLint and CoffeeLint will no longer automatically surface when editing those files. Use an alternative method for running linters such as npm or the Visual Studio Task Runner Explorer.
  • Visual Studio no longer provides IntelliSense for Knockout HTML attributes. In Visual Studio 2019 you will need to type the attributes.
  • The ability to use the Legacy Chrome debugger in ASP.NET projects for debugging JavaScript has been removed. You can continue to use the current Chrome debugger built into Visual Studio.
  • The ability to use JavaScript Console functionality in ASP.NET projects has been removed. We recommend that customers use Console included within their favorite browser devtools.
Container Tools
  • We’ve added a streamlined single-project experience for containerizing and debugging:

    • ASP.NET Web Applications (.NET Framework)
    • Console Applications (.NET Core)
  • We’ve added support for debugging ASP.NET Core Applications that use Alpine as a base image.
  • We’ve added support for the latest ASP.NET and .NET Core images.
.NET Core tools
.NET Core 3.0

With this release, you can create ASP.NET Core, Console, and Class Library projects targeting .NET Core 3.0 if you have the preview SDK installed.

If you are using Visual Studio RC, you need to also go to Tools > Options > Projects and Solutions > .NET Core and check the Use previews of the .NET Core SDKs checkbox. If you are using Visual Studio Preview, you do not need to do this. You can read more about this setting and its behavior in .NET Core tooling update for Visual Studio 2017 version 15.9.

You can also create Windows Forms or WPF projects for .NET Core 3.0 with the “dotnet new” command. These projects can then be opened in Visual Studio 2019.

New features

Starting with this release, we are making project files for .NET SDK-style projects a first-class file type in Visual Studio. The following is now supported:

  • Double-click a project node to open the project file
  • Single-click the project node to open the project file in a Preview tab
  • Find a project file by name with Go to All (

    ctrl + T

    )
  • MSBuild elements in a project file now are searchable with Find in Files
  • Opening from the error list if a project authoring error is triggered

Additionally, .NET SDK-style projects will now use the new Integrated Console experience for

F5

and

ctrl + F5

on console apps. This unifies the experience when launching console applications from Visual Studio:

  • For

    F5

    , the console window will not automatically close when the app is finished executing. You no longer need to add

    Console.Read()

    calls to your console apps.
  • For

    ctrl + F5

    , the console window will be re-used in subsequent runs of your app. You no longer need to close loads of console windows.

The new console window can be closed automatically by pressing a key when it is open or by selecting the option under Tools > Options > Automatically close the console when debugging stops.

Support for License Expressions and License Files has now been added to project property pages. This aligns with changes to deprecate

licenseUrl

in NuGet.

Performance improvements
  • The scalability of large solutions has been significantly improved, allowing the use of much larger .NET Core solutions than before.
  • Solution load times for large projects have been significantly reduced, as has the CPU and memory usage when loading them.
Feature parity with non-.NET Core projects
  • A long-standing issue where configuration changes were not respected at design-time, forcing a project reload, has been addressed.
  • It is now possible to Go to definition from Razor to C# in ASP.NET Core projects.
  • There is now support for AvailableItemName Items.
  • There is now support for automatic nesting of dependent files which are added to the project via globbing.
  • Support for XamlAppDef has been added by William Kent.

You can find a full list of issues and pull requests in the 16.0, 16.0 Preview 2, 16.0 Preview 3, and 16.0 Preview 4 milestones.

.NET Productivity
  • .NET refactorings and codefixes:

    • Sync Namespace and Folder Name
    • Pull members up refactoring with dialog options
    Pull Members Up dialog
    • Wrap/indent/align lists of parameters/arguments
    • Convert anonymous type to tuple
    • Use expression/block body for lambda
    • Invert conditional expressions and logical operations
    • Automatically close block comment on “/”
    • Convert to compound assignment
    • Fix Implicitly-typed variables cannot be constant
    • Auto-fixer to replace

      @$"

      with

      $@"

      when typing interpolated verbatim string
    • Completion for

      #nullable enable|disable
    • Fix for unused expression values and parameters
    • Fix for allowing Extract Interface to remain in the same file
  • Categorize references by Read/Write.

  • Add Editorconfig when_multiline option for csharp_prefer_braces.

  • New classification colors are available from the .NET Compiler Platform SDK (aka Roslyn). New default colors, similar to the Visual Studio Code colors, are gradually being rolled out. You can adjust these colors in Tools > Options > Environment > Fonts and Colors or turn them off in Environment > Preview Features by unchecking the Use enhanced colors check box. We’d appreciate hearing feedback on how this change affects your workflow.

JavaScript Debugging in ASP.NET projects
  • If you have added a new Google Chrome browser with custom arguments using the “Browse with…” menu for your ASP.NET project, Visual Studio will now enable JavaScript debugging for your application when debugging is started. Your custom launch arguments for Google Chrome will be applied when launching Chrome.
ASP.NET & Azure Functions tooling
  • Visual Studio 2019 comes with a new experience for creating new projects. When creating new ASP.NET projects specifically, Visual Studio offers additional dialogs that surface ASP.NET specific choices. These additional dialogs have been updated to match the visual style of the rest of the experience.
  • For a while now, publish credentials in Visual Studio are encrypted and stored in the publish profile user file so you don’t have to re-enter them every time you publish your application. User files in general are excluded from source control by default because they are likely to contain secret and/or personal information that should not be shared. Up until now, if a publish profile for an Azure Functions project was checked into source control but the user file was not, the publish credentials were missing and the publish profile could not be re-used. Now, we allow for the credentials to be edited and a new user file to be created so that the publish profile can be re-used.
Performance Wizard

In Visual Studio 2019, the profiling experiences that were available in the Performance Wizard have been moved to the Performance Profiler. You can find the CPU Usage Tool for sampling, and instrumentation in the Instrumentation tool in the Performance Profiler. With this change the Performance Wizard is no longer needed and has been removed from Visual Studio 2019. Additionally, the sampling option in the VS Performance command line tools have been removed, a replacement command line tool will be released in an upcoming preview.

Test Tools
  • You can now right-click on tests, test classes or test projects in the Solution Explorer to run or debug tests.
  • Test runs now auto-detect what processor architecture is set in the project properties.
  • OSS UI test tools such as Selenium and Appium have gained momentum and have a strong community backing. Because these frameworks have become industry standards, we deprecated Coded UI test for automated UI-driven functional testing. Visual Studio 2019 will be the final version of Visual Studio with Coded UI test features. We recommend using Selenium for testing web-applications and Appium with WinAppDriver for testing desktop and UWP apps.
  • Visual Studio 2019 will be the last version of Visual Studio with load test features. For customers requiring load testing tools, we recommend using alternate load testing tools such as Apache JMeter, Akamai CloudTest, Blazemeter.
  • In Visual Studio 2019, some test window APIs that were previously marked public but were never officially documented have been removed. They were marked deprecated in Visual Studio 2017 to give extension maintainers an early warning. To our knowledge, very few extensions have taken a dependency on these APIs. These APIs include IGroupByProvider, IGroupByProvider, KeyComparer, ISearchFilter, ISearchFilterToken, ISearchToken and SearchFilterTokenType. If this change affects your extension, please let us know by submitting an issue on Developer Community.
Visual Studio Kubernetes Tools

The Visual Studio Kubernetes Tools, which were previously available as a separate extension for Visual Studio 2017, are now integrated into the Azure development workload in Visual Studio 2019.

Adding Kubernetes support to a new project

To add Kubernetes support to a new project, open Visual Studio and select the Create a new project option. In the Create a new project window, search for Kubernetes and select the Container Application for Kubernetes project template.

Click Next and enter a project name, location, and solution name. Then, click Create. Select the ASP.NET Core application template you want to use for your project and click OK. Visual Studio will automatically create a Dockerfile and Helm chart that you can use to build and deploy your new application to a Kubernetes cluster. You can modify these artifacts as needed.

Adding Kubernetes support to an existing project

You can also add support for Kubernetes to an existing ASP.NET Core application. To do this, open the project in Visual Studio 2019. In Solution Explorer, right click on the project, point to Add, and click Container Orchestrator Support.

In the Add Container Orchestrator Support dialog, choose Kubernetes/Helm and click OK. Visual Studio will automatically create a Dockerfile and Helm chart (in a folder named charts) that you can use to build and deploy your application to a Kubernetes cluster. If either of these artifacts are already in place, they will not be overwritten. You can modify these artifacts as needed.

Creating a publicly accessible endpoint

When you add Kubernetes support to a new or existing project, Visual Studio will ask you if you want to create a publicly accessible endpoint for your application.

If you click Yes, Visual Studio will configure the Helm chart for your application to create a Kubernetes ingress object when the application is deployed to a Kubernetes cluster. You can change this option at any time by modifying the Helm chart.

Debugging your application in Azure Kubernetes Service

Once you have added Kubernetes support to a new or existing project, you can easily build, run, and debug your application in a live Azure Kubernetes Service (AKS) cluster, using a feature called Azure Dev Spaces. This is useful for testing your project in the context of an actual Kubernetes cluster or for debugging a service that is part of a much larger application without having to replicate the entire application locally. Azure Dev Spaces also includes functionality that allows your development team to share an AKS cluster. For more information on Azure Dev Spaces, see the Azure Dev Spaces documentation. To get started, ensure that Azure Dev Spaces is selected as the debug launch target in Visual Studio.

Before launching your project in Dev Spaces for the first time, configure the Azure subscription and AKS cluster that you wish to use. Also, select the space where you wish to run the project.

Typically, your team runs the latest stable version of the entire application in the default space. Then, you run your version of the service you are working on in a child space of the default space. There is now no need to run the other services in the child space; Dev Spaces automatically routes calls from your service to the stable versions of the services running in default. For more information on how to set this up, see the team development tutorials in the Azure Dev Spaces documentation. Once you have selected the correct subscription, cluster, and space, click OK to proceed with the Dev Spaces configuration. If you select a cluster that does not already have an associated Dev Spaces controller, click OK in the following dialog box to create one automatically.

Controller creation takes about 2 minutes. You can click on the Background Tasks button in the lower left corner of the Visual Studio window to see the status.

Once you have a Dev Spaces controller ready to go, press F5 or click the Azure Dev Spaces debug button on the toolbar to debug your project in AKS.

Dev Spaces will synchronize your code to Azure, build a container image containing your code, and deploy it to your AKS cluster using the Helm chart defined in your project. Visual Studio will open up a remote debug connection to the service running in the cluster so you can interact with it just as you would when debugging a service running locally.

Mobile Development with Xamarin

This release includes improvements to workload size and Android build performance and reliability, as well as enhancements for Xamarin.Android and Xamarin.Forms productivity.

  • The Xamarin workload is now just 7.69GB, a 2x reduction from Visual Studio 2017 version 15.9 and a 3x improvement over version 15.7.
  • The IntelliCode extension now supports Xamarin.Forms XAML.
File > New Project

We made performance improvements aimed at reducing the time it takes to create a new Xamarin project so you can start building your apps faster. We also now include the NuGet packages used by the templates as part of the workload installation in order to reduce package restore time, especially in low bandwidth or offline situations. These improvements reduce the time for a new Xamarin project to be completely loaded and restored by almost 50% in some cases.

Build progress indicator

You can now see more detailed build progress information when building your projects. Clicking the background tasks icon in the bottom left corner during a build will display the current build target that is running. This can be useful for determining if the build is still running but a target is taking a long time to complete.

Xamarin.Forms Previewer’s Basic Preview mode

You no longer have to build your project for the Xamarin.Forms XAML Previewer to show you a preview of your code! If you have custom controls in your XAML file, you might need to build your project to preview those, or opt them into design time rendering.

Xamarin.Forms Previewer device drop-down

You can now swap between different Android and iOS devices to preview your Xamarin.Forms XAML on using our new device drop-down menu.

Xamarin.Forms Property Panel

You can now edit the most common attributes of Xamarin.Forms controls, cells, and layouts in a property panel and see those changes reflected immediately in your XAML.

Xamarin.Forms Shell template

We updated the Xamarin.Forms templates to use the latest Xamarin.Forms release and also added a new template option for a Xamarin.Forms Shell app. Shell aims to reduce the complexity of apps while increasing developer productivity and focusing on rendering speed and memory consumption. This template gives you a bootstrapped Shell app for Android and iOS.

Android Build performance and reliability

In Visual Studio 2017 version 15.9 and Visual Studio for Mac 7.7, we made initial build performance and build correctness improvements. In Visual Studio 2019 and Visual Studio for Mac 7.8, we made building and deploying even faster.

  • You will now make use of Android’s next generation packaging tooling. To enable this feature, add an MSBuild flag in your project’s

    .csproj

    :

    • aapt2 divides Android packaging into two steps: Compile and Link. This improves performance for incremental builds and provides earlier error reporting. For example, if there are changes in a single file, you only need to recompile that file.


      True

  • aapt2 divides Android packaging into two steps: Compile and Link. This improves performance for incremental builds and provides earlier error reporting. For example, if there are changes in a single file, you only need to recompile that file.
  • By enabling this tool in your projects, you enable enhanced performance at both build time and runtime. For more details on these properties, see our documentation on the Build Process in Xamarin.Android.
Android Emulator improvements

In Visual Studio 2019, Android emulator images are easier to create. We’ve also continued to work with the Windows team in the Windows 10 October 2018 Update, version 1809, to improve the performance of the Android emulator when running on Hyper-V.

  • New users can create their first image by simply pressing the run icon.
  • Our emulator acquisition experience automatically determines the best configuration for your setup and takes advantage of hardware acceleration (with Intel HAXM or Hyper-V) and quick boot by default.
  • When you want to create another image, you can select Create Android Emulator from the dropdown to open the Android Device Manager.
Speed up your build times with our improvements for build in Xamarin.Android

We have released a set of initial build performance improvements. As of today, Xamarin.Android 9.1.1+ includes significant build performance improvements in comparison to the previous release. Check out our Xamarin.Android 15.9 vs. 16.0 build performance comparison for more details.

Enhanced Fast Deployment for Xamarin.Android

Fast Deployment has up until now provided faster incremental deployment times by skipping over rebuilding or redeploying the Android package (.apk file) in scenarios where no changes have been made to any assets, resources, shared native libraries packaged within the app, or user-defined classes that inherit from

Java.Lang.Object

.
Enhanced Fast Deployment expands support for fast deployment to cover both shared native libraries and classes that inherit from

Java.Lang.Object

. Fast deployment builds that use these new enhancements will only need to generate a new .apk file in a limited number of scenarios, such as when the AndroidManifest.xml file changes due to addition of a new

Android.App.Application

or

Activity

subclass.
These enhancements are not yet enabled by default in the current preview. To enable them, set the

$(AndroidFastDeploymentType)

MSBuild property to

Assemblies:Dexes

in your .csproj file:


Assemblies:Dexes

Next-generation Dex Compiler(d8) and Code Shrinker(r8) support in Xamarin.Android

Xamarin.Android now supports the latest Android dex compiler(d8) and code shrinker (r8).
To enable these features, set the

$(AndroidDexTool)

and

$(AndroidLinkTool)

MSBuild property to

d8

and

r8

respectfully in your .csproj file

  • d8 is a next-generation dex compiler that runs faster and produces smaller .dex files with better runtime performance.


d8

  • r8 is a new tool for shrinking and minification that converts Java bytecode to optimized dex code that replaces the need for ProGuard.


r8

For more details on d8 and r8, check out our documentation.

Xamarin.Android Designer enhancements

We have made a number of productivity enhancements to the interactions in Split View.

  • Drag and drop directly from the toolbox to the source editor to help quickly scaffold your Android layouts.
  • Select elements directly from their XML definition span in the source editor. We implemented this by synchronizing the caret position with the corresponding Android view, allowing you to quickly access an element’s properties in the property panel right from the editor.
  • Use an inline color preview to your XML code so you can see what colors are being used in your controls.
  • Use our quick info feature by hovering over a value to find out more about it, such as where it’s defined or what the hexadecimal value for the color is.
Xamarin.Android Designer improvements with initial support for constraint layouts

We’ve begun an effort to improve startup speed of the Android Designer. As part of this effort, we have also improved the messaging that the designer provides while it is loading.

Alongside these improvements, the Android Designer now natively supports Android Pie (9.0) and provides autocompletion for

ConstraintLayout

attributes.

Get better XML IntelliSense and Commenting optimizations with the Xamarin.Android Designer

When using IntelliSense to add a widget to a layout, a full snippet experience is now provided so that required attributes can be supplied from the start. We have added smart commenting and uncommenting for Android XML layouts.

Be more productive by using Go-To-Definition and use XML IntelliSense within Android resource files and AndroidManifest.xml

You can now Ctrl + Click on resource URLs to navigate to the file or line where they are defined.

IntelliSense/Autocompletion is now supported for other Android XML files other than layouts (colors, strings, drawables, menu, Android manifest, etc.).

Universal Windows Platform
  • The IntelliCode extension now supports XAML.
  • To reduce Visual Studio setup complexity and size, Windows Phone emulators have been removed from Visual Studio installation. You will now need to download the emulators manually.
  • XAML design time tooling for UWP apps targeting Windows 10 SDKs before the Windows 10 Fall Creators Update (build 16299) has been removed. Retarget your applications to Windows 10 version 1709 or higher to use the XAML Designer, or use the XAML editor.
  • UWP test projects using

    project.json

    to define NuGet dependencies are no longer supported. You must upgrade your project to use the new

    PackageReference

    format.
  • UWP JavaScript apps are no longer supported in Visual Studio 2019. You cannot create or open JavaScript UWP projects (files with extension

    jsproj

    ). You can learn more via our documentation on creating Progressive Web Apps (PWAs) that run well on Windows.
  • You can continue to attach to JavaScript UWP apps as before, however the JavaScript profiling tools (Network ,CPU and Memory Profiler) are no longer available in Visual Studio 2019.
Office Tools Template Updates

In Visual Studio 2019, we made a few changes to the Office, SharePoint, and VSTO templates.

  • The SharePoint 2019 templates that were added in Visual Studio 2017 15.9 are also available in Visual Studio 2019.
  • We have removed support for SharePoint Sequential Workflow or State Machine Workflows. While you will not be able to create or open these workflows in Visual Studio 2019, you can continue to edit them in previous releases of Visual Studio.
  • Office 2010 templates will no longer be available. However, you can still open existing Office 2010 projects in Visual Studio 2019.
  • The Office 2013 and 2016 templates have been renamed to reflect that they support Office 2013 and above.
Team Explorer and Azure DevOps

We are releasing a new, streamlined, developer-centric experience when connecting Team Explorer to an Azure DevOps project.

  • Focus on relevant work items by filtering and pivoting your view based on work items assigned to you, ones that you’re following, ones where you’re mentioned in the discussion, and ones based on your activity.

    • Within each view, you can create a work item inline, perform simple inline edits, mark a work item as complete, and associate a work item to pending changes.
  • Create a local branch from a work item which will automatically relate the work item to the changes made to that local branch. This is the default experience. Should you want to switch to the legacy experience, you can by setting the Work Items experience in Visual Studio. Note that this new experience is only true for Git repos. The new experience for TFVC repos will available in a following update.

    *Azure DevOps Work Item Hub*
  • Search for work items when doing a #mention in the pending changes commit message. For more details, see the View and add work items using the Work Items page.

    *Azure DevOps #mentions*
  • Support for Microsoft Project has been removed from the Team Foundation Server Office Integration 2019 plug-in for Visual Studio 2019 due to a low adoption rate in Azure DevOps. You will now need to export your work items to Excel and manually paste them into Project.

  • Support for PowerPoint has been removed from the Team Foundation Server Office Integration 2019 plug-in for Visual Studio 2019. However, users can still create storyboards in PowerPoint and link them manually to work items in Azure DevOps.

Application Insights and HockeyApp
  • The Application Insights Trends window has been removed in Visual Studio 2019 in favor of alternatives that are more feature-rich. Instead, you can use the Application Insights Search window in Visual Studio or the rich set of diagnostics tools in Application Insights in the Azure portal.
  • The wizards for adding the HockeyApp SDK and creating new beta distributions have been removed. We instead recommend using Visual Studio App Center, the successor to HockeyApp. You can still use HockeyApp normally, except without these shortcuts in Visual Studio.

Visual Studio 2019 version 16.9.5

released May 11, 2021

Issues Addressed in this Release:

  • Fixed an issue where Office tooling did not work as expected when using exports.
  • Fixed a Visual Studio 2019 crash that occurred during certain virtual calls between x64 and ARM64EC DLLs.
  • Resolved false-positive when running multi-threaded ASan-instrumented code.
  • Fixed a project failure producing the error “HRESULT E_FAIL has been returned from a call to COM component”.
  • Fixes a problem when opening a C++ file on startup that would occasionally cause Visual Studio 2019 to stop responding.
  • Fixed an issue with CmakeSettings.json configuration of files in which new settings failed to persist.
  • Internal compiler error that was caused by analyzing a source file when the file path contains one or more non-ASCII characters has been fixed.
  • Fixed an issue in opening coverage files where one library has multiple entries in code coverage file.
  • Fixed a bug causing customers who login with non-work accounts with remote desktop enabled could result in access denial.
  • Fixed a bug causing Visual Studio 2019 to crash when developers were customizing their menus and clicked on a separator in the customize dialog.
  • Floating document windows are restored when opening a solution.
  • Fixed an issue causing updates to fail when an administrator creates a new layout of Visual Studio for deploying updates. The client machine update will fail since the layout has moved locations.
  • Fixed an issue causing a project build with fast deployment enabled will fail or deployment will take a long time.
  • Added Xcode 12.5 Support.
  • Fixed an issue causing updates to fail when an administrator creates a new layout of Visual Studio for deploying updates. The client machine update will fail since the layout has moved locations.

Security Advisory Notice

CVE-2021-27068 RCE possible when planting python.exe in nested folder

A remote code execution vulnerability exists when opening a workspace with python code and that workspace contains a python.exe in a scripts subfolder.

CVE-2021-31204 .NET Core Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists in .NET 5.0 and .NET Core 3.1 when a user runs a single file application on Operating Systems based on Linux or macOS.

From Developer Community

Developer Community has a complete list of all of items shipping in this release.

Here are some of the top voted issues released in 16.9.5:

  • Visual Studio not restoring prior open documents on solution load if closed with floating windows.
  • Incorrect C26497: The function ‘fun’ could be marked constexpr
  • CMakeSettings.json does not change variables when using dialog.
  • Clicking on divider in toolbar editor causes crash of Visual Studio 2019.
  • Building Xamarin iOS binding project not longer works in Visual Studio v16.9.
  • Message: There was an error activating the remote language server.
  • Since upgrading to 16.9.2. I’m getting an error about remote language server.
  • [accepts invalid] msvc will accept [[maybe_unused]] on an invalid location
  • Visual Studio v16.9 link.exe exits with 57009.
  • Code Generation Bug in Optimization.
  • Error adding Apple Developer Account: authentication service is unavailable.
  • ASAN runtime causes random AV’s in windows.storage.dll.
  • Visual Studio extension failed to load.
  • Visual Studio 2019 Upgrade to 16.9.4 Causes Compile/Link Error.
  • MsBuild 16.9 incremental build broken.
  • Crash in Visual Studio trying to customize a toolbar.

Visual Studio 2019 version 16.7.10

released January 12, 2021

In this Release of Visual Studio 2019 version 16.7.10

Security Advisory Notice

CVE-2021-1651 / CVE-2021-1680 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector incorrectly handles data operations.

CVE-2020-26870 Visual Studio Installer Remote Code Execution Vulnerability A remote code execution vulnerability exists when the Visual Studio Installer attempts to show malicious markdown.

CVE-2021-1723 .NET Core and Visual Studio Denial of Service Vulnerability A denial of service vulnerability exists in the implementation of Kestrel.

Visual Studio 2019 version 16.9.18

released March 8, 2022

Issues Addressed in this release:

Security Advisory Notice

CVE-2020-8927 Vulnerability A Remote code Execution vulnerability exists in .NET 5.0 and .NET Core 3.1 where a buffer overflow exists in the Brotli library versions prior to 1.0.8.

CVE-2022-24464 Vulnerability A denial of service vulnerability exists in .NET 6.0, .NET 5.0, and .NET CORE 3.1 when parsing certain types of http form requests.

CVE-2022-24512 Vulnerability A Remote Code Execution vulnerability exists in .NET 6.0, .NET 5.0, and .NET Core 3.1 where a stack buffer overrun occurs in .NET Double Parse routine.

CVE-2021-3711 OpenSSL Buffer Overflow vulnerability A potential buffer overflow vulnerability exists in OpenSSL, which is consumed by Git for Windows. Git for Windows is now updated to version 2.35.1.2, which addresses this issue.

Visual Studio 2019 version 16.11.16

released June 14, 2022

From Developer Community

  • IntelliSense issues with C++ on VS 2019 v16.11.6 or newer, including VS 2022 17.0.5, 17.0.6 and 17.1.0

Security Advisories Addressed

  • CVE-2022-30184 .NET Information Disclosure Vulnerability A vulnerability exists in .NET 6.0 and .NET Core 3.1 within NuGet where a credential leak can occur.
  • CVE-2022-24513 Elevation of privilege vulnerability A potential elevation of privilege vulnerability exists when the Microsoft Visual Studio updater service improperly parses local configuration data.

What’s New in Visual Studio 2019 version 16.9

Support Timeframe

Visual Studio 2019 version 16.9 is the fourth 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.9 will be supported with fixes and security updates through October 2022. October 2022 is one year after the release of Visual Studio 2019 version 16.11, which was declared as the final servicing baseline.

In addition, now that version 16.9 is available, version 16.7, which was the last servicing baseline, will be supported for an additional 12 months and will go out of support in April 2022. Note as well that versions 16.8 is no longer under support either. 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.9 in the downloads section of my.visualstudio.com. Refer to the latest version of the release notes or visit the Visual Studio site to download the latest supported version of Visual Studio 2019. For more information about Visual Studio supported baselines, please review the support policy for Visual Studio 2019.

Visual Studio 2019 version 16.9 Releases

  • October 11 2022 — Visual Studio 2019 version 16.9.26
  • September 13 2022 — Visual Studio 2019 version 16.9.25
  • August 9 2022 — Visual Studio 2019 version 16.9.24
  • July 12, 2022 — Visual Studio 2019 version 16.9.23
  • June 14, 2022 — Visual Studio 2019 version 16.9.22
  • May 10, 2022 — Visual Studio 2019 version 16.9.21
  • April 19, 2022 — Visual Studio 2019 version 16.9.20
  • April 12, 2022 — Visual Studio 2019 version 16.9.19
  • March 8, 2022 — Visual Studio 2019 version 16.9.18
  • February 8, 2022 — Visual Studio 2019 version 16.9.17
  • January 11, 2022 — Visual Studio 2019 version 16.9.16
  • December 14, 2021 — Visual Studio 2019 version 16.9.15
  • November 16, 2021 — Visual Studio 2019 version 16.9.14
  • November 09, 2021 — Visual Studio 2019 version 16.9.13
  • October 12, 2021 — Visual Studio 2019 version 16.9.12
  • September 14, 2021 — Visual Studio 2019 version 16.9.11
  • August 10, 2021 — Visual Studio 2019 version 16.9.10
  • July 13, 2021 — Visual Studio 2019 version 16.9.9
  • June 15, 2021 — Visual Studio 2019 version 16.9.8
  • June 08, 2021 — Visual Studio 2019 version 16.9.7
  • May 18, 2021 — Visual Studio 2019 version 16.9.6
  • May 11, 2021 — Visual Studio 2019 version 16.9.5
  • April 13, 2021 — Visual Studio 2019 version 16.9.4
  • March 30, 2021 — Visual Studio 2019 version 16.9.3
  • March 16, 2021 — Visual Studio 2019 version 16.9.2
  • March 09, 2021 — Visual Studio 2019 version 16.9.1
  • March 02, 2021 — Visual Studio 2019 version 16.9.0

Visual Studio 2019 Archived Release Notes

  • Visual Studio 2019 version 16.8 Release Notes
  • Visual Studio 2019 version 16.7 Release Notes
  • Visual Studio 2019 version 16.6 Release Notes
  • Visual Studio 2019 version 16.5 Release Notes
  • Visual Studio 2019 version 16.4 Release Notes
  • Visual Studio 2019 version 16.3 Release Notes
  • Visual Studio 2019 version 16.2 Release Notes
  • Visual Studio 2019 version 16.1 Release Notes
  • Visual Studio 2019 version 16.0 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:

  • Available Today! Visual Studio 2019 v16.9 and v16.10 Preview 1
  • Visual Studio 2019 v16.9 Preview 3 is Available Today!
  • Visual Studio 2019 v16.9 Preview 2 and New Year Wishes Coming to You!
  • Visual Studio 2019 v16.8 and v16.9 Preview Available Today
  • New Features in Visual Studio 2019 v16.8 Preview 3.1
  • Visual Studio 2019 v16.8 Preview 2 Releases New Features Today!
  • Visual Studio 2019 v16.7 and v16.8 Preview 1 Release Today!
  • Visual Studio 2019 v16.7 Preview 2 Available Today!
  • Exciting new updates to the Git experience in Visual Studio
  • Releasing Today! Visual Studio 2019 v16.6 & v16.7 Preview 1
  • Visual Studio 2019 version 16.6 Preview 2 Releases New Features Your Way
  • Visual Studio 2019 version 16.5 is now available!
  • ‘Tis the Season for Visual Studio 2019 v16.4 Release
  • Visual Studio 2019 v16.4 Preview 2, Fall Sports, and Pumpkin Spice
  • .NET Core Support and More in Visual Studio 2019 version 16.3 – Update Now!
  • Visual Studio 2019 version 16.3 Preview 2 and Visual Studio 2019 for Mac version 8.3 Preview 2 Released!
  • Visual Studio 2019 version 16.2 and 16.3 Preview 1 now available
  • Visual Studio 2019 version 16.2 Preview 2
  • Visual Studio 2019 version 16.1 and Preview 16.2 Preview
  • Visual Studio 2019: Code faster. Work smarter. Create the future.

Visual Studio 2019 version 16.0.3

released April 30, 2019

What’s New in Visual Studio 2019 version 16.0.3

  • Visual Studio Tools for Kubernetes now supports the latest Azure Dev Spaces.

Issues fixed in Visual Studio 2019 version 16.0.3

  • Delete option is missing from solution explorer context menu in Xamarin Forms Android projects.
  • Xamarin.Android: Can’t select target framework 28 in Android Manifest settings.
  • Could not load file or assembly ‘Microsoft.VisualStudio.Web.PageInspector.Loader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ or one of its dependencies. The system cannot find the file specified.
  • “There was an error running the selected code generator” when trying to create a new view.
  • Android Berechtigungsliste ist leer-Android permission list is empty.
  • Missing icons for .axml files in Visual Studio 2019.
  • axml icons are not displayed.
  • Visual Studio extensions may fail to install attempting to overwrite core NuGet files.
  • C# switch statement on a constant expression may produce bad compiler errors.

Visual Studio 2019 version 16.11.5

released October 12, 2021

Issues Addressed in this Release

Security Advisories Addressed

CVE-2020-1971 OpenSSL Denial of Service Vulnerability

A potential denial of service vulnerability exists in OpenSSL library, which is consumed by Git.

CVE-2021-3449 OpenSSL Denial of Service Vulnerability

A potential denial of service vulnerability exists in OpenSSL library, which is consumed by Git.

CVE-2021-3450 OpenSSL Denial of Service Vulnerability

A potential flag bypass exists in OpenSSL library, which is consumed by Git.

CVE-2021-41355 .NET Disclosure Vulnerability

An Information Disclosure vulnerability exists in .NET where System.DirectoryServices.Protocols.LdapConnection sends credentials in plain text on Linux.

Visual Studio 2019 version 16.7.5

released September 29, 2020

In this Release of Visual Studio 2019 version 16.7.5

  • Incorrect code gen on ARM64 with vector math (DirectXMath.h)
  • Faulty type casts : VS.2019 V16.7.1, native C++
  • C++ builds with Windows SDK 8.1 fail after upgrade to Visual Studio 16.7
  • With VC++ 16.7 ABI change in vtable.
  • fatal error C1001: Internal compiler error with 16.7.0
  • CET/EHCONT Exception handling metadata is broken in vcruntime140.dll. This fix may have an increased chance of requiring a reboot of the machine in order to install an updated VC++ Redistributable package.
  • PGO switch MEMMAX seems not respected
  • [19.26.28900] New compiler causing possible bad codegen
  • Code analysis crashed with buffer underflow
  • Fixed a bug in the C++ compiler when importing classes with methods containing a combination of default arguments and [params] / [ParamArray] argument list.

Visual Studio 2019 version 16.0.2

released April 18, 2019

Issues fixed in Visual Studio 2019 version 16.0.2

  • The solution name in title bar is truncated.
  • Missing interpolation in warning when packaging Cloud Service projects.
  • Visual Studio will no longer show an error message on startup after you reset or import settings in certain cases.
  • Accessibility issues in Cloud Service projects where wrong inputs in the diagnostics configuration window are not read by screen readers have been fixed.

Visual Studio 2019 version 16.11.34

released February 13th, 2024

Issues addressed in this release

Developer Community

  • fatal error C1001: Internal compiler error
  • VS2022 is using too old node.js version 16 – any plans to upgrade?

Security advisories addressed

  • CVE-2024-0057 A security feature bypass vulnerability exists when Microsoft .NET Framework-based applications use X.509 chain building APIs but do not completely validate the X.509 certificate due to a logic flaw.

Visual Studio 2019 version 16.0.7

released August 13, 2019

Issues fixed in Visual Studio 2019 version 16.0.7

  • Fixed a performance regression during breakpoint hit and stepping.
  • Fixed a performance regression when IntelliTrace.exe starts up.
  • Fixed a bug causing a crash when unable to reach the TFS.
  • Fix for HRESULT E_FAIL build error in some C++ projects when upgrading to 16.0.1

Security Advisory Notice

CVE-2019-1211 Git for Visual Studio Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists in Git for Visual Studio when it improperly parses configuration files. An attacker who successfully exploited the vulnerability could execute code in the context of another local user. To exploit the vulnerability, an authenticated attacker would need to modify Git configuration files on a system prior to a full installation of the application. The attacker would then need to convince another user on the system to execute specific Git commands. The update addresses the issue by changing the permissions required to edit configuration files.

**CVE-2019-1301: Denial of Service Vulnerability in .NET Core

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

The update addresses the vulnerability by correcting how the .NET Core web application handles web requests.

Keywords searched by users: visual studio 2019 16.0

Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.3 Preview 2 And Visual Studio For Mac Version  8.3 Preview 2 Released! - Visual Studio Blog
Visual Studio 2019 Version 16.3 Preview 2 And Visual Studio For Mac Version 8.3 Preview 2 Released! – Visual Studio Blog
Rò Rĩ Phiên Bản Visual Studio 2019 (Version: 16.0.0 Preview 1) | Devmaster
Rò Rĩ Phiên Bản Visual Studio 2019 (Version: 16.0.0 Preview 1) | Devmaster
Visual Studio 2019 Version 16.4 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.4 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.11 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.11 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Download Microsoft Visual Basic 2019-16.0 For Windows - Filehippo.Com
Download Microsoft Visual Basic 2019-16.0 For Windows – Filehippo.Com
Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.8 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.8 Release Notes | Microsoft Learn
Performance Improvements In Visual Studio 2019 - Visual Studio Blog
Performance Improvements In Visual Studio 2019 – Visual Studio Blog
Visual Studio 2019 Version 16.8 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.8 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Visual Studio 2019 Version 16.0 Release Notes | Microsoft Learn
Visual Studio - Wikipedia
Visual Studio – Wikipedia
Install Visual Studio 2019 (Cài Đặt Visual Studio Lập Trình Windows Form  C#) - Youtube
Install Visual Studio 2019 (Cài Đặt Visual Studio Lập Trình Windows Form C#) – Youtube
Rò Rĩ Phiên Bản Visual Studio 2019 (Version: 16.0.0 Preview 1) | Devmaster
Rò Rĩ Phiên Bản Visual Studio 2019 (Version: 16.0.0 Preview 1) | Devmaster

See more here: kientrucannam.vn

Trả lời

Email của bạn sẽ không được hiển thị công khai. Các trường bắt buộc được đánh dấu *