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

Application must be run from Visual Studio #4043

Closed
dgnuff opened this issue Dec 22, 2019 · 3 comments · Fixed by #4085
Closed

Application must be run from Visual Studio #4043

dgnuff opened this issue Dec 22, 2019 · 3 comments · Fixed by #4085
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.

Comments

@dgnuff
Copy link

dgnuff commented Dec 22, 2019

This should go in the "Building and Debugging" section of the docs. I have Terminal cloned in f:\dev\terminal, so after a debug build using PowerShell the executable is found in f:\dev\terminal\x64\Debug\WindowsTerminal.exe .

You can't directly execute this app, you have to either run it from within Visual Studio, or launch it via the Application folder found at shell:appsfolder
@dgnuff dgnuff added the Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs label Dec 22, 2019
@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 Dec 22, 2019
@mkitzan
Copy link
Contributor

mkitzan commented Dec 24, 2019

If you've deployed the solution (using VS), you should be able to run the application from outside VS. A deployed solution can be run by pressing the Windows button then typing terminal. Something like Windows Terminal (Dev Build) should appear in the search window.

terminal-dev-build

@dgnuff
Copy link
Author

dgnuff commented Dec 25, 2019

@mkitzan I know all those things. I'm talking about opening a PowerShell window in f:\dev\terminal and then typing ".\x64\Debug\WindowsTerminal.exe". For non-UWP development, this is a first time "smoke test" that is sometimes done as soon as you have a successful build. In the case of UWP apps, that smoke test is generally going to fail, it's worth noting this for the benefit of people who are looking at this as an introduction to UWP.

@zadjii-msft zadjii-msft mentioned this issue Dec 30, 2019
Merged
3 tasks
@ghost ghost added the In-PR This issue has a related PR label Dec 30, 2019
@ghost ghost added Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. and removed In-PR This issue has a related PR labels Dec 30, 2019
@Vurmiraaz
Copy link

Yes, me too. I installed Windows Terminal from Microsoft Store and found it in "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.1.2021.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe". However, an error occurred saying I can't visit this program.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add notes concerning running WT directly from VS microsoft/terminal
3 participants
@dgnuff @mkitzan @Vurmiraaz