-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Question about VSBuild task #4441
Comments
No special advantage. I liked the simplicity of calling a command line tool. We need to call vswhere from multiple places: agent for capability scan and 4 tasks msbuild, vsbuild, vstest, xamarinandroid. The pattern of calling a command line tool is most flexible (vstest task is written in typescript). |
As I had the same need in my code (retrieve VS path), I took a peak at your code. Using vssetup PS library turned out to be much more elegant solution in my case. Not only, it is about 5X smaller in size then vswhere thus the size of my build task is drastically smaller.
can change into:
|
In the latest version I do see that you used vswhere.exe as the VS Locator. My question is, is there a reason for that, against using using vssetup https://github.com/Microsoft/vssetup.powershell?
Thanks
The text was updated successfully, but these errors were encountered: