Visual Studio Icon Visual Studio 2017 Preview Release Notes


| Developer Community | System Requirements | Compatibility | Distributable Code | License Terms | Blogs | Known Issues |


Important

This release is not "go-live" and not intended for use on production computers or for creating production code.

Click a button to download the newest preview version of Visual Studio 2017. For instructions on installing and updating Visual Studio 2017, see Update Visual Studio 2017 to the most recent release documentation.


What's New in 15.8

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 15.8 releases in the following posts:

Visual Studio 2017 version 15.8 Preview Releases

Visual Studio 2017 version 15.8 Announcements


Known Issues

See all existing known issues and available workarounds in Visual Studio 2017 version 15.8.

Visual Studio 2017 Known Issues


Release Notes Icon Visual Studio 2017 version 15.8 Preview 1

released May 07, 2018

Summary of What's New in 15.8 Preview 1

New Features in 15.8 Preview 1

Issues Fixed in 15.8 Preview 1

These are the customer-reported issues addressed in this release. If you are looking for a specific customer-reported issue that has been fixed in 15.8 Preview 1, visit the Developer Community.


Details of What's New in 15.8 Preview 1

C++

C++ Quick Info tooltips on macros now show what they expand to, rather than just their definition. This is particularly useful for complex macros that reference other macros as it clarifies what the macro identifier is replaced with by the preprocessor.

Visual Studio Web Tools

Library Manager is a new feature included in Visual Studio 2017. It helps you manage client-side libraries in your web projects.

Container Tools

In Visual Studio 15.8 Preview 1, we have added a new single project Docker container experience for ASP.NET Core web projects. This supplements the existing Docker Compose-based container tooling and provides a simpler, easier way to create, debug, and build Docker containers right from Visual Studio.

You can add Docker support when creating the project (Figure 1):

Enable Docker Support
(Figure 1) Enable Docker Support

Or, you can enable Docker support to an existing project through the project’s context menu in Solution Explorer (Figure 2). Once you do this, Visual Studio creates a single Dockerfile in the project. You have the option to choose either Windows or Linux.

Add Docker Support
(Figure 2) Add Docker Support

Visual Studio also adds a debugger launch profile (Figure 3) for Docker so that the project can be debugged while running within a container.

Docker Launch Profile
(Figure 3) Docker Launch Profile

If you have a solution with multiple Docker projects, by default, only one container runs when you choose to start the solution. If you wish to run multiple containers simultaneously, you can right-click on the solution in Solution Explorer and select Set Startup Projects, then Multiple startup projects, and then set the Action drop-down to Start or Start without debugging for all projects that you want to run.

Once you have your containerized project running the way you want, you can right-click on the project and select Build Docker Image to build an image locally, when ready to push to Azure Container Registry or DockerHub.

You can also add the existing Docker Compose-based functionality to an ASP.NET Core web project through the new Container Orchestrator Support option (Figure 4). Right-click on the ASP.NET Core web project in Solution Explorer, select Add > Container Orchestrator Support, and then select Docker Compose from the drop-down menu.

Add Container Orchestrator Support
(Figure 4) Add Orchestration Support

Release Notes Icon Visual Studio 2017 version 15.8 Preview 1.1

released May 08, 2018

Issues Fixed in 15.8 Preview 1.1

  • This release provides a fix that reduces memory usage and GC pressure during solution load.

Release Notes Icon Visual Studio 2017 version 15.8 Preview 1 Security Advisory Notice

updated May 08, 2018

Microsoft Security Advisory for .NET Core Denial Of Service Vulnerability

CVE-2018-0765

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core and .NET native version 2.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

Microsoft is aware of a denial of service vulnerability that exists when .NET Framework and .NET Core improperly process XML documents. An attacker who successfully exploited this vulnerability could cause a denial of service against a .NET Framework, .NET Core, or .NET native application.

The update addresses the vulnerability by correcting how .NET Framework, .NET Core, and .NET native applications handle XML document processing.

If your application is an ASP.NET Core application, developers are also advised to update to ASP.NET Core 2.0.8.


Release Notes Icon Visual Studio 2017 version 15.8 Preview 2 New Release icon

released May 31, 2018

Summary of What's New in 15.8 Preview 2

New Features in 15.8 Preview 2

Issues Fixed in 15.8 Preview 2

These are the customer-reported issues addressed in this release. If you are looking for a specific customer-reported issue that has been fixed in 15.8 Preview 2, visit the Developer Community.


Details of What's New in 15.8 Preview 2

Install

You now have the option to download all installation files before starting your installation.

  • To use this new option, select the "Download all, then install" option in the installer (Figure 1). We suggest this option if you have a slower internet connection.
  • The default option remains "Install while downloading", which downloads and installs in parallel.
Download, then install option
(Figure 1) Download, then install option

Performance

We've added an option to disable reopening documents that were open in the previous session, as reopening certain types of files or designers can delay solution load.

  • Toggle this option in Tools > Options > Projects > Solutions > General.

Debugging

When you have more than one instance of Visual Studio 2017 installed, you can now select which instance to deploy your extension to when debugging (Figure 2). That way you can develop in the e.g. the Visual Studio release channel while debugging in the preview channel.

Select your debug instance
(Figure 2) Select debug instance

Extensibility

You can now build Visual Studio extension (VSIX) projects using the Build Tools for Visual Studio 2017.

Performance Profiling (CPU Usage)

This release contains the following improvements to the CPU Usage tool of the Performance Profiler (available via ALT-F2):

  • The Call Tree view now displays asynchronous execution by logical call stack by default. You can turn off this behavior by unchecking the option "Stitch Async Code" in the Filter dropdown of the CPU Usage main view.
  • Added a Modules/Functions view which displays performance information by module (dll) and by function within a module. One can display the Modules/Functions view from the context menu available when selecting a function in the CPU Usage main view, or from the View dropdown in the Call Tree or Caller/Callee views.
  • Added 'instance indication' to the CPU Usage graph in the CPU Usage tool's main view. You can view the instances when a function is executing (for instance, on the stack) by double clicking a function listed in any of the CPU Usage views.

C++

This release has the following updates and enhancements to C++:

  • Added Add > New Item template for generating a .clang-format file following the coding convention specified for ClangFormat in Tools > Options. If the Visual Studio convention is selected, the generated file tries to match the user's current Visual Studio formatting configuration from Tools > Options.
  • Updated the shipped clang-format.exe version to 6.0.0.
  • Templates to simplify adding configurations to CppProperties.json.

Visual Studio Tools for Xamarin

This release contains the following updates for Xamarin:

Hyper-V Android emulator support

This release contains a preview of the Google Android emulator that is compatible with Hyper-V which is available in the Windows 10 April 2018 Update (Figure 3). This enables you to use Google's Android emulator side-by-side with other Hyper-V based technologies, including Hyper-V virtual machines, Docker tooling, the HoloLens emulator, and more. Mobile app developers who use Hyper-V now have access to a fast Android emulator that always supports the latest Android APIs, works with Google Play Services out of the box, and supports all features of the Android emulator, including camera, geolocation, and Quick Boot.

Screenshot of both the Google Android emulator and HoloLens emulator running at the same time.
(Figure 3) Google Android Emulator and HoloLens emulator
Minimum support for Xamarin.Mac binding projects

We have added minimum support for Xamarin.Mac binding projects in Visual Studio 2017. This enables Visual Studio to load and recognize Xamarin.Mac binding projects as supported. You can also build Xamarin.Mac binding projects, however the build process is performed locally without using the native Mac tool chain so the generated IL assemblies cannot be used for running or debugging in apps.

F# and F# Tools

We focused on performance for F# tools when using .NET SDK-style projects and F# compiler fixes.

F# language
  • You can once again inherit from FSharpFunc. This was previously disabled in F# 4.1.
  • We fixed a bug where you could get an AccessViolationException with seq { } when using yield! with multiple collected sequences in release mode.
  • We fixed a bug in MailboxProcessor.TryReceive() where it could cause a spike in CPU usage on first invocation.
  • Enum pattern match warnings now print out a field name of an uncovered code, by John Wostenberg.
F# tools
  • We significantly improved the time to semantic colorization in newly-opened F# files in .NET SDK projects that are not using multi-targeting.
  • We significant improved IntelliSense performance for F# in .NET SDK projects that are not using multi-targeting.
  • Completion data in IntelliSense is now saved for up to two minutes, allowing descriptions in the tooltip to remain for up until that point per invocation.

Feedback

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 Feedback Icon icon is located in the upper right-hand corner. You can track your issues in the Visual Studio Developer Community, where you can ask questions and find answers. You can also make a product suggestion through UserVoice or get free installation help through our Live Chat support.


Blogs

Take advantage of the insights and recommendations available in the Developer Tools Blogs site to keep you up-to-date on all new releases and include deep dive posts on a broad range of features.

Developer Tools Blogs


Visual Studio 2017 Release Notes History

Please see the Visual Studio 2017 Release Notes History page.


Top of Page