Why to setup vcpkg if its included in VS 2022?

[kyxap]

Hey there,

This is confusing for person who do not have a lot of experience with cpp + vs.

Page:
https://learn.microsoft.com/en-us/vcpkg/get_started/get-started-vs?pivots=shell-cmd#1---set-up-vcpkg

It took my a while to understand that:

• There no need to pull vcpkg since now its comes with VS (yay package manager for cpp in 2023, sorta).
• And if you do you will get warnings and errors - because VS using UI config path which is not mentioned here at all and
• For some reason we trying set custom vcpkg path in CMD which will be ignored when you try to build the project from VS ui.

This need to updated to by in sync with current dev of vcpkg integration

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 94e7a328-84e7-33e6-9e9f-9bb95cbd99cb
• Version Independent ID: 94e7a328-84e7-33e6-9e9f-9bb95cbd99cb
• Content: Install and use packages with CMake in Visual Studio
• Content Source: vcpkg/get_started/get-started-vs.md
• Product: vcpkg
• GitHub Login: @JavierMatosD
• Microsoft Alias: javiermat

[vicroms]

There are some reasons to use a standalone vcpkg. For one, classic mode is not supported by the VS copy of vcpkg (since the install location must remain immutable). I'll add an explanation to existing articles to clarify.

[vicroms]

Related to #251