• Custom Project Template Not Found
• msvsmon.exe crashes when hitting breakpoint in native C++ code
• Search for a folder in solution explorer, then click home or the X in the search box. The view is reset.
• External Tools argument current line is always zero.
• Can't create v3 Function project.
• Access violation reading location 0xFFFFFFFFFFFFFFFF. after updating to VS 2019 Update 16.4.3
• Cannot create function app under 16.4
• MSVC2019 generates AVX-512 instruction in AVX/AVX2 mode
• Bad code generation with rsqrtss (register clobber)
• Visual Studio 2019 Debugger crashes when viewing FastLink callstack.
• C#: Fixed a crash when an attribute constructor is decorated with itself and Nullable Reference Types is enabled.
• Fixed an optimization-analysis bug where we lose track of alias information for arrays of indeterminate length (declared as extern int a[]) when we unroll loops, leading to possible incorrect dead-store removal. 

Visual Studio Code doesn't support solution files, whereas Visual Studio does. In Visual Studio we use solution files to link multiple projects together, and at first I thought that this was going to be a deal breaker for Visual Studio Code - but it's not at all. Many people aren't aware that Visual Studio Code, although lightweight, is a powerful editor that can do most of the things you need. 

These are the customer-reported issues addressed in 15.8.5:

• Debugger tooltip does not expand in Xamarin.iOS debugging session.
• Debugger won't let me leave execution point (Android).
• After updating to 15.8.1, data tip does not show when debugging.
• Debugger data tip does not expand [Editor].
• Exception:MSB0001: Internal MSBuild Error: Already registered for build-time.
• Wrong path to resource in manifest for ClickOnce after upgrading to VS 15.8.1.
• ClickOnce Manifest error in 15.8.
• ClickOnce Publish is missing certain references.
• ClickOnce: Language file copied to wrong location.
• Reference missing in the ClickOnce publish folder.
• Compiling non-.NET SDK style F# projects results in an internal MSBuild error unless MSBuild parallelism is set to 1.
• F# is not NGEN'd in Visual Studio.
• F# deploys the FSharp.Core 4.5.0.0 binary in the 4.4.3.0 location.

Details of What's New in 15.8.5

Visual Studio Tools for Xamarin

Visual Studio Tools for Xamarin now supports Xcode 10, which allows you to build and debug apps for iOS 12, tvOS 12, and watchOS 5. See how to get ready for iOS 12 and our introduction to iOS 12 for more details on the new features available. 

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 Notices

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. 

Logging is a big part of software development for many years now. One can argue that a logging mechanism is a must-have part of any application or library. I would agree with that statement. Logging has a crucial part to play in a scenario where you can’t use interactive debugging (that is, attaching a debugger like Visual Studio). It allows us to investigate errors after the problem already happened. In some cases, like Production Debugging, logs might be the only information you have. 

Visual Studio extension that shows the text of a string resource (.resx) when used inline in code. 

Better late than never! Some of you may have noticed that C# 7.3 already shipped, back in Visual Studio 2017 update 15.7. Some of you may even be using the features already. 

Top Issues Fixed in Visual Studio 2019 version 16.4.1

• Fixed "the write operation failed. you must first acquire write access from dataschemamodelcontroller" error trying to publish a database
• Fix ExecutionEngineException exceptions when using SignalR on iOS devices in some configurations
• Runtime Fix "CEE_RET: value type stack" crash when interpreter was enabled with some libraries
• TypeScript 3.7.3 is now included by default, which contains several fixes for issues that effect the JavaScript and TypeScript editing experience.
• May allow mitigation of a Per-Monitor awareness related crash in Visual Studio

Security Advisory Notice

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

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

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

CVE-2019-1352 Git for Visual Studio Remote Excecution Vulnerability due to unawareness 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

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

CVE-2019-1486 Live Share extension URL redirection vulnerability

GitHub Issues

The GitHub Issues integration allows you to search and reference your issues from the commit message box in VS, in response to this suggestion ticket. You can reference an issue or a pull request by typing # or clicking on the # button in the lower right side of the commit message text box. If you weren't already authenticated to access related issues, you will now be prompted to sign in to take advantage of this feature.

Line Unstaging

To continue improving our line-staging (aka interactive staging) feature, we've added unstage. You can now use the tool tip option to unstage changes, line by line, as requested here Unstage individual lines and hunks in a file - 4 votes

Arm64

We continue to build native support for Arm64 on Windows 11 for the most popular developer scenarios. We now support the .NET Multi-platform App UI (MAUI) workload on Arm64 Visual Studio.

C++

• Available as a preview feature, you can now view Unreal Engine logs without leaving VS. To see the logs from the Unreal Engine Editor, click View > Other Windows > UE Log. To filter your logs, click on the "Categories" or "Verbosity" dropdowns. Since this is an experimental feature, feedback is greatly appreciated.
• You can now import STM32CubeIDE projects for embedded development within Visual Studio with File > Open > Import STM32CubeIDE project. This generates a CMake project with device flashing and debugging settings for STLink. You must have the STM32CubeIDE installed with the board support package for your device. More details available here.
• You can use the new CMake Debugger to debug your CMake scripts at build time. You can set breakpoints based on filenames, line numbers, and when CMake errors are triggered. Additionally, you can view call stacks of filenames and watch defined variables. Currently, this only works with bundled CMake, and projects targeting WSL or remote machines are not supported yet. We are actively working to add more support to the CMake debugger, and feedback is greatly appreciated.