How Do I Build it to Begin With? #684

@AnderssonPeter commented on GitHub (May 7, 2019):

The Readme has a section for that
https://github.com/microsoft/Terminal/blob/master/README.md#building-the-code

@AnderssonPeter commented on GitHub (May 7, 2019): The Readme has a section for that https://github.com/microsoft/Terminal/blob/master/README.md#building-the-code

claunia commented

@martinmine commented on GitHub (May 7, 2019):

There are some instructions on how to get started on the repo readme file, but some prerequisites (which version of Windows, Visual Studio, what do I need enabled of SDKs and whatnot) would be nice.

@martinmine commented on GitHub (May 7, 2019): There are some instructions on how to get started on the repo readme file, but some prerequisites (which version of Windows, Visual Studio, what do I need enabled of SDKs and whatnot) would be nice.

claunia commented

@will commented on GitHub (May 7, 2019):

I'm in a somewhat similar situation. The git submodules and nuget was all fine, but I cant figure out how to build it fully correctly. I've been poking around some of the other issues and pull requests to piece together information.

I got msbuild openconsole.sln /p:Platform=x64 to successfully build, no errors and a few warnings. However the openterm tool doesn't work

λ  .\tools\openterm.cmd
Could not locate the CascadiaWin32.exe in \bin\\. Double check that it has been built and try again.

With the formatting of the path in the error message, it looks like several variables aren't set. I don’t how they're supposed to be set.

I've also tried building through visual studio and figured out how to set it as x86 there also. That one I did in release mode.

Looking at what the openterm does, it eventually runs CascadiaWin32.exe, however that doesn't appear to exist

    Directory: C:\code\Terminal\bin\x64\release


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----         5/6/2019   9:34 PM          34304 buffersize.exe
-a----         5/6/2019   9:34 PM          51200 CloseTest.exe
-a----         5/6/2019   9:34 PM          36352 ConEchoKey.exe
-a----         5/6/2019   9:36 PM          60416 ConTerm.Parser.FuzzWrapper.exe
-a----         5/6/2019   9:36 PM          32256 FontList.exe
-a----         5/6/2019   9:34 PM          10240 Nihilist.exe
-a----         5/6/2019   9:45 PM         915968 OpenConsole.exe
-a----         5/6/2019   9:36 PM          10240 Scratch.exe
-a----         8/9/2018   1:14 AM         351744 TE.exe
-a----         8/9/2018   1:14 AM          22528 TE.ProcessHost.exe
-a----         8/9/2018   1:14 AM          22528 TE.ProcessHost.UAP.exe
-a----         5/6/2019   9:34 PM           9728 VTApp.exe
-a----         5/6/2019   9:36 PM          80384 VTCommandFuzzer.exe
-a----         5/6/2019   9:34 PM          66048 VtPipeTerm.exe
-a----         5/6/2019   3:50 PM         133040 WinAppDriver.exe

(neither in the debug directory from the command line build)

Some of the other issues people say to set it as the startup package. I don’t know what that means really but I tried pressing this

but it doesn't seem to do anything.

I'm not sure where to go from here.

@will commented on GitHub (May 7, 2019): I'm in a somewhat similar situation. The git submodules and nuget was all fine, but I cant figure out how to build it fully correctly. I've been poking around some of the other issues and pull requests to piece together information. I got `msbuild openconsole.sln /p:Platform=x64` to successfully build, no errors and a few warnings. However the openterm tool doesn't work ``` λ .\tools\openterm.cmd Could not locate the CascadiaWin32.exe in \bin\\. Double check that it has been built and try again. ``` With the formatting of the path in the error message, it looks like several variables aren't set. I don’t how they're supposed to be set. I've also tried building through visual studio and figured out how to set it as x86 there also. That one I did in release mode. Looking at what the openterm does, it eventually runs CascadiaWin32.exe, however that doesn't appear to exist ``` Directory: C:\code\Terminal\bin\x64\release Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 5/6/2019 9:34 PM 34304 buffersize.exe -a---- 5/6/2019 9:34 PM 51200 CloseTest.exe -a---- 5/6/2019 9:34 PM 36352 ConEchoKey.exe -a---- 5/6/2019 9:36 PM 60416 ConTerm.Parser.FuzzWrapper.exe -a---- 5/6/2019 9:36 PM 32256 FontList.exe -a---- 5/6/2019 9:34 PM 10240 Nihilist.exe -a---- 5/6/2019 9:45 PM 915968 OpenConsole.exe -a---- 5/6/2019 9:36 PM 10240 Scratch.exe -a---- 8/9/2018 1:14 AM 351744 TE.exe -a---- 8/9/2018 1:14 AM 22528 TE.ProcessHost.exe -a---- 8/9/2018 1:14 AM 22528 TE.ProcessHost.UAP.exe -a---- 5/6/2019 9:34 PM 9728 VTApp.exe -a---- 5/6/2019 9:36 PM 80384 VTCommandFuzzer.exe -a---- 5/6/2019 9:34 PM 66048 VtPipeTerm.exe -a---- 5/6/2019 3:50 PM 133040 WinAppDriver.exe ``` (neither in the debug directory from the command line build) Some of the other issues people say to set it as the startup package. I don’t know what that means really but I tried pressing this <img width="513" alt="Screen Shot 2019-05-06 at 10 37 37 PM" src="https://user-images.githubusercontent.com/1973/57274319-c61c9500-704f-11e9-84e9-e7aa0aced700.png"> but it doesn't seem to do anything. I'm not sure where to go from here.

