Visual Studio 2017 version 15.6 - Preview Release Notes


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


Download the Current Preview Release of Visual Studio 2017

Click the button to download the latest Preview version of Visual Studio 2017. For instructions, see Install Visual Studio 2017.

Note: Installation package size will vary depending on your current Visual Studio configuration.

Tip

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

Feedback

We’d love to hear from you! For issues, let us know via 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.

Tip

Need professional support right now? See available support options.

Release History

  • February 14, 2018 -- Visual Studio version 15.6 Preview 5 New Release icon
  • February 7, 2018 -- Visual Studio version 15.6 Preview 4 -- Read the Preview 4 blog post!
  • January 25, 2018 -- Visual Studio version 15.6 Preview 3
  • January 10, 2018 -- Visual Studio version 15.6 Preview 2 -- Read the Preview 2 blog post!
  • December 14, 2017 -- Visual Studio version 15.6 Preview 1.1
  • December 7, 2017 -- Visual Studio version 15.6 Preview 1 -- Read the Preview 1 blog post!

Tip

You can learn more about how we ship our releases and how to identify different versions in the Visual Studio 2017 Release Rhythm document.

Known Issues

Visual Studio 2017 Known Issues See all existing known issues and available workarounds in Visual Studio 2017 version 15.6.


Release Date: February 14, 2018 - Visual Studio 2017 version 15.6 Preview 5

Summary of Updates in this Release

Top Issues Fixed in this Release

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.6 Preview, visit the Developer Community.

What's New in this Release

Tools for Universal Windows Platform Developers

The Windows 10 Insider Preview SDK, Build 17095, can now be installed as an optional component with the Universal Windows Platform development workload.


Release Date: February 7, 2018 - Visual Studio 2017 version 15.6 Preview 4

Summary of Updates in this Release

  • We streamlined the update process so the notification takes you directly to the Installer.
  • We added a new shortcut for Edit.Duplicate in the keyboard mapping.
  • The Performance Profiler's CPU Usage Tool can display logical call stacks for asynchronous code.
  • You can now click on "Continuous Delivery" tile in Team explorer to configure automated build and deployments for your application.
  • C++ Mapfile generation overhead is reduced in full linking scenarios.
  • Additional F# tooling and compiler updates are now available, including full support for file ordering with F# and .NET Core SDK projects.

Top Issues Fixed in this Release

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.6 Preview 4, visit the Developer Community.

What's New in this Release

IDE Setup

  • We've streamlined the update process by having the update notification in Visual Studio take you directly to the installer, instead of Extensions and Updates.
  • The workloads "ASP.NET and web development" and ".NET Core cross-platform development" have been updated to include "Cloud tools for web development". This component comprises of everything needed to consume Azure Functions from within Visual Studio.

    Note

    When updating from 15.6 Preview 3 to Preview 4 or greater, the computer may restart automatically without notifying or confirming with the user.

IDE Shortcut

We added Ctrl+D as the shortcut for Edit.Duplicate in the default keyboard mapping. The previous chord (Ctrl+E, V) still works, and is available in all keyboard mapping schemes

Performance

UI Responsiveness Notifications

In order to provide more transparency around extensions' impact on performance and reliability, Visual Studio performs real-time analysis to determine whether an extension is likely to have caused unresponsiveness. If an extension is determined to have caused the hang, Visual Studio will display a notification which allows the user to disable the suspect extension or suppress future notifications for that extension (Figure 1).

UI Responsiveness notification with option to disable
(Figure 1) UI Responsiveness notification with option to disable the extension or suppress future notifications

.NET Core Solution Load

In this Preview, we focused on .NET Core and according to our lab measurements, customers can expect 20% faster solution load times on average.

Debugging and Diagnostics

CPU Usage Tool

The CPU Usage tool can display logical call stacks for asynchronous code (aka 'Async Call Stack Stitching').

  • To see logical call stacks (i.e. 'stitched call stacks'), turn on the "Stitch Async Code" setting in the Filter drop-down menu of the CPU Usage tool.
  • Asynchronous code running on behalf of a parent function or Task will appear as a child in the Call Tree and Caller/Callee views.
  • This change makes it easier to navigate asynchronous code and understand its performance characteristics.

    Note

    This feature can take a long time to produce the logical call stacks for some async code patterns. You can cancel the analysis and turn off the setting if necessary. This behavior is only available during post-mortem style profiling using the ALT-F2 Performance Profiler launch page. When the CPU Usage tool is used during debugging, it does not shows logical call stacks.

