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.

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

Using vswhere.exe to locate vs? #42

Open
Akarinnnnn opened this issue Jul 1, 2020 · 6 comments
Open

Using vswhere.exe to locate vs? #42

Akarinnnnn opened this issue Jul 1, 2020 · 6 comments
Labels
enhancement Stuff related to new and shiny things question Stuff related to questions

Comments

@Akarinnnnn
Copy link

Actually, not all Visual Studio are installed in C: , , but all vswhere.exe is located in C:\Program Files(x86)\Microsoft Visual Studio\Installer\vswhere.exe .
As it's name shown, vswhere can show where the Visual Studio(s) located. Consider using it?

@Akarinnnnn
Copy link
Author

@Gramps Gramps added the question Stuff related to questions label Jul 1, 2020
@Gramps
Copy link
Collaborator

Gramps commented Jul 1, 2020

Are you asking if you should use it?

@Akarinnnnn
Copy link
Author

I meam use this in build script.

@Gramps Gramps added the enhancement Stuff related to new and shiny things label Jul 2, 2020
@Gramps
Copy link
Collaborator

Gramps commented Jul 2, 2020

Ah, OK. Use this in the build script to locate Visual Studio. Probably not a bad idea considering that installation location will not be the same for everyone. I install mine on my E: drive actually.

Do you know if vswhere.exe returns a usable string? I guess I can always read the README in their repo!

@Akarinnnnn
Copy link
Author

it returns JSON or xml. Use powershell's intregrated xml parser may better.

@Gramps
Copy link
Collaborator

Gramps commented Jul 3, 2020

I'd think parsing JSON would be easier, but I don't really parse XML very often. I'll look into when after getting the rest of it fixed up.

Personally I don't even use the batch file to compile this, I just enter it into command prompt myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Stuff related to new and shiny things question Stuff related to questions
Projects
None yet
Development

No branches or pull requests

2 participants