Reasons Why .NET Core 5 Is Not Available In Visual Studio 2019 

it will be available in .NET Core 3.1 which ships with Visual Studio 2019 16.4 

Security Advisory Notice for 16.6.2

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

Top Issues Fixed in Visual Studio 2019 version 16.6.2

• Visual Studio 2019 16.60 hang at run or build when modified not saved in C++/CLI project
• An unhandled exception of type 'System.NullReferenceException' occurred in Microsoft.VisualStudio.DesignTools.WpfTap.dll
• Recurring null reference when reopening documents
• "Create new project" dialog search does not find templates for third-party language providers
• IntelliSense shows that "tilde-slash" (~/) points to ASP .NET Core 3.1 project root instread of wwwroot subfolder after upgrading Visual Studio Enterprise 16.5.6->16.6.0
• Fixed a compiler error (error C2475: redefinition; 'constexpr' specifier mismatch) affecting std::atomic when compiled as C++/CX in C++17 mode.
• URL completion values and format was fixed in Razor views. App-relative URL format is now used again and the values in the URL completion list show files and folders rooted under app root, i.e. wwwroot.
• Fixed a crash when using snippets.
• Restore item templates that could be hidden by extensions.

• Fixed: Android SDK not found after upgrade to 16.2
• Fixed: VS won't start after update with message tht setup is complete.
• Fixed an issue resulting in an installer verification or manifest verification fail when user is updating through the setup UI.
• Fixed an issue that caused Visual Studio to crash or stop responding during shutdown.
• Fixed a timing-related issue while saving changed Xamarin.Android project properties or building the project that resulted in the product to stop responding.
• Fixed an issue with Visual Studio crashing when C# users typed above a namespace.
• Fixed an issue preventing SSIS packages from successfully running in some circumstances after reloading a solution. 

A Visual Studio extension that installs a short list of highly valuable extensions targeted web development. 

A Visual Studio to Visual Studio Code Snippet Converter 

Debugger for Edge by Microsoft JS Diagnostics

Install: From within Visual Studio Code, you can use Quick Open (Ctrl+P) and paste ext install debugger-for-edge then press Enter.
 

These are the customer-reported issues addressed in 15.7.3:

• VS2017 compiler creates broken debug build using Qt framework and generates 'Invalid address specified to RtlValidateHeap' error.
• Incorrect code generation for matrix multiplication.
• VS 2017 Update 7: Git History Codelens only showing entries for the past 6 months.
• UWP projects reference multiple NetStandard 2.0 dlls after 15.7.1 upgrade.
• Building C++ code in VS 15.7 with /std:c++17 breaks binary compatibility for std::_Ptr_move_cat.
• Visual Studio 15.7 stuck when opening XAML files.
• CMake configuration fails and generates message "C++ IntelliSense information may be out of date, generate the CMake cache to refresh".
• Unable to start second process for debugging.
• After update to Visual Studio 15.7.1, some test programs fail in start-up due to reading access violation.
• Missing compiler required member 'Microsoft.CSharp.RuntimeBinder.Binder.Convert'.
• Build fails after 15.7.0 update on older project using .NET 3.5 .
• Coloring, typing, tooltips and IntelliSense slow in F# in VS2017 editor.
• F# editing experience takes up to a minute for tooltips and dropdowns to display.
• Certain class member variable value are incorrectly read as zero.
• Attempt to open XAML file for the first time causes VS to sit with the "Opening the file ..." message for about 10 minutes before XAML file opens.
• Visual Studio slows down and freezes, creating work loss.
• The target "GetBuiltProjectOutputRecursive" does not exist in the project.
• Internal error with lambda C++17 after 15.7.1 update.
• UWP App is slow to return a stopped state in IDE.
• MSVC auto-vectorization produces incorrect code or incorrect results.
• Visual Studio closed debug a new instance project1, when a new debug new instance project2 has started.
• Latest update breaks "start without debugging" on multiple projects.
• UWP XAML is very very slow on open.
• XAML viewer freezes on 15.7.2 and 15.8.0 preview 1.1.
• Xamarin UI Test App project template missing.
• Xamarin project creation problem.
• Visual Studio crashes when creating new Mobile APP Xamarin.
• Unable to create Xamarin.Forms-Projects.
• Não consigo criar novos projetos Xamarin Forms - Can't create new projects Xamarin Forms.
• Blank project crash after update. 

1. Debugging WPF Applications
2. Stepping Through Code
3. Working with Debug Windows
4. Debugger Visualizers and Trace Listeners
5. XAML Debugging
6. Analyzing the UI Performances
7. Analyzing the Application Performances