Logical Call Stack Tree with Call Stack Stitching in effect
(Figure 2) Logical Call Stack Tree with Call Stack Stitching in effect

.NET Productivity

Visual Studio Web Tools

  • Solution Explorer has a new capability for .NET Core projects called "file nesting", which allows users to control how related files appear in Solution Explorer.
  • The project publishing experience has been updated.
  • In the New Project dialog:
    • the drop-down that let's you pick a version of .NET Framework has been moved to the bottom of the dialog and no longer acts as a filter for the template.
    • for the node "Web", the sub-node "Web Site" has been renamed to "Previous Versions".
  • The debug drop-down for WebForms and MVC 5 projects:
    • now allows users to select the Snapshot Debugger for Azure App Service deployed apps.
    • has been updated to have the same browser selection gesture as ASP.NET Core projects.

Configure Continuous Delivery Tools

For solutions under source control, you can now click on the “Continuous Delivery” tile in Team Explorer to configure automated build and deployments for your application.

C++

Mapfile generation overhead is reduced in full linking scenarios. We still recommend using PDB files instead of mapfiles.

F# Compiler and Tooling Improvements

Preview 4 introduces full support for file ordering and initial support for multi-targeting with F# and .NET Core SDK projects, and also some critical fixes for the F# compiler.

Compiler and Core Library Changes

  • A regression in System.Tuple types defined in F# code no longer supporting .Item1/.Item2/etc. has been fixed. Because these tuple types are now 100% synonymous with F# tuple syntax, we introduce a warning when using these properties. See the linked pull request for more details.
  • Two regressions and another bug fix in inference order for Statically Resolved Type Parameters have been fixed by Gustavo Leon.
  • The IsSerializable property for F# types in FSharp.Core for .NET Standard has been enabled. F# types such as Option and Async are now serializable for .NET Standard and .NET Core.
  • The FSharp.Core package has been updated to version 4.3.3 and includes all changes for this release and Preview 3.

F# Tooling Improvements

  • Support for multi-targeting of F#/.NET Core SDK-based projects is now implemented.
  • File ordering for .NET Core SDK-based projects is implemented, including Add Above/Below, folder support, and the Visual Studio UI updating without needing to reload a project.
  • Bug fixes and performance improvements, by Eugene Auduchinok and Microsoft.
  • Code surrounded by #if INTERACTIVE defines now support IDE features which do not require type checking, by Eugene Auduchinok.
  • An inadvertent reversion of a fix for empty "New file" window on older F#/ASP.NET (.NET Framework) projects has been fixed by Loïc Denuzière.

F# infrastructure and OSS repo improvements

  • Satellite assemblies and FSharp.Core.resources.dll are now included in the F# compiler SDK.
  • The compiler is now prevented from rebuilding itself in the Visual F# codebase if assembly info has not changed.
  • ToString() is implemented for FSharpSymbolUse to make it easier to look at all symbol use results when debugging editor tooling, by Eugene Auduchinok.

To see the full commit changelog, see our tag.


Release Date: January 25, 2018 - Visual Studio 2017 version 15.6 Preview 3

Summary of Updates in this Release

Top Issues Fixed in this Release

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.6 Preview, visit the Developer Community.

What's New in this Release

Visual Studio Build Tools

The Visual Studio Build Tools allow you to create build servers without installing all of Visual Studio. The installer already supports C++, ASP.NET, and .NET Core for Desktop projects. In response to customer requests, we are enhancing the Visual Studio Build Tools to support additional project types. In this release we have added support for TypeScript and Node.js projects. We expect to add support for more project types in future releases. This is the download location for the Visual Studio Build Tools for this Preview release.

Visual Studio ClickOnce Tools

ClickOnce is a deployment technology that enables you to create self-updating Windows-based applications that can be installed and run with minimal user interaction. It uses certificates to verify the authenticity of the application's publisher, and to sign the application and deployment manifests to prove that the files have not been tampered with. In this release we have added support for signing the application and deployment manifests with Cryptography Next Generation (CNG) certificate.

Diagnostics and Debugging

