• Fixed: Error running the selected code generator :" value -1 is outside the acceptable [0,2147483647] range. Parameter name :value"
• Fixed: VS2019 will randomly hang while unloading projects
• Fixed: vcpkgsrv freezes VS on opening new cpp files
• Fixed an issue that caused Visual Studio 2019 to stop responding on shut down.
• Added error handling to prevent a crash when displaying tool windows with Per-Monitor awareness enabled. 

A few years ago, we took over maintenance and guidance for the ASP.NET AJAX Control Toolkit project. Please refer to this blog post for more information on the project and why we stepped in to assist.
As part of our ongoing commitment to the project, we’ve released an update (ASP.NET AJAX Control Toolkit v19.1.0) to address the following issues.
Improvements
- Visual Studio 2019 Support
- Security hardening: HTML-encode file names in AjaxFileUpload (#483)
 

Improved the MSBuild selection logic. The standalone instance inside OmniSharp is now preferred over VS2017, with VS2019 given the highest priority. This ensures that .NET Core 3.0 works correctly. It is also possible manually provide an MSBuild path using OmniSharp configuration, which is then always selected. (omnisharp-roslyn#1541, PR: omnisharp-roslyn#1545)

    {
        "MSBuild": {
            "MSBuildOverride": {
                "MSBuildPath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\MSBuild\\15.0\\Bin",
                "Name": "vs2017 msbuild"
            }
        }
    }

• Custom tasks with default contextType via tasks.vs.json are broken in Open Folder.
• No snapshot created for C++ native code in Memory Usage tool in the Diagnostic Tools window while debugging.
• Crash in VS 16.1.0 when pressing the link "search online".
• Fixed the issue where sometimes certain features (i.e. Find All References) in LiveShare guest session do not work.
• Fixed an issue where the devenv.exe process could hang around after shutdown of Visual Studio for up to 30 seconds. 

These are the customer-reported issues addressed in 15.9.6:

• Installation failures of the Unity Editor component in China.
• Starting a new nanoFramework project from a template.
• Deployment errors after VS2017 update.
• Android Deploy failed - Error ADB0010.
• Error in German translation: info bar "session closed unexpectedly".
• Visual Studio 2017 create offline layout problem: Failed to load from stream for non-ENU layouts.
• Extension auto-update can leave extension disabled. 

• InvalidOperationException Writing is not allowed after writer was completed
• ICE on valid code after upgrading to 16.2.0
• CPU Usage Tool context menu does not navigate
• Wrong assembly when result of conversion operator is converted to reference to base class.
• DockerUpdateComposeVsGeneratedFiles throws "Value cannot be null" ("Parameter name: path1") after updating to Visual Studio 16.3
• CPU Usage Tool contect menu does not navigate.
• InvalidOperationException Writing is not allowed after writer was completed.
• Publish doesn't work in Visual Studio 16.3.1.
• This fixes an issue with the Snapshot Debugger where customers are using MSA accounts.
• Fixed an issue where customers trying to install Microsoft.Visualstuio.Shell.15.0 NuGet package received a warning message of Framework not found.
• Fixes MSVC compiler bug involving implicit conversion from a lambda to function pointer.
• Fixed issue with Visual Studio crashing due to null reference exception.
• A fix is made to address a compiler interal error when the code has a out-of-line definition of a static data member of a nested class inside a partial specialization. 

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. 

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. 

These are the customer-reported issues addressed in 15.9.5:

• VSX1000: No enough information has been provided to MSBuild in order to establish a connection to a Remote Server.
• Visual C++ 2017 Redistributable for ARM64 is not available via visualstudio.com.
• VC Runtime Redistributable Update for VS 15.9 deletes Registry Key. This fix may have an increased chance of requiring a reboot of the machine in order to install an updated VC++ Redistributable package.
• Incorrect codegen in managed c++ with List to List assignment.
• Can't connect to mac build host after Visual Studio 15.9.4 update.
• Resource directories missed in incremental builds with AndroidAarLibrary items.
• Lots of external assembly references - JNI ERROR (app bug): local reference table overflow (max=512).
• The Unity Editor has been updated to 2018.3. For more information, please visit the Unity website.
• SSDT: We enabled SQL projects to build schemas that have non-clustered columnstore indexes on an indexed views.
• SSDT: We fixed a significant performance issue in the schema compare tool when generating a script.
• SSDT: We fixed the schema drift detection logic in the schema compare tool which forced a new comparison to reenable scripting and publishing actions.

Security Advisory Notices

• A remote code execution vulnerability exists in Visual Studio when the C++ compiler improperly handles specific combinations of C++ constructs. 

Issues Fixed in 15.9.21

• Fixed a bug where the .NET Profiling tools couldn't be installed on non-enterprise versions of Visual Studio 2017 when using an offline installer.
• Fixed C++ compiler bug where a static_cast in a decltype would evaluate incorrectly. To minimize disruptions to existing codebases, in VS2017 this fix takes effect when the (newly added) /d1decltypeIdentityConversion switch is thrown.
• New Spectre mitigation options in C++ compiler: /Qspectre-load & /Qspectre-load-cf for speculative load hardening.

Security Advisory Notices

• Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability
• A spoofing vulnerability exists when creating an Outlook Web-Addin if multi-factor authentication is enabled