claunia commented

@lizy14 commented on GitHub (May 7, 2019):

Deploy CascadiaPackage then you can see it in Start.

@lizy14 commented on GitHub (May 7, 2019): Deploy `CascadiaPackage` then you can see it in Start. ![image](https://user-images.githubusercontent.com/9985286/57274837-0f5ff980-70cf-11e9-807a-16b2086d54b4.png)

claunia commented

@rw3iss commented on GitHub (May 7, 2019):

Same.
I spent the last 4 hours trying to build this on Windows 10, after downloading the 2019 MSBuild tools, realizing it wants VS2017 tools (the link to them is broken on MS site).
I installed the 2019 tools and changed the paths in razzle.bat to point to MSBuild.exe in the 2019 directory.
That runs, and the other scripts run, but building fails.
First it was telling me it wanted v141 build tools, so I installed those from the visual studio installer.
Still complains they're missing.
I then opened the project in Visual Studio, and upgraded it to 2019 (using v142 tools).
Running the command line build still fails, saying it can't find v142 tools.
If I clean and build in Visual Studio, it fails with a bunch of syntax errors.
Anyone know why the syntax errors, at least?

========== Build: 18 succeeded, 24 failed, 0 up-to-date, 0 skipped ==========

@rw3iss commented on GitHub (May 7, 2019): Same. I spent the last 4 hours trying to build this on Windows 10, after downloading the 2019 MSBuild tools, realizing it wants VS2017 tools (the link to them is broken on MS site). I installed the 2019 tools and changed the paths in razzle.bat to point to MSBuild.exe in the 2019 directory. That runs, and the other scripts run, but building fails. First it was telling me it wanted v141 build tools, so I installed those from the visual studio installer. Still complains they're missing. I then opened the project in Visual Studio, and upgraded it to 2019 (using v142 tools). Running the command line build still fails, saying it can't find v142 tools. If I clean and build in Visual Studio, it fails with a bunch of syntax errors. Anyone know why the syntax errors, at least? ========== Build: 18 succeeded, 24 failed, 0 up-to-date, 0 skipped ==========

claunia commented

@lizy14 commented on GitHub (May 7, 2019):

@rw3iss see #449

@lizy14 commented on GitHub (May 7, 2019): @rw3iss see #449

claunia commented

@will commented on GitHub (May 7, 2019):

Thanks @lizy14 . I tried that, but got this error:

DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.18362.0 or higher. You currently are running version 10.0.17763.475. Please update your OS, or change your deployment target to a device with the appropriate version. | CascadiaPackage

However windows says that I am up to date, so I don't know how to get 10.0.18362.0

@will commented on GitHub (May 7, 2019): Thanks @lizy14 . I tried that, but got this error: `DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.18362.0 or higher. You currently are running version 10.0.17763.475. Please update your OS, or change your deployment target to a device with the appropriate version. | CascadiaPackage` However windows says that I am up to date, so I don't know how to get `10.0.18362.0` ![image](https://user-images.githubusercontent.com/1973/57275252-cff3c780-7052-11e9-9013-01c66584639d.png)

claunia commented

@lizy14 commented on GitHub (May 7, 2019):

@will I'm in Windows Insider Program (Release Preview ring), so I'm on 18362.

It seems that if you want to run it you need 1903.

@lizy14 commented on GitHub (May 7, 2019): @will I'm in Windows Insider Program (Release Preview ring), so I'm on 18362. It seems that if you want to run it you need 1903.

claunia commented

@rw3iss commented on GitHub (May 7, 2019):

@rw3iss see #449

Ah thank you! Fixed those.
Only a few remaining:

3 of these:
Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Users\Ryan\Sites\Terminal\src\cascadia\WindowsTerminal\AppHost.h 7

1 of these:
Error Specified EntryPointExe 'WindowsTerminal.exe' was not found in the project outputs. CascadiaPackage C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets 413

(I think the latter because of the 3 former errors).

@rw3iss commented on GitHub (May 7, 2019): > @rw3iss see #449 Ah thank you! Fixed those. Only a few remaining: 3 of these: Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Users\Ryan\Sites\Terminal\src\cascadia\WindowsTerminal\AppHost.h 7 1 of these: Error Specified EntryPointExe 'WindowsTerminal.exe' was not found in the project outputs. CascadiaPackage C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets 413 (I think the latter because of the 3 former errors).

claunia commented

@MarcusXe commented on GitHub (May 7, 2019):

same error,bull shit

@MarcusXe commented on GitHub (May 7, 2019): same error,bull shit

claunia commented

@imfht commented on GitHub (May 7, 2019):

any built exe download?

@imfht commented on GitHub (May 7, 2019): any built exe download?

claunia commented

@rw3iss commented on GitHub (May 7, 2019):

winrt I think needs the Windows Insider 10.0.18362.* build.
It's not hard to join Windows Insider program, just sign up, then go to Windows Insider Program in Win10 Settings, set the preferences there (set mine to 'Active Development of Windows'), then go to "Windows Update" tab, and search for updates, and it will download.
I'll do some more digging into the WinRT solution and report back.

But so far, seems to almost compile by just importing the solution into Visual Studio and upgrading it to the 2019/v142 library tools (have to install the v142 tools from the Visual Studio Installer > Individual Components, but I think they're default with 2019 anyway).

Before this worked I also ran these commands in the README:
git submodule update --init --recursive
nuget restore OpenConsole.sln

I also ran tools/razzle.bat, after changing the MSBuild path their to the 2019 location of MSBuild.exe
ie:

if exist "%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\msbuild.exe" (
    set MSBUILD="%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\msbuild.exe"
    goto :FOUND_MSBUILD
)

...but not sure that's necessary if importing to VS2019 and building from there. Just listing what I did.

Then I imported the project to VS2019, make sure Configuration is set to x64, cleaned it, and built it.
Now just the above winrt/terminalApp.h error.

@rw3iss commented on GitHub (May 7, 2019): winrt I think needs the Windows Insider 10.0.18362.* build. It's not hard to join Windows Insider program, just sign up, then go to Windows Insider Program in Win10 Settings, set the preferences there (set mine to 'Active Development of Windows'), then go to "Windows Update" tab, and search for updates, and it will download. I'll do some more digging into the WinRT solution and report back. But so far, seems to almost compile by just importing the solution into Visual Studio and upgrading it to the 2019/v142 library tools (have to install the v142 tools from the Visual Studio Installer > Individual Components, but I think they're default with 2019 anyway). Before this worked I also ran these commands in the README: git submodule update --init --recursive nuget restore OpenConsole.sln I also ran tools/razzle.bat, after changing the MSBuild path their to the 2019 location of MSBuild.exe ie: ``` if exist "%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\msbuild.exe" ( set MSBUILD="%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\msbuild.exe" goto :FOUND_MSBUILD ) ``` ...but not sure that's necessary if importing to VS2019 and building from there. Just listing what I did. Then I imported the project to VS2019, make sure Configuration is set to x64, cleaned it, and built it. Now just the above winrt/terminalApp.h error.

claunia commented

@rw3iss commented on GitHub (May 7, 2019):

Guys I think that worked. I didn't need the Insider build (was not finished installing yet), but I did need to install the WinRT package:
https://marketplace.visualstudio.com/items?itemName=CppWinRTTeam.cppwinrt101804264

========== Rebuild All: 47 succeeded, 0 failed, 0 skipped ==========

However, the built x64/Debug WindowsTerminal.exe file throws an error upon trying to run it:

Humbugh.
At least building it is solved, with VS2019, I think!

@rw3iss commented on GitHub (May 7, 2019): Guys I think that worked. I didn't need the Insider build (was not finished installing yet), but I did need to install the WinRT package: https://marketplace.visualstudio.com/items?itemName=CppWinRTTeam.cppwinrt101804264 ========== Rebuild All: 47 succeeded, 0 failed, 0 skipped ========== However, the built x64/Debug WindowsTerminal.exe file throws an error upon trying to run it: ![2019-05-07 02_40_49-Window](https://user-images.githubusercontent.com/372120/57277230-b9a93400-7071-11e9-823a-325169e32f8b.png) Humbugh. At least building it is solved, with VS2019, I think!

claunia commented

@rw3iss commented on GitHub (May 7, 2019):

Running Debug on the WindowsTerminal (Windows Store 10 version) from within VS2019 throws exception here:

Exception thrown at 0x00007FFA64CE9129 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x000000A58C91F2F8. occurred

inside base.h line 4321.

So, very esoteric error there, related to WinRT, if anyone has any ideas. I am not a C++/desktop developer (web mostly).

I'm gonna finish installing Insider build (another 10 mins), restart, see what happens.

@rw3iss commented on GitHub (May 7, 2019): Running Debug on the WindowsTerminal (Windows Store 10 version) from within VS2019 throws exception here: Exception thrown at 0x00007FFA64CE9129 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x000000A58C91F2F8. occurred inside base.h line 4321. So, very esoteric error there, related to WinRT, if anyone has any ideas. I am not a C++/desktop developer (web mostly). I'm gonna finish installing Insider build (another 10 mins), restart, see what happens.

claunia commented

@astra-midnight commented on GitHub (May 7, 2019):

None of the suggestions in here have allowed me to build it. Please provide build instructions for VS2019.

Much appreciated

@astra-midnight commented on GitHub (May 7, 2019): None of the suggestions in here have allowed me to build it. Please provide build instructions for VS2019. Much appreciated

claunia commented

2026-01-30 21:59:31 +00:00

@Supernalboot commented on GitHub (May 7, 2019):

#449 should fix some issues with VS2019 not working, some other fixes are also in here

@Supernalboot commented on GitHub (May 7, 2019): #449 should fix some issues with VS2019 not working, some other fixes are also in here

claunia commented

@will commented on GitHub (May 7, 2019):

@lizy14 and @rw3iss thanks, I did the windows insider and got on 10.0.18362.30 and the Deploy menu item did put it into my start menu. Thank you.

This was all on VS2017 for that data point.

@will commented on GitHub (May 7, 2019): @lizy14 and @rw3iss thanks, I did the windows insider and got on `10.0.18362.30` and the Deploy menu item did put it into my start menu. Thank you. This was all on VS2017 for that data point.

claunia commented

2026-01-30 21:59:31 +00:00

@rw3iss commented on GitHub (May 7, 2019):

None of the suggestions in here have allowed me to build it. Please provide build instructions for VS2019.

Much appreciated

Chloe follow #449 for the first fix to remove all the syntax errors, it's easy, literally just this change:
https://github.com/microsoft/Terminal/pull/449/files

Second, open the project in VS2019, and right click solution, select Retarget solution, and change it to VS2019, x64, etc.

Try to build it and see what errors it's giving, and let us know. That helps.

If you get the winrt/TerminalApp.h errors, install the WinRT C++ library as above.

I'm able to compile on Windows 10 VS2019 without errors, but it will not run.

@rw3iss commented on GitHub (May 7, 2019): > None of the suggestions in here have allowed me to build it. Please provide build instructions for VS2019. > > Much appreciated Chloe follow #449 for the first fix to remove all the syntax errors, it's easy, literally just this change: https://github.com/microsoft/Terminal/pull/449/files Second, open the project in VS2019, and right click solution, select Retarget solution, and change it to VS2019, x64, etc. Try to build it and see what errors it's giving, and let us know. That helps. If you get the winrt/TerminalApp.h errors, install the WinRT C++ library as above. I'm able to compile on Windows 10 VS2019 without errors, but it will not run.

claunia commented

2026-01-30 21:59:31 +00:00

@rw3iss commented on GitHub (May 7, 2019):

@lizy14 and @rw3iss thanks, I did the windows insider and got on 10.0.18362.30 and the Deploy menu item did put it into my start menu. Thank you.

This was all on VS2017 for that data point.

@will Are you saying you got the WindowsTerminal app to run? Am still waiting for Insider build 18362 to finish installing.

@rw3iss commented on GitHub (May 7, 2019): > @lizy14 and @rw3iss thanks, I did the windows insider and got on `10.0.18362.30` and the Deploy menu item did put it into my start menu. Thank you. > > This was all on VS2017 for that data point. @will Are you saying you got the WindowsTerminal app to run? Am still waiting for Insider build 18362 to finish installing.

claunia commented

@will commented on GitHub (May 7, 2019):

Yes, I'm all set now

@will commented on GitHub (May 7, 2019): Yes, I'm all set now ![image](https://user-images.githubusercontent.com/1973/57280564-fc611100-705d-11e9-9980-1d92997c9fc3.png)

claunia commented

@Supernalboot commented on GitHub (May 7, 2019):

@w3iss it does seem to be a windows insider requirement just see if it will work when insider is done, I unfortunately haven't had time to test everything yet but hopefully when I do we can make a proper list of fixes.

@Supernalboot commented on GitHub (May 7, 2019): @w3iss it does seem to be a windows insider requirement just see if it will work when insider is done, I unfortunately haven't had time to test everything yet but hopefully when I do we can make a proper list of fixes.

claunia commented

@rw3iss commented on GitHub (May 7, 2019):

@will @DimitriLambrou Cool, thanks! Will give it another go here in a bit.

@rw3iss commented on GitHub (May 7, 2019): @will @DimitriLambrou Cool, thanks! Will give it another go here in a bit.

claunia commented

@rw3iss commented on GitHub (May 7, 2019):

@will @Supernalboot Got it! Debugging it doesn't work, have to actually right click the solution and Deploy, as @will implied, then it will show in start menu. Thanks. Everyone else, just follow the few steps previously mentioned above and it should work.

@rw3iss commented on GitHub (May 7, 2019): @will @Supernalboot Got it! Debugging it doesn't work, have to actually right click the solution and Deploy, as @will implied, then it will show in start menu. Thanks. Everyone else, just follow the few steps previously mentioned above and it should work.

claunia commented

@Supernalboot commented on GitHub (May 7, 2019):

Steps:

Follow #449. (https://github.com/microsoft/Terminal/pull/449/files)
If using VS2019, open the project in VS2019, and right click solution, select Retarget solution.
If you get the winrt/TerminalApp.h errors, install the WinRT C++ library.
Run in build Mode, not Debugger.

If you get an error like this
DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.18362.0 or higher.
You might need windows Insider. Still unconfirmed.

@rw3iss Nice work.

@Supernalboot commented on GitHub (May 7, 2019): Steps: - Follow #449. (https://github.com/microsoft/Terminal/pull/449/files) - If using VS2019, open the project in VS2019, and right click solution, select Retarget solution. - If you get the winrt/TerminalApp.h errors, install the WinRT C++ library. - Run in build Mode, not Debugger. If you get an error like this `DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.18362.0 or higher. ` You might need windows Insider. Still unconfirmed. @rw3iss Nice work.

claunia commented

@codeex commented on GitHub (May 7, 2019):

why nobody publish zip or exe file?

@codeex commented on GitHub (May 7, 2019): why nobody publish zip or exe file?

claunia commented

@rw3iss commented on GitHub (May 7, 2019):

why nobody publish zip or exe file?

Because you can't. Running the built .exe crashes. It only works if you choose 'Deploy Solution' in VS2019, then it automatically shows up in your start menu. I don't know why.

@rw3iss commented on GitHub (May 7, 2019): > why nobody publish zip or exe file? Because you can't. Running the built .exe crashes. It only works if you choose 'Deploy Solution' in VS2019, then it automatically shows up in your start menu. I don't know why.

claunia commented

2026-01-30 21:59:34 +00:00

@Supernalboot commented on GitHub (May 7, 2019):

@rw3iss @codeex I'm pretty sure it is like this that way people who want to add features to the terminal can do so and run their own version, for example, if you want the terminal to change colors every few seconds you can do so yourself and test it.

@Supernalboot commented on GitHub (May 7, 2019): @rw3iss @codeex I'm pretty sure it is like this that way people who want to add features to the terminal can do so and run their own version, for example, if you want the terminal to change colors every few seconds you can do so yourself and test it.

claunia commented

@phuclv90 commented on GitHub (May 7, 2019):

why nobody publish zip or exe file?

Because you can't. Running the built .exe crashes. It only works if you choose 'Deploy Solution' in VS2019, then it automatically shows up in your start menu. I don't know why.

because a UWP app can't run standalone. It's not a win32 app

@phuclv90 commented on GitHub (May 7, 2019): > > why nobody publish zip or exe file? > > Because you can't. Running the built .exe crashes. It only works if you choose 'Deploy Solution' in VS2019, then it automatically shows up in your start menu. I don't know why. because a UWP app can't run standalone. It's not a win32 app

claunia commented

2026-01-30 21:59:34 +00:00

@phuclv90 commented on GitHub (May 7, 2019):

why nobody publish zip or exe file?

Because you can't. Running the built .exe crashes. It only works if you choose 'Deploy Solution' in VS2019, then it automatically shows up in your start menu. I don't know why.

because a UWP app can't run standalone. It's not a win32 app

@phuclv90 commented on GitHub (May 7, 2019): > > why nobody publish zip or exe file? > > Because you can't. Running the built .exe crashes. It only works if you choose 'Deploy Solution' in VS2019, then it automatically shows up in your start menu. I don't know why. because a UWP app can't run standalone. It's not a win32 app

claunia commented

2026-01-30 21:59:34 +00:00

@Paul-Weisser commented on GitHub (May 7, 2019):

Steps:
* Follow #449. (https://github.com/microsoft/Terminal/pull/449/files)

* If using VS2019, open the project in VS2019, and right click solution, select Retarget solution.

* If you get the winrt/TerminalApp.h errors, install the WinRT C++ library.

* Run in build Mode, not Debugger.
If you get an error like this
DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.18362.0 or higher.
You might need windows Insider. Still unconfirmed.

@rw3iss Nice work.

installed the Microsoft.Windows.CppWinRT nuget Package via VS 2019 Community
still got
"Cannot open include file: 'winrt/Microsoft.Terminal.Settings.h': No such file or directory TerminalCore ~\Documents\Terminal\src\cascadia\TerminalCore\Terminal.cpp 13"
and
"Cannot open include file: 'winrt/Microsoft.Terminal.TerminalControl.h': No such file or directory WindowsTerminal ~\Documents\Terminal\src\cascadia\WindowsTerminal\AppHost.h 6"
Error.
(The second Error apears twice in Apphost.h and Islandwindow.h)

Any possible solutions?

@Paul-Weisser commented on GitHub (May 7, 2019): > > > Steps: > > * Follow #449. (https://github.com/microsoft/Terminal/pull/449/files) > > * If using VS2019, open the project in VS2019, and right click solution, select Retarget solution. > > * If you get the winrt/TerminalApp.h errors, install the WinRT C++ library. > > * Run in build Mode, not Debugger. > > > If you get an error like this > `DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.18362.0 or higher. ` > You might need windows Insider. Still unconfirmed. > > @rw3iss Nice work. installed the Microsoft.Windows.CppWinRT nuget Package via VS 2019 Community still got "Cannot open include file: 'winrt/Microsoft.Terminal.Settings.h': No such file or directory TerminalCore ~\Documents\Terminal\src\cascadia\TerminalCore\Terminal.cpp 13" and "Cannot open include file: 'winrt/Microsoft.Terminal.TerminalControl.h': No such file or directory WindowsTerminal ~\Documents\Terminal\src\cascadia\WindowsTerminal\AppHost.h 6" Error. (The second Error apears twice in Apphost.h and Islandwindow.h) Any possible solutions?

claunia commented

2026-01-30 21:59:35 +00:00

@rw3iss commented on GitHub (May 7, 2019):

@Paul-Weissner I installed winrt from the standalone exe linked above. Maybe try that after uninstalling from vs/nuget/windows first.

@rw3iss commented on GitHub (May 7, 2019): @Paul-Weissner I installed winrt from the standalone exe linked above. Maybe try that after uninstalling from vs/nuget/windows first.

claunia commented

2026-01-30 21:59:35 +00:00

@Cibifang commented on GitHub (May 7, 2019):

@Paul-Weissner I installed winrt from the standalone exe linked above. Maybe try that after uninstalling from vs/nuget/windows first.

Yes, I'm all set now

I build it successfully, but if I click the "Windows Terminal", it just like original cmder without tab.

Do you know why?
or maybe I should open a new issus for this?

More:
I just deploy CascadiaPackage(because it still have many new errors when deploy whole project), but I am not sure if it is relative...

@Cibifang commented on GitHub (May 7, 2019): > @Paul-Weissner I installed winrt from the standalone exe linked above. Maybe try that after uninstalling from vs/nuget/windows first. > Yes, I'm all set now > > ![image](https://user-images.githubusercontent.com/1973/57280564-fc611100-705d-11e9-9980-1d92997c9fc3.png) I build it successfully, but if I click the "Windows Terminal", it just like original cmder without tab. ![Capture](https://user-images.githubusercontent.com/9337824/57292922-c1122100-70f5-11e9-809d-331e2ae92956.PNG) Do you know why? or maybe I should open a new issus for this? More: I just deploy CascadiaPackage(because it still have many new errors when deploy whole project), but I am not sure if it is relative...

claunia commented

2026-01-30 21:59:35 +00:00

@rw3iss commented on GitHub (May 7, 2019):

Yea that's all it is, hah. Should have tab support though (ctrl+t) and also wsl and powershell baked in, and stuff.

@rw3iss commented on GitHub (May 7, 2019): Yea that's all it is, hah. Should have tab support though (ctrl+t) and also wsl and powershell baked in, and stuff.

claunia commented

2026-01-30 21:59:36 +00:00

@Cibifang commented on GitHub (May 7, 2019):

Yea that's all it is, hah. Should have tab support though (ctrl+t) and also wsl and powershell baked in, and stuff.

wow....Thank you!
Do you know how to turn to other tabs using keyboard? or any documents about it?

@Cibifang commented on GitHub (May 7, 2019): > Yea that's all it is, hah. Should have tab support though (ctrl+t) and also wsl and powershell baked in, and stuff. wow....Thank you! Do you know how to turn to other tabs using keyboard? or any documents about it?

claunia commented

2026-01-30 21:59:36 +00:00

@nikanorov commented on GitHub (May 7, 2019):

Do you know how to turn to other tabs using keyboard? or any documents about it?

Ctrl+Tab - forward, Ctrl+Shift+Tab - back.

@nikanorov commented on GitHub (May 7, 2019): > Do you know how to turn to other tabs using keyboard? or any documents about it? Ctrl+Tab - forward, Ctrl+Shift+Tab - back.

claunia commented

2026-01-30 21:59:37 +00:00

@ankitbko commented on GitHub (May 7, 2019):

I managed to build it is VS2019 without changing target to v142 and without any code change. Followed this to install WinRT and then right-clicked on solution -> install missing feature.

@ankitbko commented on GitHub (May 7, 2019): I managed to build it is VS2019 without changing target to v142 and without any code change. Followed this to install WinRT and then right-clicked on solution -> install missing feature.

claunia commented

2026-01-30 21:59:37 +00:00

@itzjustzee commented on GitHub (May 7, 2019):

Its ALIVE!!

FINALLY!!! just doing some minor personalizing now :)

@itzjustzee commented on GitHub (May 7, 2019): Its ALIVE!! ![image](https://user-images.githubusercontent.com/43456859/57313528-b3ee3580-70e7-11e9-9663-44225842a99d.png) FINALLY!!! just doing some minor personalizing now :)

claunia commented

2026-01-30 21:59:38 +00:00

@isaacrlevin commented on GitHub (May 7, 2019):

Which project do you set as startup? WindowsTerminal? If I deploy solution with VS2017, I get this when I open it up. I get no dropdown or settings. What am I doing wrong?

@isaacrlevin commented on GitHub (May 7, 2019): Which project do you set as startup? WindowsTerminal? If I deploy solution with VS2017, I get this when I open it up. I get no dropdown or settings. What am I doing wrong? ![image](https://user-images.githubusercontent.com/8878502/57314282-580fb680-70bf-11e9-896f-727fa29c22fc.png)

claunia commented

2026-01-30 21:59:38 +00:00

@zadjii-msft commented on GitHub (May 7, 2019):

@isaac2004 CascadiaPackage

@zadjii-msft commented on GitHub (May 7, 2019): @isaac2004 `CascadiaPackage`

claunia commented

2026-01-30 21:59:38 +00:00

@zadjii-msft commented on GitHub (May 7, 2019):

I'm going to close this issue, and route all discussion on the topic of getting the terminal to build to #489

@zadjii-msft commented on GitHub (May 7, 2019): I'm going to close this issue, and route all discussion on the topic of getting the terminal to build to #489

claunia commented

@isaacrlevin commented on GitHub (May 7, 2019):

@zadjii-msft look above, why am I not getting dropdown or settings?

@isaacrlevin commented on GitHub (May 7, 2019): @zadjii-msft look above, why am I not getting dropdown or settings?

claunia commented

@zadjii-msft commented on GitHub (May 7, 2019):

@isaac2004 Try pressing ctrl+t. The defaults intentionally look much like the old Console.

We're still working on the UI, so be patient :)

@zadjii-msft commented on GitHub (May 7, 2019): @isaac2004 Try pressing ctrl+t. The defaults intentionally look much like the old Console. We're still working on the UI, so be patient :)

claunia commented

@mc1brew commented on GitHub (May 8, 2019):

@isaac2004 FYI: you can change the profile.json (C:\Users{userName}\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState on my machine...) to have "alwaysShowTabs": true. This way when you open the terminal it will be clear you're working with the new windows terminal AND you'll have immediate access to the drop down.

@mc1brew commented on GitHub (May 8, 2019): @isaac2004 FYI: you can change the profile.json (C:\Users\{userName}\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState on my machine...) to have "alwaysShowTabs": true. This way when you open the terminal it will be clear you're working with the new windows terminal AND you'll have immediate access to the drop down.

claunia commented

@rw3iss commented on GitHub (May 8, 2019):

@all Fair warning: I installed Insider Build a day ago, got this all working, things were fine, nothing intense running, all the sudden the computer just gave me nonstop BSOD, and nothing worked, no system restores, couldn't boot into safemode. Only thing that worked was resetting pc and keeping files, but have to reinstall all software, grumble. Not really sure why it happened, but maybe related.

@rw3iss commented on GitHub (May 8, 2019): @all Fair warning: I installed Insider Build a day ago, got this all working, things were fine, nothing intense running, all the sudden the computer just gave me nonstop BSOD, and nothing worked, no system restores, couldn't boot into safemode. Only thing that worked was resetting pc and keeping files, but have to reinstall all software, grumble. Not really sure why it happened, but maybe related.

claunia commented

@bmmcwhirt commented on GitHub (May 8, 2019):

I installed the WinRT packaged linked above and I still get the error:

Severity Code Description Project File Line Suppression State
Error (active) E1696 cannot open source file "winrt/Microsoft.Terminal.Settings.h" TerminalCore C:\Users\bmcwhirt\Downloads\Terminal\src\cascadia\TerminalCore\Terminal.cpp 13

@bmmcwhirt commented on GitHub (May 8, 2019): I installed the WinRT packaged linked above and I still get the error: Severity Code Description Project File Line Suppression State Error (active) E1696 cannot open source file "winrt/Microsoft.Terminal.Settings.h" TerminalCore C:\Users\bmcwhirt\Downloads\Terminal\src\cascadia\TerminalCore\Terminal.cpp 13

claunia commented

@ankitbko commented on GitHub (May 8, 2019):

I installed the WinRT packaged linked above and I still get the error:

Severity Code Description Project File Line Suppression State
Error (active) E1696 cannot open source file "winrt/Microsoft.Terminal.Settings.h" TerminalCore C:\Users\bmcwhirt\Downloads\Terminal\src\cascadia\TerminalCore\Terminal.cpp 13

Right click on solution and check if there is option to "Install Missing Features". This solved the error for me.

@ankitbko commented on GitHub (May 8, 2019): > I installed the WinRT packaged linked above and I still get the error: > > Severity Code Description Project File Line Suppression State > Error (active) E1696 cannot open source file "winrt/Microsoft.Terminal.Settings.h" TerminalCore C:\Users\bmcwhirt\Downloads\Terminal\src\cascadia\TerminalCore\Terminal.cpp 13 Right click on solution and check if there is option to "Install Missing Features". This solved the error for me.

claunia commented

@baddate commented on GitHub (May 10, 2019):

Its ALIVE!!

FINALLY!!! just doing some minor personalizing now :)

what's your windows version?

@baddate commented on GitHub (May 10, 2019): > Its ALIVE!! > > ![image](https://user-images.githubusercontent.com/43456859/57313528-b3ee3580-70e7-11e9-9663-44225842a99d.png) > > FINALLY!!! just doing some minor personalizing now :) what's your windows version?

claunia commented

@3rikk commented on GitHub (May 11, 2019):

Hello!
Just built it but it just shows up with this upon opening:

I tried changing "commandline":"powershell.exe" to "commandline":C:/Windows/System32/powershell.exe" but i still get the same issue. Changing the / to \ causes this error:

Even though I have that WinRT package installed. Any ideas? (Also, making a new cmd tab opens and instantly closes one)
Thanks!

@3rikk commented on GitHub (May 11, 2019): Hello! Just built it but it just shows up with this upon opening: ![image](https://user-images.githubusercontent.com/26841663/57574095-cb545800-7432-11e9-8572-d64a03acadd1.png) I tried changing "commandline":"powershell.exe" to "commandline":C:/Windows/System32/powershell.exe" but i still get the same issue. Changing the / to \ causes this error: ![image](https://user-images.githubusercontent.com/26841663/57574111-487fcd00-7433-11e9-9e4b-3c361a0e5ab0.png) Even though I have that WinRT package installed. Any ideas? (Also, making a new cmd tab opens and instantly closes one) Thanks!

claunia commented

@phuclv90 commented on GitHub (May 13, 2019):

I tried changing "commandline":"powershell.exe" to "commandline":C:/Windows/System32/powershell.exe" but i still get the same issue. Changing the / to \ causes this error:

@MrErikDev did you escape \ with \\ in the json string?

@phuclv90 commented on GitHub (May 13, 2019): > I tried changing "commandline":"powershell.exe" to "commandline":C:/Windows/System32/powershell.exe" but i still get the same issue. Changing the / to \ causes this error: @MrErikDev did you escape `\` with `\\` in the json string?

claunia commented

@mKay00 commented on GitHub (May 13, 2019):

I tried changing "commandline":"powershell.exe" to "commandline":C:/Windows/System32/powershell.exe" but i still get the same issue. Changing the / to \ causes this error:

@MrErikDev did you escape \ with \\ in the json string?

@MrErikDev and you miss a quotation mark in your second command in front of the C:..

@mKay00 commented on GitHub (May 13, 2019): > > I tried changing "commandline":"powershell.exe" to "commandline":C:/Windows/System32/powershell.exe" but i still get the same issue. Changing the / to \ causes this error: > > @MrErikDev did you escape `\` with `\\` in the json string? @MrErikDev and you miss a quotation mark in your second command in front of the C:..

claunia commented

@Iam-AyAn18 commented on GitHub (May 19, 2019):

Hey fellas,
I am just new to git hub and how to install a repository.

Can anybody help me how to start debugging??
I have the latest version of vs code...
cheers.

@Iam-AyAn18 commented on GitHub (May 19, 2019): Hey fellas, I am just new to git hub and how to install a repository. Can anybody help me how to start debugging?? I have the latest version of vs code... cheers.

claunia commented

@bugproof commented on GitHub (Jul 19, 2019):

Ideally, releases should contain an executable to test. I hate the fact that you have to use the Windows Store to install it.

@bugproof commented on GitHub (Jul 19, 2019): Ideally, releases should contain an executable to test. I hate the fact that you have to use the Windows Store to install it.

claunia commented