Snapshot Debugger

If you are working on an ASP.NET application running in Azure App Service, and would like to try out Snappoints or Logpoints, you can now do so by selecting "Snapshot Debugger (Azure App Service)" in the Debug Target dropdown (Figure 1).

Start Snapshot Debugger for ASP.NET application
(Figure 1) Start Snapshot Debugger for ASP.NET application

Installation

With new installation details (Figure 2), you can see the download size, download percentage completed and the rate of the download. You can also see total number of packages being installed and how many are remaining.

  • Note: If you pause the installation and later resume, the progress applies to what’s left to be downloaded and installed, and does not start from the previous count.
Installation details
(Figure 2) Installation details

Visual C++ Improvements

  • The C++ team has made significant compile-time improvements:
    • The compiler optimizes your code to run faster through improved optimizations of pre-incremented loops and improved identification and propagation of constant global data in LTCG.
    • Compile times are shorter compared to 15.5. The compiler front-end is between 3-5% faster on most inputs. The compiler optimizer is 3% faster due to reduced overhead of core optimization algorithms. Additionally, large LTCG compilations are 10% faster due to re-architected data structures.
  • Improvements to the C++ linker:
    • Debugging large solutions with /Debug:fastlink PDBs is more robust. Changes in the PDB lead to reduced latency and a 30% reduction in heap memory consumption in the VS Debugger.
  • Profile-Guided Optimization is enabled and fully supported on ARM64.

F# Language and Tooling Improvements

A lot of improvements went into F# and its tools for this release. As always, significant contributions from the community came together here.

F# compiler and core library improvements

F# tooling improvements

  • Error reporting improvements by Vasily Kirichenko and Eugene Auduchinok.
  • Performance improvements by Vasily Kirichenko, Eugene Auduchinok, Daniel Wedelich, and Microsoft.
  • More precise autocompletion with numerous bugs fixed by Vasily Kirichenko and Microsoft.
  • Static members in unopened namespaces are available in completion by Vasily Kirichenko.
  • Namespace symbols appear in Document Highlight and Find All References by Vasily Kirichenko.
  • Structured Guidelines code has been made available for other editors (VSCode, VS for Mac, Rider) Eugene Auduchinok.
  • Better collapsing and structured guidelines for F# constructors by Eugene Auduchinok.
  • Shared files in F# and .NET Core SDK-based projects are now supported.
  • Open statements are no longer simplified in the Simplify Names analyzer by Vasily Kirichenko.
  • Display of sbyte and byte IL fields in QuickInfo is now supported by Vasily Kirichenko.
  • Unused declaration code fix is no longer triggered on uncalled F# functions or methods by Vasily Kirichenko.
  • .NET Standard projects can now be referenced by F#/.NET Framework projects.
  • Drag and Drop across folders in .NET Framework projects is now supported by Paulo Nobre.
  • Unused declarations analyzer and code fix is now able to be toggled.

F# infrastructure improvements

  • Versioning update RFC has been implemented.
  • All localization files used in the compiler and tools are now available on GitHub, and are able to accept community contributions.
  • Nightly builds can now be produced in an hour, down from 4+ hours.
  • We removed our dependency on the Widows 10 SDK for open source contributors.

To see the full log of changes from VS 15.6 Preview 3, see our tag.


Release Date: January 10, 2018 - Visual Studio 2017 version 15.6 Preview 2

Summary of Updates in this Release

Top Issues Fixed in this Release

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.6 Preview, visit the Developer Community.

What's New in this Release

Installation and Setup

  • With this release, users without administration rights will be able to create a VS layout, which will allow non-administrators to create an offline network install.
  • When you install Visual Studio for the first time or update it from the web, you will see a new, more transparent setup experience for the Visual Studio Installer. Under the hood, nothing has changed – but the new experience shows you step-by-step what's happening (Figure 3).
Improved transparency setup for Visual Studio Installer
(Figure 3) Improved transparency setup for Visual Studio Installer

Performance

In 15.6, we continued improving solution load performance, specifically for the scenario when design time build results are cached. Large C# and Visual Basic solutions will load twice as fast as before when a solution has already been opened on a machine.

Debugging and Diagnostics

CPU Usage Tool

The CPU Usage tool now displays logical call stacks for asynchronous code (aka 'Async Call Stack Stitching') (Figure 4).

  • Asynchronous code running on behalf of a parent function or Task will appear as a child in the Call Tree and Caller/Callee views.
  • This change makes it easier to navigate asynchronous code and understand its performance characteristics.
  • To see actual call stacks (without 'stitching'), turn off the "Stitch Async Code" setting in Filter drop-down menu of the CPU Usage tool.

    Note

    This behavior is only available during post-mortem style profiling using the ALT-F2 Profiler launch page. When the CPU Usage tool is used during debugging, it does not shows logical call stacks.

Example of Call Stack Stitching
(Figure 4) Example of Call Stack Stitching

.NET Productivity Features

In 15.6 Preview 2, we’ve added the ability to navigate to decompiled sources. When enabled, invoking Go To Definition or Peek Definition on any referenced type or member will show its definition with reconstructed method bodies via ILSpy decompilation. To turn on this feature, go to Tools > Options > Text Editor > C# > Advanced > Enable navigation to decompiled sources (Figure 5).

Navigate to decompiled sources
(Figure 5) Navigate to decompiled sources

We also added a couple more .NET EditorConfig options: dotnet_prefer_inferred_tuple_names and dotnet_prefer_inferred_anonymous_type_member_names. To see all .NET coding convention options, check out .NET coding convention settings for EditorConfig.

Configure Continuous Delivery Tools

  • We added support for TFVC as a source control provider: You can now configure continuous delivery for solutions under source control in a VSTS TFVC team project (Figure 6).
Configure Continuous Delivery for projects in a VSTS TFVC project
(Figure 6) Configure Continuous Delivery for projects in a VSTS TFVC project
  • We added support for Git authentication over SSH: you can now configure continuous delivery for solutions under source control in a VSTS or GitHub Git repo with SSH AUTH enabled.

  • We introduced support for containerized projects: you can now configure continuous delivery for solutions with ASP.NET Core projects and docker support targeting Azure App Service on Linux (Web App for Containers) (Figure 7). The Configure Continuous Delivery dialog will default to create a new Azure App Service on Linux (Web App for Containers), and an Azure Container Registry if one doesn’t already exist under your Azure Subscription.

Configure Continuous Delivery to Azure dialog for App Service on Linux
(Figure 7) Configure Continuous Delivery to Azure dialog for App Service on Linux

Visual C++ Improvements

  • Further progress toward implementing the C++17 Standard Library, including APIs such as stable_sort, partition, inline vector::emplace_back in parallel, and <memory_resource>, per C++17 standards.
  • Easily add Boost unit tests to your project with Boost.Test item templates. Your Boost unit tests now also use the Boost dynamic library.
  • CTest, Google Test, and Boost.Test tests in CMake projects are automatically discovered and listed in the Test Explorer.
  • Missing include files are automatically discovered for C++ Open Folder if they exist under the workspace root, even if they are not explicitly added to the include path.
  • Debug options are now available for Embedded ARM GCC support. Right click your binary, choose Debug and Launch Settings, and then select C/C++ Debug microcontroller.
  • A C++ Core Checker extension to detect use of indirections with a lifetime that is out of scope.
  • 5 new checks enforcing rules around integer overflow, and additional rules from the C++ Core Guidelines.
  • IntelliSense errors for inactive configurations will be shown as purple squiggles in the editor. The number of configurations to process is configurable in Tools > Options.
  • Support for running single file Code Analysis (or on your selection of files from the Solution Explorer); cleaned up the Build and Analyze menus. "Run Code Analysis" no longer runs code generation, which speeds up analysis runs.

C# Compiler

The C# compiler now supports:

  • Compiler server on CoreCLR, for build throughput performance
  • Strong name signing on CoreCLR (/keyfile option, all OSes)

In addition to numerous bug fixes and one breaking change (see running list of breaking changes), two minor language changes where made to the 7.2 language features:

Visual Studio Tools for Xamarin

This release includes Xamarin.iOS 11.8 and Xamarin.Android 8.2.

Live XAML Previewing with the iOS Simulator

The Xamarin Live Player enables developers to continuously deploy, test, and debug their apps using just Visual Studio and an iOS or Android device. Visual Studio 2017 version 15.5 added support to enable developers to preview real-time XAML changes directly in the Android emulator without requiring a recompile or redeploy. This release brings this functionality to the Remoted iOS Simulator for Windows.

