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

Understanding wt.exe version that is being used #9606

Closed
FallenHoot opened this issue Mar 24, 2021 · 2 comments
Closed

Understanding wt.exe version that is being used #9606

FallenHoot opened this issue Mar 24, 2021 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@FallenHoot
Copy link

FallenHoot commented Mar 24, 2021 •
edited
Loading

Currently, when you look up the version within PowerShell it provides a System.Windows.MessageBox

image

Reproduce with: wt --version

I am looking for something like this:
$PSVersionTable.PSVersion
or
cmd --version

I want to verify if WT or WT Preview is installed. I also want to know what release version of WT or WT Preview is being used without the MessageBox.
@FallenHoot FallenHoot added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 24, 2021
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 24, 2021
@zadjii-msft
Copy link
Member

Yep, this is exactly by design (currently). You'll want to see #7258 for a longer discussion on the subject.

/dup #7258

@ghost
Copy link

ghost commented Mar 24, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Mar 24, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 24, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @FallenHoot