Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No suitable Visual Studio instances were found #22287

Closed
LedLoaf opened this issue Jan 2, 2022 · 3 comments
Closed

No suitable Visual Studio instances were found #22287

LedLoaf opened this issue Jan 2, 2022 · 3 comments
Assignees
@MonicaLiu0311
Labels
category:question This issue is a question

Comments

@LedLoaf
Copy link

LedLoaf commented Jan 2, 2022

Hello,

I recently deleted Visual Studio 2019 and installed Visual Studio 2022.

When I use vcpkg I get this error message "No suitable Visual Studio instances were found". I'm assuming it is looking for 2019, how can I redirect where it is looking? I did a quick search for similar problems and I found nothing of use.

Any help would be appreciated!
@LedLoaf
Copy link
Author

LedLoaf commented Jan 2, 2022 •
edited
Loading

Okay, it was solved by installing the MSVS v142 - VS 2019 C++ x64/x86 build tools (v14.20-16.11) So I'm assuming vcpkg hasn't updated to accept VS2022 aka MSVS v143?

@JackBoosY
Copy link
Contributor

See microsoft/vcpkg-tool#314.

@JackBoosY JackBoosY self-assigned this Jan 2, 2022
@JackBoosY JackBoosY added the category:question This issue is a question label Jan 2, 2022
@matshou matshou mentioned this issue Jan 8, 2022
Closed
@JackBoosY JackBoosY added the category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed label Jan 13, 2022
@JackBoosY JackBoosY mentioned this issue May 27, 2022
Closed
@LilyWangLL LilyWangLL assigned MonicaLiu0311 and unassigned JackBoosY Dec 6, 2022
@FrankXie05 FrankXie05 removed the category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed label Feb 14, 2023
@FrankXie05
Copy link
Contributor

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MonicaLiu0311 MonicaLiu0311

Labels
category:question This issue is a question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@LedLoaf @JackBoosY @FrankXie05 @MonicaLiu0311