diff --git a/vcpkg/about/faq.md b/vcpkg/about/faq.md index 0df47dbc..f6d3d192 100644 --- a/vcpkg/about/faq.md +++ b/vcpkg/about/faq.md @@ -209,7 +209,7 @@ We recommend building your libraries once with your preferred build configuratio ## What MSVC toolsets are supported? -We support Visual Studio 2015 Update 3 and above. +We support Visual Studio 2017 and above. ## Why does Visual Studio not use my libraries with user-wide integration enabled? diff --git a/vcpkg/commands/integrate.md b/vcpkg/commands/integrate.md index 2a6cac1f..180b9072 100644 --- a/vcpkg/commands/integrate.md +++ b/vcpkg/commands/integrate.md @@ -32,8 +32,6 @@ Integrate vcpkg with shells and buildsystems. Integrates with [Visual Studio](../users/buildsystems/msbuild-integration.md#user-wide-integration) (Windows-only), sets the user-wide vcpkg instance, and displays CMake integration help. -On Windows with Visual Studio 2015, this subcommand will add redirecting logic into the MSBuild installation which will automatically pick up each user's user-wide vcpkg instance. Visual Studio 2017 and newer have this logic in the box. - To set the user-wide vcpkg instance, vcpkg creates a few short files containing the absolute path to the vcpkg instance inside the user's user-wide configuration location: - `%LOCALAPPDATA%\vcpkg` or `%APPDATA%\Local\vcpkg` on Windows diff --git a/vcpkg/consume/classic-mode.md b/vcpkg/consume/classic-mode.md index 47e1c2f8..7bab9ed4 100644 --- a/vcpkg/consume/classic-mode.md +++ b/vcpkg/consume/classic-mode.md @@ -77,7 +77,7 @@ to remove MSBuild system-wide integration. This integration method automatically adds vcpkg-installed packages to the following project properties: `Include Directories`, `Link Directories`, and `Link Libraries`. Additionally, this creates a post-build action that ensures that any required DLLs are copied into the build output folder. This works for all solutions and -projects using Visual Studio 2015 or newer. +projects using Visual Studio 2017 or newer. ### [CMake](#tab/cmake) diff --git a/vcpkg/consume/manifest-mode.md b/vcpkg/consume/manifest-mode.md index 4af53f1c..c9594648 100644 --- a/vcpkg/consume/manifest-mode.md +++ b/vcpkg/consume/manifest-mode.md @@ -91,7 +91,7 @@ to remove MSBuild system-wide integration. This integration method automatically adds vcpkg-installed packages to the following project properties: `Include Directories`, `Link Directories`, and `Link Libraries`. Additionally, this creates a post-build action that ensures that any required DLLs are copied into the build output folder. This works for all solutions and -projects using Visual Studio 2015 or newer. +projects using Visual Studio 2017 or newer. ### [CMake](#tab/cmake) diff --git a/vcpkg/users/buildsystems/msbuild-integration.md b/vcpkg/users/buildsystems/msbuild-integration.md index 4e69ae2c..febd1d54 100644 --- a/vcpkg/users/buildsystems/msbuild-integration.md +++ b/vcpkg/users/buildsystems/msbuild-integration.md @@ -31,7 +31,7 @@ integration. This integration method automatically adds vcpkg-installed packages to the following project properties: Include Directories, Link Directories, and Link Libraries. Additionally, this creates a post-build action that ensures that any required DLLs are copied into the build output folder. This -works for all solutions and projects using Visual Studio 2015 or newer. +works for all solutions and projects using Visual Studio 2017 or newer. This is all you need to do for the vast majority of libraries. However, some libraries perform conflicting behaviors, such as redefining `main()`. Since you need to choose per-project which of diff --git a/vcpkg/users/triplets.md b/vcpkg/users/triplets.md index 3ee16f1b..03b1a0df 100644 --- a/vcpkg/users/triplets.md +++ b/vcpkg/users/triplets.md @@ -303,10 +303,10 @@ selection algorithm. Valid settings: +- The Visual Studio 2026 platform toolset is `v145`. - The Visual Studio 2022 platform toolset is `v143`. - The Visual Studio 2019 platform toolset is `v142`. - The Visual Studio 2017 platform toolset is `v141`. -- The Visual Studio 2015 platform toolset is `v140`. ### VCPKG_PLATFORM_TOOLSET_VERSION