Some culprits have been identified: vsync, low network bandwidth, Windows update, nVidia drivers and overlay, Visual Studio, Unity license auth service, memory leaks, etc We released some fixes that helped addressing partially, or entirely, the issues some of you were having.
-->
| Developer Community| System Requirements| Compatibility| Distributable Code| License Terms| Blogs| Known Issues |
Click a button to download the latest version of Visual Studio 2017. For instructions on installing and updating Visual Studio 2017, see Update Visual Studio 2017 to the most recent release. Also, see instructions on how to install offline.
Visit the visualstudio.com/downloads page to download other Visual Studio 2017 products.
What's New in 15.9Visual Studio 2017 version 15.9 Releases
Important
Visual Studio 2017 version 15.9 Security Advisory Notices
Microsoft Visual Studio For MacVisual Studio 2017 version 15.9.15
released on August 13, 2019
Issues Fixed in 15.9.15
These are the issues addressed in 15.9.15:
Security Advisory NoticesVisual Studio 2017 version 15.9.14
released on July 9, 2019
Issues Fixed in 15.9.14
These are the issues addressed in 15.9.14:
Security Advisory NoticesVisual Studio 2017 version 15.9.13
released on June 11, 2019
Issues Fixed in 15.9.13
These are the customer-reported issues addressed in 15.9.13:
Visual Studio 2017 version 15.9.12
released on May 14, 2019
Issues Fixed in 15.9.12
These are the customer-reported issues addressed in 15.9.12:
Security Advisory NoticesVisual Studio 2017 version 15.9.11
released on April 02, 2019
Issues Fixed in 15.9.11
These are the customer-reported issues addressed in 15.9.11:
Visual Studio 2017 version 15.9.10
released on March 25, 2019
Issues Fixed in 15.9.10
These are the customer-reported issues addressed in 15.9.10:
Visual Studio 2017 version 15.9.9
released on March 12, 2019
Issues Fixed in 15.9.9
These are the customer-reported issues addressed in 15.9.9:
Security Advisory Notices
Visual Studio 2017 version 15.9.8
released on March 05, 2019
Issues Fixed in 15.9.8
These are the customer-reported issues addressed in 15.9.8:
Visual Studio 2017 version 15.9.7
released on February 12, 2019
Issues Fixed in 15.9.7
These are the customer-reported issues addressed in 15.9.7:
Security Advisory Notices
Visual Studio 2017 version 15.9.6
released on January 24, 2019
Issues Fixed in 15.9.6
These are the customer-reported issues addressed in 15.9.6:
Visual Studio 2017 version 15.9.5
released on January 08, 2019
Issues Fixed in 15.9.5
These are the customer-reported issues addressed in 15.9.5:
Security Advisory Notices
Visual Studio 2017 version 15.9.4
released on December 11, 2018
Brush for mac studio fix powder. I agree with Lecatprincess, the ELF Studio Powder brush is the only brush I find that works well with specifically MAC Stuido Fix Powder. Or any flat top synthetic brush would work well. I was frustrated with the powder until I used that brush.
Issues Fixed in 15.9.4
These are the customer-reported issues addressed in 15.9.4:
Security Advisory Notices
Visual Studio 2017 version 15.9.3
released on November 28, 2018
Issues Fixed in 15.9.3
These are the customer-reported issues addressed in 15.9.3:
Visual Studio 2017 version 15.9.2
released on November 19, 2018
Issues Fixed in 15.9.2
These are the customer-reported issues addressed in 15.9.2:
Visual Studio 2017 version 15.9.1
released on November 15, 2018
Issues Fixed in 15.9.1
These are the issues addressed in 15.9.1: Dvd video soft free download.
Details of What's New in 15.9.1Universal Windows Platform Development SDK
The Windows 10 October 2018 Update SDK (build 17763) is now the default selected SDK for the Universal Windows Platform development workload.
Summary of Notable New Features in 15.9
![]() Top Issues Fixed in 15.9
See all customer-reported issues fixed in Visual Studio 2017 version 15.9.
Details of What's New in 15.9Visual Studio 2017 version 15.9.0
released on November 13, 2018
New Features in 15.9Install
We made it easier to keep your installation settings consistent across multiple installations of Visual Studio. You can now use the Visual Studio Installer to export a .vsconfig file for a given instance of Visual Studio. This file will contain information about what workloads and components you have installed. You can then import this file to add these workload and component selections to another installation of Visual Studio.
Debugging
We have added support for consuming the new portable-pdb based symbol package format (.snupkg). We have added tooling to make it easy to consume and manage these symbol packages from sources like the NuGet.org symbol server.
C++
F#F# Compiler
F# Tools
F# Open Source Repository
The VisualFSharpFull project is now set as the default startup project, eliminating the need to manually set that before debugging. Thanks, Robert Jeppesen!
JavaScript and TypeScript Language Service Support
SharePoint 2019 Support
We added new templates that allow you to create projects for SharePoint 2019. You will have the ability to migrate existing SharePoint projects from both SharePoint 2013 and SharePoint 2016 to the new project template.
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 12and our introduction to iOS 12for more details on the new features available.
Initial Xamarin.Android Build Performance Improvements
Xamarin.Android 9.1 includes initial build performance improvements. See our Xamarin.Android 15.8 vs. 15.9 build performance comparison for more details.
Tools for Universal Windows Platform Developers
NuGetNuGet Credential Provider Improvements
This release substantially improves the experience of using authenticated package feeds, especially for Mac and Linux users:
NuGet Package Manager Improvements
NuGet Security
We have introduced NuGet Client Policies which allow you to configure package security constraints. This means you can lock down environments so only trusted packages can be installed by:
.NET Core Tools for Visual Studio
Starting with this release, the .NET Core tools for Visual Studio will now default to using only the latest stable version of a .NET Core SDK that is installed on your machine for GA releases of Visual Studio. For future previews, the tools will use only preview .NET Core SDKs.
Visual Studio 2017 version 15.9 Security Advisory NoticesVisual Studio 2017 version 15.9.15 Service Release-- released on August 13, 2019CVE-2019-1211 Git for Visual Studio Elevation of Privilege Vulnerability
An elevation of privilege vulnerability exists in Git for Visual Studio when it improperly parses configuration files. An attacker who successfully exploited the vulnerability could execute code in the context of another local user. To exploit the vulnerability, an authenticated attacker would need to modify Git configuration files on a system prior to a full installation of the application. The attacker would then need to convince another user on the system to execute specific Git commands. The update addresses the issue by changing the permissions required to edit configuration files.
Visual Studio 2017 version 15.9.14 Service Release-- released on July 9, 2019CVE-2019-1075 ASP.NET Core Spoofing Vulnerability
.NET Core updates have released today and are included in this Visual Studio update. This release addresses security and other important issues. Details can be found in the .NET Core release notes.
CVE-2019-1077 Visual Studio Extension Auto Update Vulnerability
An elevation of privilege vulnerability exists when the Visual Studio Extension auto-update process 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 Visual Studio Extension auto-update performs file operations in.
CVE-2019-1113 WorkflowDesigner XOML deserialization allows code execution
A XOML file referencing certain types could cause random code to be executed when the XOML file is opened in Visual Studio.There is now a restriction on what types are allowed to be used in XOML files. If a XOML file containing one ofthe newly unauthorized types is opened, a message is displayed explaining that the type is unauthorized.
For further information, please refer to https://support.microsoft.com/en-us/help/4512190/remote-code-execution-vulnerability-if-types-are-specified-in-xoml.
Visual Studio 2017 version 15.9.12 Service Release-- released on May 14, 2019CVE-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.
Visual Studio 2017 version 15.9.9 Service Release-- released on March 12, 2019CVE-2019-0809 Visual Studio Remote Code Execution Vulnerability
A remote code execution vulnerability exists when the Visual Studio C++ Redistributable Installer improperly validates input before loading dynamic link library (DLL) files. An attacker who successfully exploited the vulnerability could execute arbitrary code in the context of the current user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. To exploit the vulnerability, an attacker must place a malicious DLL on a local system and convince a user to execute a specific executable. The security update addresses the vulnerability by correcting how the Visual Studio C++ Redistributable Installer validates input before loading DLL files.
CVE-2019-9197 Unity Editor Remote Code Execution Vulnerability
A remote code execution vulnerability exists in the Unity Editor, a 3rd party software that Visual Studio offers to install as part of the Game Development with Unity workload. If you've installed Unity from Visual Studio, please make sure to update the version of Unity you're using to a version that addresses the vulnerability as described in the CVE.The Visual Studio installer has been updated to offer to install a Unity Editor version which addresses the vulnerability.
CVE-2019-0757 .NET Core NuGet Tampering Vulnerability
A tampering vulnerability exists in NuGet software when executed in a Linux or Mac environment. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of the vulnerability requires that an attacker can login as any other user on that machine. At that point, the attacker will be able to replace or add to files that were created by a NuGet restore operation in the current users account.
.NET Core updates have released today and are included in this Visual Studio update. The security update addresses the vulnerability by correcting how NuGet restore creates file permissions for all files extracted to the client machine. Details about the packages can be found in the .NET Core release notes.
Visual Studio 2017 version 15.9.7 Service Release-- released on February 12, 2019CVE-2019-0613 WorkflowDesigner XOML deserialization allows code execution
A XOML file referencing certain types could cause random code to be executed when the XOML file is opened in Visual Studio.There is now a restriction on what types are allowed to be used in XOML files. If a XOML file containing one ofthe newly unauthorized types is opened, a message is displayed explaining that the type is unauthorized.
For further information, please refer to https://support.microsoft.com/en-us/help/4512190/remote-code-execution-vulnerability-if-types-are-specified-in-xoml.
CVE-2019-0657 .NET Framework and Visual Studio Spoofing Vulnerability
.NET Core updates have released today and are included in this Visual Studio update. This release addresses security and other important issues. Details can be found in the .NET Core release notes.
Visual Studio 2017 version 15.9.5 Service Release-- released on January 08, 2018CVE-2019-0546 Visual Studio Remote Code Execution Vulnerability
A remote code execution vulnerability exists in Visual Studio when the C++ compiler improperly handles specific combinations of C++ constructs. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. The security update addresses the vulnerability by correcting how the Visual Studio C++ compiler handles certain C++ constructs.
Visual Studio 2017 version 15.9.4 Service Release-- released on December 11, 2018CVE-2018-8599 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability
An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly handles certain file operations. An attacker who successfully exploited this vulnerability could gain elevated privileges. To exploit this vulnerability, an attacker would require unprivileged access to a vulnerable system. The security update addresses the vulnerability by ensuring the Diagnostics Hub Standard Collector Services properly impersonates file operations.
Fixed Issues
See all customer-reported issues fixed in Visual Studio 2017 version 15.9.
Known Issues
See all existing known issues and available workarounds in Visual Studio 2017 version 15.9.
Feedback
We would love to hear from you! For issues, let us know through the Report a Problem option in the upper right-handcorner of either the installer or the Visual Studio IDE itself. The icon is located in the upper right-hand corner.You can make a product suggestion or track your issues in the Visual Studio Developer Community, where you can ask questions, find answers, and propose new features.You can also 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.
Visual Studio 2017 Release Notes History
For more information relating to past versions of Visual Studio 2017, see the Visual Studio 2017 Release Notes History page.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |