From bd2dbb2ce50ecb31ea8206ede7975041cd6d75eb Mon Sep 17 00:00:00 2001
From: Phoebe <20694052+PhoebeHui@users.noreply.github.com>
Date: Thu, 2 Jul 2020 07:58:04 +0800
Subject: [vcpkg] Update message in bootstrap.ps1 (#12145)

* [vcpkg] Update message in bootstrap.ps1

* Update docs/users/integration.md
---
 docs/users/integration.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs')

diff --git a/docs/users/integration.md b/docs/users/integration.md
index cd5f61e9d..e9a9c42cd 100644
--- a/docs/users/integration.md
+++ b/docs/users/integration.md
@@ -17,7 +17,7 @@ These link your project(s) to a specific copy of Vcpkg on your machine so any up
 ```no-highlight
 vcpkg integrate install
 ```
-This will implicitly add Include Directories, Link Directories, and Link Libraries for all packages installed with Vcpkg to all VS2015 and VS2017 MSBuild projects. We also add a post-build action for executable projects that will analyze and copy any DLLs you need to the output folder, enabling a seamless F5 experience.
+This will implicitly add Include Directories, Link Directories, and Link Libraries for all packages installed with Vcpkg to all VS2015, VS2017 and VS2019 MSBuild projects. We also add a post-build action for executable projects that will analyze and copy any DLLs you need to the output folder, enabling a seamless F5 experience.
 
 For the vast majority of libraries, this is all you need to do -- just File -> New Project and write code! However, some libraries perform conflicting behaviors such as redefining `main()`. Since you need to choose per-project which of these conflicting options you want, you will need to add those libraries to your linker inputs manually.
 
-- 
cgit v1.2.3