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. 

Have you ever found a bug in your code and wanted to pause code execution to inspect the problem? If you are a developer, there’s a strong chance you have experienced or will experience this issue many, many times. While the short and sweet answer to this problem is to use a breakpoint, the longer answer is that Visual Studio actually provides multiple kinds of breakpoints and methods that let you pause your code depending on the context! Based on the different scenarios you may experience while debugging, here are some of the various ways to pause your code and set or manage a breakpoint in Visual Studio 2017 

These are the customer-reported issues addressed in 15.8.4:

• Constexpr function with explicit (void) parameter crashes MSVC 15.8.0 release.
• TypeScriptLspCodeActionProvider encountered an error and has been disabled.
• The 'Shared Web Components' package did not load correctly.
• Editing CSS with Browser Link enabled can crash Visual Studio.
• Service Fabric Deployment fails in 15.8.0.
• Incorrect error for constexpr pointer to members with VS2017 15.8.
• Constexpr doesn't support __declspec(dllimport) in VS2017 15.8.
• C++ VS 2017 Update 8 difference in member function pointer between C++14 and C++17 modes leads to crashes.
• TestExplorer locking up UI in latest build.
• [WebKit] "Already defined symbol" for static template member definition (regression).
• VS 15.8.0 Internal compiler error.
• Internal compiler error in constexpr function.
• Test Explorer Window remains blank with Express.
• Visual Studio 2017 fails to open on FIPS-enabled machine..
• VS2017 15.8 Internal Compiler Error 'msc1.cpp', line 1518 when evaluating simple constexpr function.
• Fatal error C1001 after update to VS 15.8.0.
• Migrating to VS2017 15.8: Internal compiler error when using constexpr functions as template parameters.
• Internal compiler error when compiling a template function with a constexpr in VC++ 15.8.0.
• Code generated by VC 15.8.1 compiler lead to crash. 

These are the customer-reported issues addressed in 15.8.3:

• Visual Studio 2017 version 15.8.2 contained a pre-release build of .NET Core SDK 2.1.401 that is incompatible with Visual Studio. We have corrected this issue with Visual Studio 2017 version 15.8.3.
• VSCppUnit test case creation failure.
• Python IntelliSense not working on Python 2.7.
• XAML designer causing Visual Studio to close unexpectedly. 

These are the customer-reported issues addressed in 15.8.2:

• Publish single file context menu item missing.
• Git network operations not working: Cannot spawn git-askpass.exe.
• "Visual C++ Resource Editor Package" load failed.
• Preview Transform gives error.
• Cannot type close brace.
• Object reference not set to an instance of an object when deploying Service Fabric project after update 15.8.0.
• "The given path's format is not supported" installation error.
• Task ExpandPriContent failed. Illegal characters in path.
• "Could not create instance of type System.Collections.Genertic.Iset'1[Signer]" installer error.
• Service fabric deployment fails in 15.8.0.
• Cannot create app package for Windows store.
• Incorrect code generation for strongly-typed resources.
• Keyboard binding for Italian layout.
• IntelliSense broken #9999.
• When working on a Unity project and Unity rewrites multiple project files, the Visual Studio Tools for Unity will now automatically reload the solution.
• The customer will now get a dialog to close Office applications if they are blocking the Visual Studio install and causing a failure of 1303. 

These are the issues addressed in 15.8.1:

• Fixed an issue where Visual Studio would close unexpectedly when a browser window was closed while debugging a Web project.

This release contains the following improvements and enhancements:

• This release now installs Java™ Development Kit 8, Update 181 (JDK version 8u181). 

These are the customer-reported issues addressed in 15.7.6:

• Visual C++ Redistributable 2017 does not report the install state in a specific registry location.
• In 15.7 users may see extensions load without all of their assets and cause VS to crash. This has been addressed for 15.7.6.
• Visual Studio 2017 version 15.7.5 crashes when opening a solution. 

These are the customer-reported issues addressed in 15.7.4:

• Green squiggles and light bulb with "Macro in skipped region" message.
• F7 does not switch to code.
• F7 does not build anymore.
• F7 build does not work.
• LINK : error : Telemetry event upload failed: 'Failed to open connection to VCTIP'.
• AXML file doesn't open after update.
• F7 no longer toggles between the designer and the code.
• XAML Editor Error: Window is not supported in WPF project.
• WinForms View.ToggleDesigner does not work as it used to.
• Toggle designer key binding lost.
• F7 does not start a new build.
• F7 no longer toggles between Designer and Code views.
• There is a problem with structure definition in C language.
• Provisioning a new SQL Server and new SQL DB in a different region than the App Service plan fails.

Git Security Vulnerability

We also fixed a security vulnerability in Git that was disclosed by the Git community. The vulnerability can lead to arbitrary code execution when a user clones a malicious repository. This blog post has more information. 

PostSharp 6.0 is the biggest refactoring since the 2.0 version released in July 2010. For a good cause: PostSharp 6.0 now runs natively in .NET Core 2.0. Previous versions of PostSharp executed only under .NET Framework at build time and the support for .NET Core was achieved by using a load of hacks that ended up being unmaintainable, warranting this big refactoring.

Let’s have a look at the new features of PostSharp 6.0 :

• Support for .NET Core 2.0-2.1 and .NET Standard 2.0.
• Support for Portable PDB.
• Support for C# 7.2.
• Ending the PostSharp versioning hell side-by-side: backward compatibility within the same major version.
• Logging: robustness to faults in the logging subsystem.
• Logging: no need to initialize before the first logged method is hit.
• Caching: preventing concurrent execution (locking).
• Visual Studio tooling: support for the new CPS-based project systems.
• GDPR compliance: we no longer collect your name and email for trial, nor use unsecure HTTP, nor use non-resettable user id hashes.