Updated a spelling mistake in user facing text.

[0xNinshu]

The spelling of lexicographically was incorrectly entered as lexigraphically. Made the minor adjustment rebuilt the project and ran the tests with no issue.

[0xNinshu]

@microsoft-github-policy-service agree

[heaths]

Thanks for the contribution!

Wow. I've been using this wrong forever, and I typically pride myself on using proper grammar even on the Internet. I learned something today!

That said, I don't know when the next release is planned. Perhaps @tydunkel can weigh in. Perhaps we can release a new version here under Releases at least.

[0xNinshu]

@heaths No problem, we are only human. :) I found the cli to be very useful all in all thanks for the hard work!
I did notice that it doesn't work with the build tools though. Maybe that is a feature? It would be nice to be able to detect installs of the stand alone build tools. If it does and I am mistaken let me know. Actually I didn't check if vswhere is shipped with the build tools.

[heaths]

I did notice that it doesn't work with the build tools though.

It does, but you have to pass -products * or reference the Build Tools ID specifically. See #8 for details why. tl;dr: originally, Build Tools contained very little support for workloads VS did, so it was not considered. Changing that now would be a breaking change because it's still a subset.

[heaths]

/azp run Microsoft.vswhere

[heaths]

@tydunkel the pipeline seems to be broken. I can't find it in Azure Pipelines where I thought it was defined. Did this get deleted late last year?

I'm tempted just to merge. This is a benign change...or at least should be. .rc file encodings can be finicky (IIRC, I think I converted this to UTF-8 a while ago at least, since it was UCS-2 previously and treated as binary by git), but I could pull and double check this locally, too.

[heaths]

Verified locally. Not sure what's up with the pipelines - we'll investigate separately - but not holding up this PR any longer.