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

Terminal does not start after building #2029

Closed
SJang1 opened this issue Jul 19, 2019 · 2 comments
Closed

Terminal does not start after building #2029

SJang1 opened this issue Jul 19, 2019 · 2 comments
Labels
Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@SJang1
Copy link

SJang1 commented Jul 19, 2019 •
edited
Loading

Environment

Windows build number: Microsoft Windows [Version 10.0.18936.1000]
Windows Terminal version (if applicable): commit ID 8ffff8e

Steps to reproduce

.\tools\razzle.cmd rel
bcz rel
Run terminal at .\src\cascadia\CascadiaPackage\bin\x64\Release\WindowsTerminal.exe

Expected behavior

Windows Terminal Starts correctly.

Actual behavior

Terminal starts, and right after start it closes (like when commandline argument is not able to open - There is no problem for profiles.json).
@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 Jul 19, 2019
@DHowett-MSFT
Copy link
Contributor

You cannot run Windows Terminal by double-clicking the EXE; please deploy and launch the appx package. Visual Studio makes this way easier. #926

@DHowett-MSFT DHowett-MSFT added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jul 19, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 19, 2019
@SJang1
Copy link
Author

SJang1 commented Jul 19, 2019

Hmmmm.... it was possible before this commit.. 🤔
Is there a way to deploy by using a command-line?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting 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
@DHowett-MSFT @SJang1