To use this feature, select an iOS simulator from the deployment targets dropdown and “Live Run Current View” using the context menu, keyboard shortcut, or the banner at the top of each XAML file.

Test Explorer

New Hierarchy View

The Test Explorer in Visual Studio now has a hierarchy view (Figure 8) that organizes your tests by Project, Namespace, and then Class. For Visual Studio 2017 15.6 Preview 2, the hierarchy view will be behind a feature flag, but for future previews it will be on by default. With the feature flag turned on, this view can be toggled on and off using the hierarchy button located at the top of the Test Explorer window next to the Group by button.

Test Explorer Hierarchy View
(Figure 8) Test Explorer Hierarchy View

You can turn on this feature flag through the developer command prompt or install the Feature Flags extension (Figure 9).

Feature Flags extension
(Figure 9) Feature Flags extension

If you’d like to turn on the feature flag through the Visual Studio developer command prompt, run the command below after changing the path to where Visual Studio is installed:

vsregedit set “C:\Program Files (x86)\Microsoft Visual Studio\Preview\Enterprise” HKLM FeatureFlags\TestingTools\UnitTesting\HierarchyView Value dword 1

Note

You can turn off the flag with the same command by using a 0 instead of a 1 after dword.

This feature not only makes navigating your tests much easier, but also gives better feedback on tests at a glance.

  • The “parent nodes” in the hierarchy (Project, Namespace, and Class) display a failing test icon if they contain at least one failing test.
  • Parent nodes are also followed by a number summarizing how many tests the grouping contains. The duration in milliseconds shown to the right of a parent node is the total time that tests within that group took to execute.

Adding a hierarchy view to the Test Explorer has been at the top of many wish lists and we are excited to hear feedback on how it affects your workflow. One noticeable design decision in this implementation is to prevent the use of traditional groupings within the hierarchy. Tests within each class are sorted by outcome and then by name. This means that failing tests will appear at the top of each class. A more configurable hierarchy where users can choose the ordering they wish (such as Project, Class, then Duration) would be ideal. We are interested in hearing feedback on this design.

Real Time Test Discovery

Real time test discovery is a new Visual Studio feature that uses a Roslyn analyzer to discover tests and populate the test explorer in real time without requiring you to build your project. This feature was introduced in Visual Studio 2017 15.5 Preview 2 behind a feature flag and is now on by default in 15.6! This not only makes test discovery significantly faster, it also keeps the test explorer in sync with code changes such as adding or removing tests. Since real time discovery is powered by the Roslyn compiler it is only available for C# and Visual Basic projects.

Automatic macOS Provisioning

Building iOS apps with Visual Studio on Windows just got easier. This release adds a brand new feature called automatic macOS provisioning. Rather than needing to manually maintain a Mac build machine, all you need to do is connect to the Mac, and we will handle the heavy lifting of installing and configuring your build machine with the correct Xamarin.iOS and Mono bits, all from Visual Studio.

iOS WiFi Deployment

The Remoted iOS Simulator, which allows developers to test and debug iOS apps entirely in Visual Studio on Windows, is now available to all editions of Visual Studio (as of version 15.5), including the free Community Edition! The simulator supports functionality like location simulation, rotation, gestures, and even includes functionality that the iOS simulator on Mac does not, like multi-touch. This provides a great simulator experience for developers building iOS apps on Windows, but what about devices? With Visual Studio 2017 version 15.6, you can now deploy your iOS apps over the network with WiFi deployment – no cables required! After setting up a wireless device in Xcode, it shows up in Visual Studio just like a normal deploy target.


Release Date: December 14, 2017 - Visual Studio 2017 version 15.6 Preview 1.1

Top Issues Fixed in this Release

These are the customer-reported issues addressed in this release:


Release Date: December 7, 2017 - Visual Studio 2017 version 15.6 Preview 1

Summary of Updates in this Release

Top Issues Fixed in this Release

These are the customer-reported issues addressed in this release:


What's New in this Release

Visual C++ Improvements

  • Support for C++17 guaranteed copy elision.
  • Create CMake projects from the Add New Project dialog.
  • Built-in support for Android NDK r15c for Android development.

Python

For this release, we have removed the need for a completion database in order to get IntelliSense on installed packages (Figure 10). This means that instead of waiting up to four hours after installing a package, you will now get completions in just a few seconds for popular packages such as numpy and pandas.

Python completions for the pandas package
(Figure 10) Python completions for the pandas package

We have added the ability to customize the color used for doc-strings, when they are used in a class or function, and also regular expression patterns detected as part of a call into the re library (Figure 11). These may be changed under Tools, Fonts and Colors, "Python Documentation" and "Python Regular Expression".

Example of highlighted doc-string and regular expression
(Figure 11) Example of highlighted doc-string and regular expression

Finally, for Anaconda users, we are experimenting with detection and integration of conda. When enabled, your conda environments will appear within Visual Studio automatically, and we will use conda rather than pip to manage packages. See the what's new for Python in Visual Studio 15.6 blog post for more information.

Team Explorer

We have added more support for Git tags. On the Tags page, you can view all of the tags in your repo. You can create, delete, and push tags (which was one of our most requested features on UserVoice), and you can also create a new branch from a tag.

For Visual Studio Team Services users, you can now check out pull request branches. This feature makes it easier to review pull requests, test changes, and build your code.

Setup

We've added support to pause (Figure 12) your installation and resume (Figure 13) it at a later time.

Pause your installation
(Figure 12) Pause your installation
Resume your installation
(Figure 13) Resume your installation

Extensibility

File versions for a number of Visual Studio executables – devenv.exe, blend.exe, wdexpress.exe, and vsga.exe – now reflect the minor release, for example 15.6.*.

Note

This does not affect any functionalities, but external code relying on executable file version numbers may need to be updated.

Debugging and Diagnostics

CPU Usage Tool

The CPU Usage tool (available during F5 Debugging in the Diagnostic Tools window and in the ALT-F2 Performance Profiler) now displays source line highlighting based on the CPU consumption of specific lines of code (Figure 14).

  • When you view the Call Tree or Caller/Callee views of the CPU Usage tool, the source for the selected function is displayed with CPU consumption indicated on each source line of the function.
  • If CPU performance of a function is a concern, now you can determine specifically what source lines of the function are responsible for the CPU consumption when the function was executing.

    Note

    This feature requires that source information be included in the generated PDB which is controlled by the project settings. Projects for which PDBs do not have source information will be unable to display either the line attribution or the source file.

CPU Usage tool with source line highlighting
(Figure 14) CPU Usage tool with source line highlighting

Thread Name Support

Per user feedback, the debugger is now able to display thread names that are set via SetThreadDescription APIs in dump debugging. This feature requires dumps to be collected on Windows 10 Fall Creators Update or later builds.

Key Vault

We've added the Azure Services Authentication Extension in-box for 15.6 Preview 1. This will allow projects that use the Microsoft.Azure.Services.AppAuthentication library to access Azure resources such as Key Vault using their Visual Studio accounts.


Blogs

Developer Tools Blogs Take advantage of the insights and recommendations available in the Developer Tools Blogs site.

The Developer Tools Blogs keep you up-to-date on all new releases and include deep dive posts on a broad range of features. For insights into the .NET world, check out the DotNet Blog. You can find detailed expertise in each language area team blog — C#, VB, C++ and, F# — to name a few.


Visual Studio 2017 Release Notes History

Visual Studio 2017 version 15.6 Preview Release Notes


Visual Studio 2017 version 15.5 Release Notes

The Developer Community Portal See customer-reported issues fixed in Visual Studio 2017 version 15.5.

Visual Studio 2017 version 15.4 Release Notes

The Developer Community Portal See customer-reported issues fixed in Visual Studio 2017 version 15.4.

Visual Studio 2017 version 15.3 Release Notes

The Developer Community Portal See customer-reported issues fixed in Visual Studio 2017 version 15.3.

Visual Studio 2017 version 15.2 Release Notes

The Developer Community Portal See customer-reported issues fixed in Visual Studio 2017 version 15.2.

Visual Studio 2017 version 15.1 Release Notes

The Developer Community Portal See customer-reported issues fixed in Visual Studio 2017 version 15.1.

Visual Studio 2017 version 15.0 Release Notes

The Developer Community Portal See customer-reported issues fixed in Visual Studio 2017 version 15.0.


Top of Page