Guide for build and installation #726

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

This information should be included in the Building the Code section of the README file.

@ecampidoglio commented on GitHub (May 7, 2019): This information should be included in the [`Building the Code`](https://github.com/microsoft/Terminal#building-the-code) section of the README file.

claunia commented

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

Windows 1903 is required to deploy Windows Terminal
https://github.com/microsoft/Terminal/issues/437#issuecomment-489899822

@pavelovcharov commented on GitHub (May 7, 2019): Windows 1903 is required to deploy Windows Terminal https://github.com/microsoft/Terminal/issues/437#issuecomment-489899822

claunia commented

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

Can I build it with VS 2019?

@AregevDev commented on GitHub (May 7, 2019): Can I build it with VS 2019?

claunia commented

2026-01-30 22:00:51 +00:00

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

Can I build it with VS 2019?

I've been trying for a few hours with no success. I have given up and am currently installing VS 2017

@NikolausWeiss commented on GitHub (May 7, 2019): > Can I build it with VS 2019? I've been trying for a few hours with no success. I have given up and am currently installing VS 2017

claunia commented

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

Same as you

@AregevDev commented on GitHub (May 7, 2019): Same as you

claunia commented

2026-01-30 22:00:51 +00:00

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

Can I build it with VS 2019?

I'm afraid you can't, I have got 23 FAILED to build with VS2019...

@HowBoring commented on GitHub (May 7, 2019): > Can I build it with VS 2019? I'm afraid you can't, I have got 23 FAILED to build with VS2019...

claunia commented

2026-01-30 22:00:51 +00:00

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

Thanks! I am installing VS2017, can't wait to try the new Terminal out!

@AregevDev commented on GitHub (May 7, 2019): Thanks! I am installing VS2017, can't wait to try the new Terminal out!

claunia commented

2026-01-30 22:00:52 +00:00

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

hello. can I download the binary file of you build ? I don`t want to build it . no environment . 😆

@clearcodecn commented on GitHub (May 7, 2019): hello. can I download the binary file of you build ? I don`t want to build it . no environment . 😆

claunia commented

2026-01-30 22:00:52 +00:00

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

Can I build it with VS 2019?

I've been trying for a few hours with no success. I have given up and am currently installing VS 2017

Me, neither. Better try on VS2017 directly. \cry

@DarryNobi commented on GitHub (May 7, 2019): > > Can I build it with VS 2019? > > I've been trying for a few hours with no success. I have given up and am currently installing VS 2017 Me, neither. Better try on VS2017 directly. \cry

claunia commented

2026-01-30 22:00:52 +00:00

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

There is a pull request for a branch that fixes the VS 2019 errors: https://github.com/microsoft/Terminal/pull/449

@NikolausWeiss commented on GitHub (May 7, 2019): There is a pull request for a branch that fixes the VS 2019 errors: https://github.com/microsoft/Terminal/pull/449

claunia commented

2026-01-30 22:00:53 +00:00

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

Can I build it with VS 2019?

Yes, with hours of patience, and fixing many bugs.

@Berrysoft commented on GitHub (May 7, 2019): > Can I build it with VS 2019? Yes, with hours of patience, and fixing many bugs.

claunia commented

2026-01-30 22:00:53 +00:00

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

There is a pull request for a branch that fixes the VS 2019 errors: #449

That single line of code worked for me in VS2019. I'm now installing insider build to get to 1903 or above.

@noobhacker commented on GitHub (May 7, 2019): > There is a pull request for a branch that fixes the VS 2019 errors: #449 That single line of code worked for me in VS2019. I'm now installing insider build to get to 1903 or above.

claunia commented

2026-01-30 22:00:53 +00:00

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

what dos the 'solution' mean exactly in step5, i'm new here

@ob1231 commented on GitHub (May 7, 2019): what dos the 'solution' mean exactly in step5, i'm new here

claunia commented

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

So, still, you need an insider build, right?

@pulimento commented on GitHub (May 7, 2019): So, still, you need an insider build, right?

claunia commented

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

what dos the 'solution' mean exactly in step5, i'm new here

The solution (top one) in the Solution Explorer.

@Berrysoft commented on GitHub (May 7, 2019): > what dos the 'solution' mean exactly in step5, i'm new here The solution (top one) in the Solution Explorer.

claunia commented

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

what dos the 'solution' mean exactly in step5, i'm new here

@noobhacker commented on GitHub (May 7, 2019): > what dos the 'solution' mean exactly in step5, i'm new here ![image](https://user-images.githubusercontent.com/16358189/57303534-1eb36700-7110-11e9-8338-c706825583f5.png)

claunia commented

2026-01-30 22:00:55 +00:00

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

I successfully built it, but wanted to ask, are all the features shown in the video implemented? I can only see the new UWP based console

@AregevDev commented on GitHub (May 7, 2019): I successfully built it, but wanted to ask, are all the features shown in the video implemented? I can only see the new UWP based console

claunia commented

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

what dos the 'solution' mean exactly in step5, i'm new here

thanks a lot

@ob1231 commented on GitHub (May 7, 2019): > > what dos the 'solution' mean exactly in step5, i'm new here > > ![image](https://user-images.githubusercontent.com/16358189/57303534-1eb36700-7110-11e9-8338-c706825583f5.png) thanks a lot

claunia commented

2026-01-30 22:00:55 +00:00

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

To compile, you also need to install the "Universal Windows Platform Tools" (not installed by default).

For me, TerminalCore and Unittests_TerminalCode can't be loaded, I don't know why. The file common.build.pre.props can't be loaded...

@Aarklendoia commented on GitHub (May 7, 2019): To compile, you also need to install the "Universal Windows Platform Tools" (not installed by default). For me, TerminalCore and Unittests_TerminalCode can't be loaded, I don't know why. The file common.build.pre.props can't be loaded...

claunia commented

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

This should be in the readme.md-file, maybe you should open a PR for this @ZgblKylin ? :)

@martinmine commented on GitHub (May 7, 2019): This should be in the readme.md-file, maybe you should open a PR for this @ZgblKylin ? :)

claunia commented

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

========== Build: 0 succeeded, 45 failed, 2 up-to-date, 0 skipped ==========

@zhouchaoyuan commented on GitHub (May 7, 2019): ========== Build: 0 succeeded, 45 failed, 2 up-to-date, 0 skipped ==========

claunia commented

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

Is there a way to do that from command prompt? /t:Deploy doesn't do anything on the solution.

@joj commented on GitHub (May 7, 2019): Is there a way to do that from command prompt? /t:Deploy doesn't do anything on the solution.

claunia commented

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

Thanks! I am installing VS2017, can't wait to try the new Terminal out!

hope you have succeed, I am doing this now (I have spend half a day on VS2019 )

@hjc2025 commented on GitHub (May 7, 2019): > Thanks! I am installing VS2017, can't wait to try the new Terminal out! hope you have succeed, I am doing this now (I have spend half a day on VS2019 )

claunia commented

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

To peoples who really want to try out but failed to build:
https://github.com/microsoft/Terminal/issues/468#issuecomment-489967072

@noobhacker commented on GitHub (May 7, 2019): To peoples who really want to try out but failed to build: https://github.com/microsoft/Terminal/issues/468#issuecomment-489967072

claunia commented

@Mika-Lahtinen commented on GitHub (May 7, 2019):

When I used Git bash，I was told bash：nuget：command not found
How to solve it？

@Mika-Lahtinen commented on GitHub (May 7, 2019): When I used Git bash，I was told `bash：nuget：command not found` How to solve it？

claunia commented

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

Thanks! I am installing VS2017, can't wait to try the new Terminal out!

hope you have succeed, I am doing this now (I have spend half a day on VS2019 )

I used a fork that sent the fix to vs2019, built without problems

@AregevDev commented on GitHub (May 7, 2019): > > Thanks! I am installing VS2017, can't wait to try the new Terminal out! > > hope you have succeed, I am doing this now (I have spend half a day on VS2019 ) I used a fork that sent the fix to vs2019, built without problems

claunia commented

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

When I used Git bash，I was told bash：nuget：command not found
How to solve it？

use .\dep\nuget\nuget ...

@AregevDev commented on GitHub (May 7, 2019): > When I used Git bash，I was told `bash：nuget：command not found` > How to solve it？ `use .\dep\nuget\nuget ...`

claunia commented

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

Does anyone know how to solve the error about the windows version? My window's current version is 17763, but the requirement is higher.

@iBalance94 commented on GitHub (May 7, 2019): Does anyone know how to solve the error about the windows version? My window's current version is 17763, but the requirement is higher.

claunia commented

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

@hengbu the solution is to upgrade to an Insider's build of Windows, or wait until 1903 reaches general availability. We require some features that are only available in the latest version of Windows.

@zadjii-msft commented on GitHub (May 7, 2019): @hengbu the solution is to upgrade to an Insider's build of Windows, or wait until 1903 reaches general availability. We require some features that are only available in the latest version of Windows.

claunia commented

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

always getting those errors:
Severity Code Description Project File Line Suppression State
Error C1083 Cannot open include file: 'wil/Common.h': No such file or directory WindowsTerminal C:\Users\yoda\Downloads\Terminal-master\src\inc\LibraryIncludes.h 46

@y0d4a commented on GitHub (May 7, 2019): always getting those errors: Severity Code Description Project File Line Suppression State Error C1083 Cannot open include file: 'wil/Common.h': No such file or directory WindowsTerminal C:\Users\yoda\Downloads\Terminal-master\src\inc\LibraryIncludes.h 46

claunia commented

@DHowett-MSFT commented on GitHub (May 7, 2019):

@y0d4a you should do the submodules thing in the README...

@DHowett-MSFT commented on GitHub (May 7, 2019): @y0d4a you should do the submodules thing in the README...

claunia commented

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

can someone just give us the build

@Hazix00 commented on GitHub (May 7, 2019): can someone just give us the build

claunia commented

@glen-84 commented on GitHub (May 7, 2019):

@HamzaT1992 https://github.com/microsoft/Terminal/issues/468#issuecomment-490105048.

@glen-84 commented on GitHub (May 7, 2019): @HamzaT1992 https://github.com/microsoft/Terminal/issues/468#issuecomment-490105048.

claunia commented

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

This is now the megathread for all build issues.

@zadjii-msft commented on GitHub (May 7, 2019): This is now the megathread for all build issues.

claunia commented

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

This is now the megathread for all build issues.

So I think it can be pinned because a lot of people can not build it smoothly

@ghost commented on GitHub (May 7, 2019): > This is now the megathread for all build issues. So I think it can be pinned because a lot of people can not build it smoothly

claunia commented

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

Managed to run it in VS2019 without code change or retargeting to v142. I replied in issue #461 but mentioning it here as well -
Followed this to install WinRT and then right-clicked on solution -> install missing feature.

Can someone else also try and see if this works? I can share screenshot of all the packages installed in my VS.

@ankitbko commented on GitHub (May 7, 2019): Managed to run it in VS2019 **without** code change or retargeting to v142. I replied in issue #461 but mentioning it here as well - Followed [this](https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/intro-to-using-cpp-with-winrt#visual-studio-support-for-cwinrt-xaml-the-vsix-extension-and-the-nuget-package) to install WinRT and then right-clicked on solution -> install missing feature. Can someone else also try and see if this works? I can share screenshot of all the packages installed in my VS.

claunia commented

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

I am getting this error

@nbsriharsha commented on GitHub (May 7, 2019): I am getting this error ![image](https://user-images.githubusercontent.com/9265645/57313494-5a98fd00-710d-11e9-838f-a9b623fbaa11.png)

claunia commented

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

Ran through the tutorial seen here, also updated to the latest insider build of windows. Had to perform a lot of modifications to my VSCode environment and added a lot of build tools but it compiled and it running. Thanks for this!

@audac1ty commented on GitHub (May 7, 2019): Ran through the tutorial seen here, also updated to the latest insider build of windows. Had to perform a lot of modifications to my VSCode environment and added a lot of build tools but it compiled and it running. Thanks for this!

claunia commented

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

Anyone know how to solve Win 10 SDK version issue? I am using VS 2017 and manually downloaded 1903 version SDK, but still, it deploys with 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.

@Vargnatt commented on GitHub (May 7, 2019): Anyone know how to solve Win 10 SDK version issue? I am using VS 2017 and manually downloaded 1903 version SDK, but still, it deploys with 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.

claunia commented

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

I am getting this error

You must be running Windows 1903 (build >= 10.0.18362.0) or above in order to run Windows Terminal

@audac1ty commented on GitHub (May 7, 2019): > I am getting this error > > ![image](https://user-images.githubusercontent.com/9265645/57313494-5a98fd00-710d-11e9-838f-a9b623fbaa11.png) You must be running Windows 1903 (build >= 10.0.18362.0) or above in order to run Windows Terminal

claunia commented

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

Anyone know how to solve Win 10 SDK version issue? I am using VS 2017 and manually downloaded 1903 version SDK, but still, it deploys with 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.

You must be running Windows 1903 (build >= 10.0.18362.0) or above in order to run Windows Terminal

@audac1ty commented on GitHub (May 7, 2019): > Anyone know how to solve Win 10 SDK version issue? I am using VS 2017 and manually downloaded 1903 version SDK, but still, it deploys with 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. You must be running Windows 1903 (build >= 10.0.18362.0) or above in order to run Windows Terminal

claunia commented

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

@audac1ty

It shows my windows is up-to-date. I am using Windows 10 Home edition. Do we need to update it manually?

@nbsriharsha commented on GitHub (May 7, 2019): @audac1ty ![image](https://user-images.githubusercontent.com/9265645/57314346-1ad31500-710f-11e9-80a8-5b0cc581b263.png) It shows my windows is up-to-date. I am using Windows 10 Home edition. Do we need to update it manually?

claunia commented

2026-01-30 22:01:01 +00:00

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

Building doesn't work if there are spaces in the path to the project.
Error is in the CppCommon.targets files, Exec Command=", it just really doesn't like executing the full path I think.

Collapse the path to something more straightforward, and it behaves itself a bit better. Somewhere in all the tidying, there may need to be some path escaping somewhere, but workaroundable for now.

@kianryan commented on GitHub (May 7, 2019): Building doesn't work if there are spaces in the path to the project. Error is in the CppCommon.targets files, Exec Command=", it just really doesn't like executing the full path I think. Collapse the path to something more straightforward, and it behaves itself a bit better. Somewhere in all the tidying, there may need to be some path escaping somewhere, but workaroundable for now.

claunia commented

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

for all the people who cant see the Tabs/Dropdown after they have built and run, replace the standard Profiles.json text with:

{"defaultProfile":"{00d9ddc0-fab3-49ad-90ab-64ef755bef22}","initialRows":30,"initialCols":120,"alwaysShowTabs":true,"showTerminalTitleInTitlebar":true,"experimental_showTabsInTitlebar":false,"profiles":[{"guid":"{00d9ddc0-fab3-49ad-90ab-64ef755bef22}","name":"cmd","colorscheme":"Campbell","historySize":9001,"snapOnInput":true,"cursorColor":"#FFFFFF","cursorShape":"bar","commandline":"cmd.exe","fontFace":"Consolas","fontSize":12,"acrylicOpacity":0.75,"useAcrylic":true,"closeOnExit":false,"padding":"0, 0, 0, 0"},{"guid":"{3b50b48f-7c60-4f89-9469-4537029153e4}","name":"PowerShell","colorscheme":"Campbell","historySize":9001,"snapOnInput":true,"cursorColor":"#FFFFFF","cursorShape":"bar","commandline":"powershell.exe","fontFace":"Courier New","fontSize":12,"acrylicOpacity":0.75,"useAcrylic":true,"closeOnExit":false,"padding":"0, 0, 0, 0"}],"schemes":[{"name":"Campbell","foreground":"#F2F2F2","background":"#0C0C0C","colors":["#0C0C0C","#C50F1F","#13A10E","#C19C00","#0037DA","#881798","#3A96DD","#CCCCCC","#767676","#E74856","#16C60C","#F9F1A5","#3B78FF","#B4009E","#61D6D6","#F2F2F2"]},{"name":"Solarized Dark","foreground":"#FDF6E3","background":"#073642","colors":["#073642","#D30102","#859900","#B58900","#268BD2","#D33682","#2AA198","#EEE8D5","#002B36","#CB4B16","#586E75","#657B83","#839496","#6C71C4","#93A1A1","#FDF6E3"]},{"name":"Solarized Light","foreground":"#073642","background":"#FDF6E3","colors":["#073642","#D30102","#859900","#B58900","#268BD2","#D33682","#2AA198","#EEE8D5","#002B36","#CB4B16","#586E75","#657B83","#839496","#6C71C4","#93A1A1","#FDF6E3"]}]}

alternatively just find and replace ("alwaysShowTabs":false) to true

@itzjustzee commented on GitHub (May 7, 2019): for all the people who cant see the Tabs/Dropdown after they have built and run, replace the standard Profiles.json text with: {"defaultProfile":"{00d9ddc0-fab3-49ad-90ab-64ef755bef22}","initialRows":30,"initialCols":120,"alwaysShowTabs":true,"showTerminalTitleInTitlebar":true,"experimental_showTabsInTitlebar":false,"profiles":[{"guid":"{00d9ddc0-fab3-49ad-90ab-64ef755bef22}","name":"cmd","colorscheme":"Campbell","historySize":9001,"snapOnInput":true,"cursorColor":"#FFFFFF","cursorShape":"bar","commandline":"cmd.exe","fontFace":"Consolas","fontSize":12,"acrylicOpacity":0.75,"useAcrylic":true,"closeOnExit":false,"padding":"0, 0, 0, 0"},{"guid":"{3b50b48f-7c60-4f89-9469-4537029153e4}","name":"PowerShell","colorscheme":"Campbell","historySize":9001,"snapOnInput":true,"cursorColor":"#FFFFFF","cursorShape":"bar","commandline":"powershell.exe","fontFace":"Courier New","fontSize":12,"acrylicOpacity":0.75,"useAcrylic":true,"closeOnExit":false,"padding":"0, 0, 0, 0"}],"schemes":[{"name":"Campbell","foreground":"#F2F2F2","background":"#0C0C0C","colors":["#0C0C0C","#C50F1F","#13A10E","#C19C00","#0037DA","#881798","#3A96DD","#CCCCCC","#767676","#E74856","#16C60C","#F9F1A5","#3B78FF","#B4009E","#61D6D6","#F2F2F2"]},{"name":"Solarized Dark","foreground":"#FDF6E3","background":"#073642","colors":["#073642","#D30102","#859900","#B58900","#268BD2","#D33682","#2AA198","#EEE8D5","#002B36","#CB4B16","#586E75","#657B83","#839496","#6C71C4","#93A1A1","#FDF6E3"]},{"name":"Solarized Light","foreground":"#073642","background":"#FDF6E3","colors":["#073642","#D30102","#859900","#B58900","#268BD2","#D33682","#2AA198","#EEE8D5","#002B36","#CB4B16","#586E75","#657B83","#839496","#6C71C4","#93A1A1","#FDF6E3"]}]} alternatively just find and replace ("alwaysShowTabs":false) to true

claunia commented

2026-01-30 22:01:01 +00:00

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

严重性代码说明项目文件行禁止显示状态
错误 MSB8020 无法找到 v142 的生成工具(平台工具集 =“v142”)。若要使用 v142 生成工具进行生成，请安装 v142 生成工具。或者，可以升级到当前 Visual Studio 工具，方式是通过选择“项目”菜单或右键单击该解决方案，然后选择“重定解决方案目标”。 PropertiesLibrary D:\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Platform.targets 67
could someone help me? I am new here

@AndrewGong2016 commented on GitHub (May 7, 2019): 严重性代码说明项目文件行禁止显示状态错误 MSB8020 无法找到 v142 的生成工具(平台工具集 =“v142”)。若要使用 v142 生成工具进行生成，请安装 v142 生成工具。或者，可以升级到当前 Visual Studio 工具，方式是通过选择“项目”菜单或右键单击该解决方案，然后选择“重定解决方案目标”。 PropertiesLibrary D:\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Platform.targets 67 could someone help me? I am new here

claunia commented

2026-01-30 22:01:01 +00:00

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

@audac1ty

It shows my windows is up-to-date. I am using Windows 10 Home edition. Do we need to update it manually?

Have you upgraded to the latest windows insider build? It should be 10.0.18362

@audac1ty commented on GitHub (May 7, 2019): > @audac1ty > ![image](https://user-images.githubusercontent.com/9265645/57314346-1ad31500-710f-11e9-80a8-5b0cc581b263.png) > It shows my windows is up-to-date. I am using Windows 10 Home edition. Do we need to update it manually? Have you upgraded to the latest windows insider build? It should be 10.0.18362

claunia commented

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

Can someone host a binary for Win10 64 bit? I wonder why they haven't made a release yet?

@perryizgr8 commented on GitHub (May 7, 2019): Can someone host a binary for Win10 64 bit? I wonder why they haven't made a release yet?

claunia commented

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

@audac1ty

It shows my windows is up-to-date. I am using Windows 10 Home edition. Do we need to update it manually?

Have you upgraded to the latest windows insider build? It should be 10.0.18362

How do we do it ? I am completely new to it.

@nbsriharsha commented on GitHub (May 7, 2019): > > @audac1ty > > ![image](https://user-images.githubusercontent.com/9265645/57314346-1ad31500-710f-11e9-80a8-5b0cc581b263.png) > > It shows my windows is up-to-date. I am using Windows 10 Home edition. Do we need to update it manually? > > Have you upgraded to the latest windows insider build? It should be 10.0.18362 How do we do it ? I am completely new to it.

claunia commented

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

严重性代码说明项目文件行禁止显示状态
错误 MSB8020 无法找到 v142 的生成工具(平台工具集 =“v142”)。若要使用 v142 生成工具进行生成，请安装 v142 生成工具。或者，可以升级到当前 Visual Studio 工具，方式是通过选择“项目”菜单或右键单击该解决方案，然后选择“重定解决方案目标”。 PropertiesLibrary D:\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Platform.targets 67
could someone help me? I am new here

https://github.com/microsoft/Terminal/issues/461 check this

@Vargnatt commented on GitHub (May 7, 2019): > 严重性代码说明项目文件行禁止显示状态 > 错误 MSB8020 无法找到 v142 的生成工具(平台工具集 =“v142”)。若要使用 v142 生成工具进行生成，请安装 v142 生成工具。或者，可以升级到当前 Visual Studio 工具，方式是通过选择“项目”菜单或右键单击该解决方案，然后选择“重定解决方案目标”。 PropertiesLibrary D:\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Platform.targets 67 > could someone help me? I am new here https://github.com/microsoft/Terminal/issues/461 check this

claunia commented

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

@y0d4a you should do the submodules thing in the README...

i do that... and always got that error. But that folder exist inside dep folder... somewhere in code is wrong path or mine environment is not ok... :s ?

@y0d4a commented on GitHub (May 7, 2019): > > > @y0d4a you should do the submodules thing in the README... i do that... and always got that error. But that folder exist inside dep folder... somewhere in code is wrong path or mine environment is not ok... :s ?

claunia commented

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

y0d

damn, it mine fault, i don`t have 1903... still on 1809... that can be cause..

@y0d4a commented on GitHub (May 7, 2019): > y0d damn, it mine fault, i don`t have 1903... still on 1809... that can be cause..

claunia commented

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

Open Developer Command Prompt for VS 2019:

git clone https://github.com/microsoft/Terminal.git
cd Terminal
git submodule init
git submodule update
nuget restore OpenConsole.sln
msbuild /p:Configuration=Release /p:Platform=x64 /p:PlatformToolset=v142 /p:TargetPlatformVersion=10.0.18362.0 /p:PreferredToolArchitecture=x64 OpenConsole.sln

@fcharlie commented on GitHub (May 7, 2019): Open `Developer Command Prompt for VS 2019`: ```bat git clone https://github.com/microsoft/Terminal.git cd Terminal git submodule init git submodule update nuget restore OpenConsole.sln msbuild /p:Configuration=Release /p:Platform=x64 /p:PlatformToolset=v142 /p:TargetPlatformVersion=10.0.18362.0 /p:PreferredToolArchitecture=x64 OpenConsole.sln ```

claunia commented

https://www.windowscentral.com/how-join-windows-insider-program

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

@audac1ty

It shows my windows is up-to-date. I am using Windows 10 Home edition. Do we need to update it manually?

Have you upgraded to the latest windows insider build? It should be 10.0.18362

How do we do it ? I am completely new to it.

This should help you update to the latest build :)

@audac1ty commented on GitHub (May 7, 2019): > > > @audac1ty > > > ![image](https://user-images.githubusercontent.com/9265645/57314346-1ad31500-710f-11e9-80a8-5b0cc581b263.png) > > > It shows my windows is up-to-date. I am using Windows 10 Home edition. Do we need to update it manually? > > > > > > Have you upgraded to the latest windows insider build? It should be 10.0.18362 > > How do we do it ? I am completely new to it. https://www.windowscentral.com/how-join-windows-insider-program This should help you update to the latest build :)

claunia commented

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

Can someone host a binary for Win10 64 bit? I wonder why they haven't made a release yet?

It cannot be a binary. It is UWP app so needs to be deployed (packaged and installed through store or sideloded).

I am not an expert in UWP so don't know the correct procedure to publish it but will give it a try. Unzip the file and run Add-AppDevPackage.ps1 using Admin ps.
[link scrubbed]

Before installing this, you must enable developer mode by following Step 4 in the first post of this thread.

If you get some random and weird certificate error you need to install the certificate present in the folder under Trusted Root Certification Authorities under Local Machine by following following steps present here

Note: High change this may not work as I am on windows insider and don't know how to publish UWP applications for different platforms.

@ankitbko commented on GitHub (May 7, 2019): > Can someone host a binary for Win10 64 bit? I wonder why they haven't made a release yet? It cannot be a binary. It is UWP app so needs to be deployed (packaged and installed through store or sideloded). I am not an expert in UWP so don't know the correct procedure to publish it but will give it a try. Unzip the file and run `Add-AppDevPackage.ps1` using **Admin** ps. [link scrubbed] Before installing this, you must enable developer mode by following _Step 4_ in the first post of this thread. If you get some random and weird certificate error you need to install the certificate present in the folder under **Trusted Root Certification Authorities** under **Local Machine** by following following steps present [here](https://docs.microsoft.com/en-us/windows/application-management/sideload-apps-in-windows-10#how-do-i-sideload-an-app-on-desktop) Note: High change this may not work as I am on windows insider and don't know how to publish UWP applications for different platforms.

claunia commented

@DHowett-MSFT commented on GitHub (May 7, 2019):

Hey @ankitbko,
Thanks for being excited about this. Please don't use this issue tracker to share binaries -- it's not ready to be used by the general public, and that's why we haven't published a version of it to the store or the selfhost rings.

Giving out a binary leaves people under the impression that it's Microsoft-supported, and we just can't do that yet.

@DHowett-MSFT commented on GitHub (May 7, 2019): Hey @ankitbko, Thanks for being excited about this. Please don't use this issue tracker to share binaries -- it's not ready to be used by the general public, and that's why we haven't published a version of it to the store or the selfhost rings. Giving out a binary leaves people under the impression that it's Microsoft-supported, and we just can't do that yet.

claunia commented

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

Ah got it.. thanks @DHowett-MSFT.

Sorry @perryizgr8 I can't share it here as it gives wrong impression as I am also part of Microsoft. Thanks for understanding.

@ankitbko commented on GitHub (May 7, 2019): Ah got it.. thanks @DHowett-MSFT. Sorry @perryizgr8 I can't share it here as it gives wrong impression as I am also part of Microsoft. Thanks for understanding.

claunia commented

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

@ankitbko Thanks for trying!

@perryizgr8 commented on GitHub (May 7, 2019): @ankitbko Thanks for trying!

claunia commented

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

can't see deploy after building. anyway we can run in cmd?

@xdagee commented on GitHub (May 7, 2019): can't see deploy after building. anyway we can run in cmd?

claunia commented

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

can't see deploy after building. anyway we can run in cmd?

If its successfully deployed, you will see it in start menu.

@ankitbko commented on GitHub (May 7, 2019): > can't see deploy after building. anyway we can run in cmd? If its successfully deployed, you will see it in start menu.

claunia commented

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

can't see deploy after building. anyway we can run in cmd?

Do you see the Solution Explorer side menu?
If not, then press Ctrl+Alt+L or go to View -> Solution Explorer.
At the top of the Solution Explorer, the top most item is: Solution 'OpenConsole' (47 projects).
Right click it and choose Deploy Solution from the context menu.

@nizos commented on GitHub (May 7, 2019): > > > can't see deploy after building. anyway we can run in cmd? Do you see the Solution Explorer side menu? If not, then press Ctrl+Alt+L or go to View -> Solution Explorer. At the top of the Solution Explorer, the top most item is: Solution 'OpenConsole' (47 projects). Right click it and choose Deploy Solution from the context menu. ![image](https://user-images.githubusercontent.com/16970186/57322619-3c7acf00-7104-11e9-815e-4d7427fab4bf.png)

claunia commented

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

It absolutely needs to be put into the Readme that you can NOT use Visual Studio 2019, especially since Microsoft is known for making legacy software harder to access (including Visual Studio 2017, which after uninstalling it I still don't know how to re-download).

Using VS2019's update tool doesn't work either.

@jlandrum commented on GitHub (May 7, 2019): It absolutely needs to be put into the Readme that you can NOT use Visual Studio 2019, especially since Microsoft is known for making legacy software harder to access (including Visual Studio 2017, which after uninstalling it I still don't know how to re-download). Using VS2019's update tool doesn't work either.

claunia commented

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

@jlandrum It works for me using VS 2019. What is the error that you are seeing?

@ankitbko commented on GitHub (May 7, 2019): @jlandrum It works for me using VS 2019. What is the error that you are seeing?

claunia commented

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

Followed the tutorial on 1904, build on x64 release without any errors and I get this:

If I open Windows Terminal (Preview), I get:

@Drakota commented on GitHub (May 7, 2019): Followed the tutorial on 1904, build on x64 release without any errors and I get this: ![image](https://user-images.githubusercontent.com/22665836/57326939-a16dff00-70db-11e9-9023-2852aa5634fe.png) If I open Windows Terminal (Preview), I get: ![image](https://user-images.githubusercontent.com/22665836/57326983-b9458300-70db-11e9-819c-6d588701ec87.png)

claunia commented

https://github.com/microsoft/Terminal#i-built-and-ran-the-new-terminal-but-it-looks-just-like-the-old-console-what-gives

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

@zadjii-msft commented on GitHub (May 7, 2019): https://github.com/microsoft/Terminal#i-built-and-ran-the-new-terminal-but-it-looks-just-like-the-old-console-what-gives

claunia commented

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

@zadjii-msft

https://github.com/microsoft/Terminal#i-built-and-ran-the-new-terminal-but-it-looks-just-like-the-old-console-what-gives

Thanks that worked.

Is the acrylic effect supposed to work right now?

@Drakota commented on GitHub (May 7, 2019): @zadjii-msft > https://github.com/microsoft/Terminal#i-built-and-ran-the-new-terminal-but-it-looks-just-like-the-old-console-what-gives Thanks that worked. ![image](https://user-images.githubusercontent.com/22665836/57327746-a8960c80-70dd-11e9-92de-0b6b8d813738.png) Is the acrylic effect supposed to work right now?

claunia commented

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

@drakota yes it's supposed to work, but it will only work when the app is focused. This is something that we can't control unfortunately, that's just how acrylic works. There are other magic things that control acrylic - it won't work over remote desktop connections, and supposedly it doesn't work on battery-saver.

Ctrl+Shift+mouse wheel should adjust the transparency of an acrylic tab, so you could try that to make sure it works.

@zadjii-msft commented on GitHub (May 7, 2019): @drakota yes it's supposed to work, but it will only work when the app is focused. This is something that we can't control unfortunately, that's just how acrylic works. There are other magic things that control acrylic - it won't work over remote desktop connections, and supposedly it doesn't work on battery-saver. Ctrl+Shift+mouse wheel should adjust the transparency of an acrylic tab, so you could try that to make sure it works.

claunia commented

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

Now I successfully build the whole project (2 warnings) in Visual Studio 2019 + v142 + SDK 18362. Any tricks/commands to build only OpenConsole.exe without building others?

@Biswa96 commented on GitHub (May 7, 2019): Now I successfully build the whole project (2 warnings) in Visual Studio 2019 + v142 + SDK 18362. Any tricks/commands to build only OpenConsole.exe without building others?

claunia commented

@DHowett-MSFT commented on GitHub (May 7, 2019):

Yeah, right-click “host.EXE” in the conhost section and choose Build. That’s pretty basic VS usage. You can also set it as a startup project so when you F5 it launches OpenConsole.

@DHowett-MSFT commented on GitHub (May 7, 2019): Yeah, right-click “host.EXE” in the conhost section and choose Build. That’s pretty basic VS usage. You can also set it as a startup project so when you F5 it launches OpenConsole.

claunia commented

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

can't see deploy after building. anyway we can run in cmd?

This happened to me and the problem was that I had some projects that were not loaded properly.

I opened this solution VS 2017 before I installed the needed Visual studio components. This resulted in some of the projects not loaded properly. I had to right click on the individual folders and click "Reload projects from the Solution folder".

Make sure that the successful build is more than just 2-3 projects.

@skasturi commented on GitHub (May 7, 2019): > can't see deploy after building. anyway we can run in cmd? This happened to me and the problem was that I had some projects that were not loaded properly. I opened this solution VS 2017 before I installed the needed Visual studio components. This resulted in some of the projects not loaded properly. I had to right click on the individual folders and click "Reload projects from the Solution folder". Make sure that the successful build is more than just 2-3 projects.

claunia commented

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

First, we thank you for this, it will make the lives of devs worldwide easier.
Two, how much time does it take for you to compile using vs2019?
Three, how much memory do you need to compile (aproximately)?

@taosx commented on GitHub (May 7, 2019): First, we thank you for this, it will make the lives of devs worldwide easier. Two, how much time does it take for you to compile using vs2019? Three, how much memory do you need to compile (aproximately)?

claunia commented

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

Thanks for the guide! I just built on Windows 1903 (non-Insider), using v142. It wasn't nearly as painful as I thought it would be.

@GabrielSieben commented on GitHub (May 7, 2019): Thanks for the guide! I just built on Windows 1903 (non-Insider), using v142. It wasn't nearly as painful as I thought it would be.

claunia commented

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

Please can someone tell me what I am doing wrong as I have tried to download the zip, clone the git and tried to compile from commandline, VS 2019 and VS 2017 after installing the dependancies and each time it results in something like

========== Build: 5 succeeded, 42 failed, 0 up-to-date, 0 skipped ==========

Mostly the error is:

fatal error C1083: Cannot open include file: 'wil/Common.h': No such file or directory

If I try to open the file from solution explorer, sure enough VS tells me it can't open it.

I use VS all the time and don't have issues building my own projects, granted they are not nearly as complex!

Thanks

@robinwilson16 commented on GitHub (May 7, 2019): Please can someone tell me what I am doing wrong as I have tried to download the zip, clone the git and tried to compile from commandline, VS 2019 and VS 2017 after installing the dependancies and each time it results in something like ``` ========== Build: 5 succeeded, 42 failed, 0 up-to-date, 0 skipped ========== ``` Mostly the error is: ``` fatal error C1083: Cannot open include file: 'wil/Common.h': No such file or directory ``` If I try to open the file from solution explorer, sure enough VS tells me it can't open it. I use VS all the time and don't have issues building my own projects, granted they are not nearly as complex! Thanks

claunia commented

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

@robinwilson16 : you're missing the git submodule update --init --recursive step, it will download wil

@kbalint commented on GitHub (May 7, 2019): @robinwilson16 : you're missing the` git submodule update --init --recursive` step, it will download wil

claunia commented

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

Hi all,

Lots of discovery overnight so this may not be required anymore but I was successful in building this using just the VS2109 Build Tools (i.e. no Visual Studio installed). If anyone requires a writeup on this please let me know.

Cheers
Rich Young.

@handyjellyfish commented on GitHub (May 7, 2019): Hi all, Lots of discovery overnight so this may not be required anymore but I was successful in building this using just the VS2109 Build Tools (i.e. no Visual Studio installed). If anyone requires a writeup on this please let me know. Cheers Rich Young.

claunia commented

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

git submodule update --init --recursive

Thanks @kbalint I had run it but had run it in the folder above where I ran git clone and I had not cd'd into the Terminal sub-directory. That error is now resolved and trying to build again.
Thanks for the help!
Robin

@robinwilson16 commented on GitHub (May 7, 2019): > git submodule update --init --recursive Thanks @kbalint I had run it but had run it in the folder above where I ran git clone and I had not cd'd into the Terminal sub-directory. That error is now resolved and trying to build again. Thanks for the help! Robin

claunia commented

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

git submodule update --init --recursive

Thanks @kbalint I had run it but had run it in the folder above where I ran git clone and I had not cd'd into the Terminal sub-directory. That error is now resolved and trying to build again.
Thanks for the help!
Robin

Now I am getting this error and now only 7 fail to build so it is progress:

error C3859: Failed to create virtual memory for PCH

Does anyone know how to fix this one?

@robinwilson16 commented on GitHub (May 8, 2019): > > git submodule update --init --recursive > > Thanks @kbalint I had run it but had run it in the folder above where I ran git clone and I had not cd'd into the Terminal sub-directory. That error is now resolved and trying to build again. > Thanks for the help! > Robin Now I am getting this error and now only 7 fail to build so it is progress: ``` error C3859: Failed to create virtual memory for PCH ``` Does anyone know how to fix this one?

claunia commented

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

Here is a guide for building from cmd although the last step fails which may be due to me having multiple versions of VS installed (from searching online) but not sure yet how to fix. This may work for others with only one VS

mkdir C:\Terminal
cd C:\Terminal
git init
git clone https://github.com/microsoft/Terminal.git
cd Terminal
git submodule update --init --recursive
"C:\Terminal\Terminal\dep\nuget\nuget.exe" restore OpenConsole.sln
"C:\Windows\Microsoft.NET\Framework64\v4.0.30319\msbuild.exe" OpenConsole.sln

The error I keep getting is (variations on path but same error):

c:\Terminal\Terminal\src\common.build.pre.props(3,3): error MSB4019: The imported project "c:\Microsoft.Cpp.Default.pro
ps" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. [c:\
Terminal\Terminal\src\buffer\out\lib\bufferout.vcxproj]

So far I have had zero success building this from VS 2017, VS 2019 or CMD
What is the secret to getting it to build?

@robinwilson16 commented on GitHub (May 8, 2019): Here is a guide for building from cmd although the last step fails which may be due to me having multiple versions of VS installed (from searching online) but not sure yet how to fix. This may work for others with only one VS ``` mkdir C:\Terminal cd C:\Terminal git init git clone https://github.com/microsoft/Terminal.git cd Terminal git submodule update --init --recursive "C:\Terminal\Terminal\dep\nuget\nuget.exe" restore OpenConsole.sln "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\msbuild.exe" OpenConsole.sln ``` The error I keep getting is (variations on path but same error): ``` c:\Terminal\Terminal\src\common.build.pre.props(3,3): error MSB4019: The imported project "c:\Microsoft.Cpp.Default.pro ps" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. [c:\ Terminal\Terminal\src\buffer\out\lib\bufferout.vcxproj] ``` So far I have had zero success building this from VS 2017, VS 2019 or CMD What is the secret to getting it to build?

claunia commented

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

@handyjellyfish I would really appreciate a writeup as I have tried everything and it just isn't working for me :(

@robinwilson16 commented on GitHub (May 8, 2019): @handyjellyfish I would really appreciate a writeup as I have tried everything and it just isn't working for me :(

claunia commented

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

@robinwilson16 use those issues as the guide source: #508 (translate it via google), the part from @SwimmingTiger; #449; #461.
It will lead you to the state when build is ok, but no way to deploy on 17763 or working application on insider build.

P.S. I found use-full OpenTerminal.exe on 17763 as it able to follow windows color theme, so i have backed up original conhost and replaced it with new one :)

@hapylestat commented on GitHub (May 8, 2019): @robinwilson16 use those issues as the guide source: #508 (translate it via google), the part from @SwimmingTiger; #449; #461. It will lead you to the state when build is ok, but no way to deploy on 17763 or working application on insider build. P.S. I found use-full OpenTerminal.exe on 17763 as it able to follow windows color theme, so i have backed up original conhost and replaced it with new one :) ![image](https://user-images.githubusercontent.com/3234762/57339323-c7c28780-7139-11e9-8b51-8e0b4788b060.png)

claunia commented

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

@handyjellyfish I would really appreciate a writeup as I have tried everything and it just isn't working for me :(

Hey @robinwilson16 that error that you are getting looks very much like you don't have the CPP libraries installed properly. Possibly because you are using the wrong msbuild. What I would try first is run razzle.cmd from the tools directory then run your commands again (but just running msbuild.exe OpenConsole.sln /p:Configuration=Release /p:Platform=x64) if you have 2017 installed properly it should be all that you require.

@handyjellyfish commented on GitHub (May 8, 2019): > @handyjellyfish I would really appreciate a writeup as I have tried everything and it just isn't working for me :( Hey @robinwilson16 that error that you are getting looks very much like you don't have the CPP libraries installed properly. Possibly because you are using the wrong msbuild. What I would try first is run razzle.cmd from the tools directory then run your commands again (but just running msbuild.exe OpenConsole.sln /p:Configuration=Release /p:Platform=x64) if you have 2017 installed properly it should be all that you require.

claunia commented

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

I have followed the following steps:

I upgraded to insider build 1903.
Installed VS2019 Community
Installed Visual Studio Build Tools 2017 and 2019
Added:

    1. C++ (v142 & v141) Universal Windows Platform tools
    2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0)
    3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools
    4. C++ ATL for v141 & v142 build tools (x86 & x64)
    5. C++/WinRT

Installed WinRT package
Run:

    1. git clone https://github.com/microsoft/Terminal.git
    2. git submodule update --init --recursive
    3. nuget restore OpenConsole.sln

Opened Project/Solution from VSCode
Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded)
Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance

And after all this:

Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808.

Edit: I think the team had a reason there's not a binary, it's not ready yet.
I think I'll wait till mid June. Have some good sprints!

@Berrysoft still not working, got some errors this time (unfortunately I deleted all repos and tools related with Terminal (40+ gb together with the components installed)

@taosx commented on GitHub (May 8, 2019): I have followed the following steps: - I upgraded to insider build 1903. - Installed VS2019 Community - Installed Visual Studio Build Tools 2017 and 2019 - Added: ``` 1. C++ (v142 & v141) Universal Windows Platform tools 2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0) 3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools 4. C++ ATL for v141 & v142 build tools (x86 & x64) 5. C++/WinRT ``` - Installed WinRT package - Run: ``` 1. git clone https://github.com/microsoft/Terminal.git 2. git submodule update --init --recursive 3. nuget restore OpenConsole.sln ``` - Opened Project/Solution from VSCode - Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded) - Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance And after all this: ![exception_base h](https://user-images.githubusercontent.com/5703052/57343880-cbf8a000-714d-11e9-8bce-0d6ab2140d82.png) > Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808. Edit: I think the team had a reason there's not a binary, it's not ready yet. I think I'll wait till mid June. Have some good sprints! @Berrysoft still not working, got some errors this time (unfortunately I deleted all repos and tools related with Terminal (40+ gb together with the components installed)

claunia commented

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

Hey guys, I've created a pull request to fix compile warnings and errors, after it's merged, this issue can be closed :)

@ZgblKylin commented on GitHub (May 8, 2019): Hey guys, I've created a [pull request to fix compile warnings and errors](https://github.com/microsoft/Terminal/pull/549), after it's merged, this issue can be closed :)

claunia commented

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

Hey guys, I've created a pull request to fix compile warnings and errors, after it's merged, this issue can be closed :)

Would it solve the issue I mentioned above, it doesn't seem like it.

@taosx commented on GitHub (May 8, 2019): > Hey guys, I've created a [pull request to fix compile warnings and errors](https://github.com/microsoft/Terminal/pull/549), after it's merged, this issue can be closed :) Would it solve the issue I mentioned above, it doesn't seem like it.

claunia commented

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

@taosx Have you tried Release build? Maybe it's a Debug-specific error.

@Berrysoft commented on GitHub (May 8, 2019): @taosx Have you tried Release build? Maybe it's a Debug-specific error.

claunia commented

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

I have followed the following steps:

I upgraded to insider build 1903.

Installed VS2019 Community

Installed Visual Studio Build Tools 2017 and 2019

Added:
    1. C++ (v142 & v141) Universal Windows Platform tools
    2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0)
    3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools
    4. C++ ATL for v141 & v142 build tools (x86 & x64)
    5. C++/WinRT
Installed WinRT package

Run:
    1. git clone https://github.com/microsoft/Terminal.git
    2. git submodule update --init --recursive
    3. nuget restore OpenConsole.sln
Opened Project/Solution from VSCode

Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded)

Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance

And after all this:

Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808.

I have the same problem as you.

@Fordisk123 commented on GitHub (May 8, 2019): > I have followed the following steps: > > * I upgraded to insider build 1903. > * Installed VS2019 Community > * Installed Visual Studio Build Tools 2017 and 2019 > * Added: > > ``` > 1. C++ (v142 & v141) Universal Windows Platform tools > 2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0) > 3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools > 4. C++ ATL for v141 & v142 build tools (x86 & x64) > 5. C++/WinRT > ``` > > * Installed WinRT package > * Run: > > ``` > 1. git clone https://github.com/microsoft/Terminal.git > 2. git submodule update --init --recursive > 3. nuget restore OpenConsole.sln > ``` > > * Opened Project/Solution from VSCode > * Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded) > * Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance > > And after all this: > ![exception_base h](https://user-images.githubusercontent.com/5703052/57343880-cbf8a000-714d-11e9-8bce-0d6ab2140d82.png) > > > Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808. I have the same problem as you.

claunia commented

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

Hey guys, I've created a pull request to fix compile warnings and errors, after it's merged, this issue can be closed :)

Would it solve the issue I mentioned above, it doesn't seem like it.

It seems to be some bugs but not build errors.

You can deploy and run release build, and it works fine.

@ZgblKylin commented on GitHub (May 8, 2019): > > Hey guys, I've created a [pull request to fix compile warnings and errors](https://github.com/microsoft/Terminal/pull/549), after it's merged, this issue can be closed :) > > Would it solve the issue I mentioned above, it doesn't seem like it. It seems to be some bugs but not build errors. You can deploy and run release build, and it works fine.

claunia commented

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

emm, Does it possible to use this new Terminal with Win7?

@lycug commented on GitHub (May 8, 2019): emm, Does it possible to use this new Terminal with Win7?

claunia commented

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

Can anybody share an EXE

@jingzhou123 commented on GitHub (May 8, 2019): Can anybody share an EXE

claunia commented

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

@lycug short answer is no. Long answer - Win7 doesn't support WinRT, UWP and i guess a bunch of another stuff

@hapylestat commented on GitHub (May 8, 2019): @lycug short answer is no. Long answer - Win7 doesn't support WinRT, UWP and i guess a bunch of another stuff

claunia commented

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

emm, Does it possible to use this new Terminal with Win7?

Unfortunately not, it's built with UWP and some new features in 1903( new ConPTY API).

@ZgblKylin commented on GitHub (May 8, 2019): > emm, Does it possible to use this new Terminal with Win7? Unfortunately not, it's built with UWP and some new features in 1903( new ConPTY API).

claunia commented

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

Can anybody share an EXE

Unfortunately cannot, see About installation chapter in this issue and FAQ in readme.md.

@ZgblKylin commented on GitHub (May 8, 2019): > Can anybody share an EXE Unfortunately cannot, see ```About installation``` chapter in this issue and ```FAQ``` in ```readme.md```.

claunia commented

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

Sorry maybe this is out of context but, in the promotional video shows that in the terminal there's option Ubuntu, and other distros. I've installed Ubuntu WSL, but there's no option. Is this feature isn't available yet? Thank you.

@pr0ph0z commented on GitHub (May 8, 2019): Sorry maybe this is out of context but, in the [promotional video](https://youtu.be/8gw0rXPMMPE?t=13) shows that in the terminal there's option Ubuntu, and other distros. I've installed Ubuntu WSL, but there's no option. Is this feature isn't available yet? Thank you.

claunia commented

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

Sorry maybe this is out of context but, in the promotional video shows that in the terminal there's option Ubuntu, and other distros. I've installed Ubuntu WSL, but there's no option. Is this feature isn't available yet? Thank you.

Hi @pr0ph0z - you can add other shells into your windows terminal using the settings - should be reasonably obvious how to by looking at the ones that are in there already or check out Scott Hanselman's blog post around it : https://www.hanselman.com/blog/ANewConsoleForWindowsItsTheOpenSourceWindowsTerminal.aspx

@handyjellyfish commented on GitHub (May 8, 2019): > Sorry maybe this is out of context but, in the [promotional video](https://youtu.be/8gw0rXPMMPE?t=13) shows that in the terminal there's option Ubuntu, and other distros. I've installed Ubuntu WSL, but there's no option. Is this feature isn't available yet? Thank you. Hi @pr0ph0z - you can add other shells into your windows terminal using the settings - should be *reasonably* obvious how to by looking at the ones that are in there already or check out Scott Hanselman's blog post around it : https://www.hanselman.com/blog/ANewConsoleForWindowsItsTheOpenSourceWindowsTerminal.aspx

claunia commented

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

Is there supposed to be a menu and tab bar? I see them on screenshots of some builds people did, however over here, it's just a title bar and an acrylic terminal area. No settings on the title bar, nothing in the system menu (like in the old console window).

@glowtape commented on GitHub (May 8, 2019): Is there supposed to be a menu and tab bar? I see them on screenshots of some builds people did, however over here, it's just a title bar and an acrylic terminal area. No settings on the title bar, nothing in the system menu (like in the old console window).

claunia commented

@DHowett-MSFT commented on GitHub (May 8, 2019):

Press Control+T

From: Mario Goebbels notifications@github.com
Sent: Tuesday, May 7, 2019 10:04:42 PM
To: microsoft/Terminal
Cc: Dustin Howett; Mention
Subject: Re: [microsoft/Terminal] Guide for build new Terminal (#489)

Is there supposed to be a menu and tab bar? I see them on screenshots of some builds people did, however over here, it's just a title bar and an acrylic terminal area. No settings on the title bar, nothing in the system menu (like in the old console window).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FTerminal%2Fissues%2F489%23issuecomment-490348598&data=01%7C01%7Cduhowett%40microsoft.com%7Cf56e6c4af2a24aaf51d808d6d372ae6d%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=8nhZM1bgyDZaJW3bFtEg1FoTHwfCxVquKd1RuGTH%2BvU%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADNHLGWAJQGJBVYBHOF5MRDPUJNOVANCNFSM4HLHRKIQ&data=01%7C01%7Cduhowett%40microsoft.com%7Cf56e6c4af2a24aaf51d808d6d372ae6d%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=p11Rf3bfmTnnW0yAYyN1mizzeDU9mI%2Bp9ubIZvm%2BVsk%3D&reserved=0.

@DHowett-MSFT commented on GitHub (May 8, 2019): Press Control+T ________________________________ From: Mario Goebbels <notifications@github.com> Sent: Tuesday, May 7, 2019 10:04:42 PM To: microsoft/Terminal Cc: Dustin Howett; Mention Subject: Re: [microsoft/Terminal] Guide for build new Terminal (#489) Is there supposed to be a menu and tab bar? I see them on screenshots of some builds people did, however over here, it's just a title bar and an acrylic terminal area. No settings on the title bar, nothing in the system menu (like in the old console window). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FTerminal%2Fissues%2F489%23issuecomment-490348598&data=01%7C01%7Cduhowett%40microsoft.com%7Cf56e6c4af2a24aaf51d808d6d372ae6d%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=8nhZM1bgyDZaJW3bFtEg1FoTHwfCxVquKd1RuGTH%2BvU%3D&reserved=0>, or mute the thread<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADNHLGWAJQGJBVYBHOF5MRDPUJNOVANCNFSM4HLHRKIQ&data=01%7C01%7Cduhowett%40microsoft.com%7Cf56e6c4af2a24aaf51d808d6d372ae6d%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=p11Rf3bfmTnnW0yAYyN1mizzeDU9mI%2Bp9ubIZvm%2BVsk%3D&reserved=0>.

claunia commented

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

Sorry maybe this is out of context but, in the promotional video shows that in the terminal there's option Ubuntu, and other distros. I've installed Ubuntu WSL, but there's no option. Is this feature isn't available yet? Thank you.

Open settings, you can add wsl profile manually.

Press Ctrl + T will open a new tab, and show the menu dropdown, click Settings, then you'll see the profiles.json.

For example, I copied cmd profile, rename to WSL, change the commandline to wsl.exe, and give it a new guid:

{
    "guid": "{09dc5eef-6840-4050-ae69-21e55e6a2e62}",
    "name": "WSL",
    "colorscheme": "Campbell",
    "historySize": 9001,
    "snapOnInput": true,
    "cursorColor": "#FFFFFF",
    "cursorShape": "bar",
    "commandline": "wsl.exe",
    "fontFace": "Consolas",
    "fontSize": 12,
    "acrylicOpacity": 0.75,
    "useAcrylic": true,
    "closeOnExit": false,
    "padding": "0, 0, 0, 0"
}

@ZgblKylin commented on GitHub (May 8, 2019): > Sorry maybe this is out of context but, in the [promotional video](https://youtu.be/8gw0rXPMMPE?t=13) shows that in the terminal there's option Ubuntu, and other distros. I've installed Ubuntu WSL, but there's no option. Is this feature isn't available yet? Thank you. Open settings, you can add wsl profile manually. Press ```Ctrl + T``` will open a new tab, and show the menu dropdown, click ```Settings```, then you'll see the ```profiles.json```. For example, I copied ```cmd``` profile, rename to ```WSL```, change the ```commandline``` to ```wsl.exe```, and give it a new guid: ```json { "guid": "{09dc5eef-6840-4050-ae69-21e55e6a2e62}", "name": "WSL", "colorscheme": "Campbell", "historySize": 9001, "snapOnInput": true, "cursorColor": "#FFFFFF", "cursorShape": "bar", "commandline": "wsl.exe", "fontFace": "Consolas", "fontSize": 12, "acrylicOpacity": 0.75, "useAcrylic": true, "closeOnExit": false, "padding": "0, 0, 0, 0" } ```

claunia commented

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

I've followed the steps, built the solution successfully, but I'm getting this error when I try to deploy:
17>LINK : fatal error C1007: unrecognized flag '-Yu' in 'p2'
Anyone else getting the same thing?

@krzykli commented on GitHub (May 8, 2019): I've followed the steps, built the solution successfully, but I'm getting this error when I try to deploy: 17>LINK : fatal error C1007: unrecognized flag '-Yu' in 'p2' Anyone else getting the same thing?

claunia commented

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

Add some supplements if you encountered many errors in VS2017:

Open CMD.exe, run tools/razzle.cmd, it will set up some environment variables. Notice, it needs to run every time when you opening new CMD.exe window.
Run "git submodule update --init --recursive" to update sub modules.
Run "nuget restore OpenConsole.sln".
Open "OpenConsole.sln" in VS2017, make sure the "x64" or "x86" is selected base don your OS.
Start project should be set to "CascadiaPackage".
Back to CMD.exe window, which razzle.cmd was run above. Then run "msbuild OpenConsole.sln" to start the build. Or run "tools/bcz dbg" to build debug version. MSbuild will not report error but some warnings.
Back to VS2017, right click the solution name and select "Deploy Solution"
After the "Deploy Solution" completes, go to start menu to run "Windows Terminal (Preview)"

@wellsluo commented on GitHub (May 8, 2019): Add some supplements if you encountered many errors in VS2017: - Open CMD.exe, run tools/razzle.cmd, it will set up some environment variables. Notice, it needs to run every time when you opening new CMD.exe window. - Run "git submodule update --init --recursive" to update sub modules. - Run "nuget restore OpenConsole.sln". - Open "OpenConsole.sln" in VS2017, make sure the "x64" or "x86" is selected base don your OS. - Start project should be set to "CascadiaPackage". - Back to CMD.exe window, which razzle.cmd was run above. Then run "msbuild OpenConsole.sln" to start the build. Or run "tools/bcz dbg" to build debug version. MSbuild will not report error but some warnings. - Back to VS2017, right click the solution name and select "Deploy Solution" - After the "Deploy Solution" completes, go to start menu to run "Windows Terminal (Preview)"

claunia commented

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

git submodule update --init --recursive

Thanks @kbalint I had run it but had run it in the folder above where I ran git clone and I had not cd'd into the Terminal sub-directory. That error is now resolved and trying to build again.
Thanks for the help!
Robin

Now I am getting this error and now only 7 fail to build so it is progress:
error C3859: Failed to create virtual memory for PCH
Does anyone know how to fix this one?

hi, I have got this error too, I have gooogle it, and get some information.
so I closed some app in windows, only leave vs2017 and Chrome,
build it again, and everything is ok, build success.

:)

@iamting747 commented on GitHub (May 8, 2019): > > > git submodule update --init --recursive > > > > > > Thanks @kbalint I had run it but had run it in the folder above where I ran git clone and I had not cd'd into the Terminal sub-directory. That error is now resolved and trying to build again. > > Thanks for the help! > > Robin > > Now I am getting this error and now only 7 fail to build so it is progress: > > ``` > error C3859: Failed to create virtual memory for PCH > ``` > > Does anyone know how to fix this one? hi, I have got this error too, I have gooogle it, and get some information. so I closed some app in windows, only leave vs2017 and Chrome, build it again, and everything is ok, build success. :)

claunia commented

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

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): 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

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

Some time build project have an error :cann't find file winrt/TerminalApp.h.
We need install WinRT C++ library:
https://marketplace.visualstudio.com/items?itemName=CppWinRTTeam.cppwinrt101804264

@dybb8999 commented on GitHub (May 8, 2019): Some time build project have an error :cann't find file winrt/TerminalApp.h. We need install WinRT C++ library: https://marketplace.visualstudio.com/items?itemName=CppWinRTTeam.cppwinrt101804264

claunia commented

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

@handyjellyfish I have now managed to get further and am left with just one build error.
The problem was that I needed to use a different version of msbuild (noticed the nuget command references this other one) so ran these commands:

mkdir C:\Terminal
cd C:\Terminal
git init
git clone https://github.com/microsoft/Terminal.git
cd Terminal
git submodule update --init --recursive
"C:\Terminal\Terminal\dep\nuget\nuget.exe" restore OpenConsole.sln
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\bin\msbuild.exe" OpenConsole.sln

This results in a single error which is:

"C:\Terminal\Terminal\OpenConsole.sln" (default target) (1) ->
"C:\Terminal\Terminal\src\host\exe\Host.EXE.vcxproj.metaproj" (default target) (2) ->
"C:\Terminal\Terminal\src\host\exe\Host.EXE.vcxproj" (default target) (4) ->
"C:\Terminal\Terminal\src\tsf\tsf.vcxproj" (default target) (18) ->
(ClCompile target) ->
  c:\terminal\terminal\src\tsf\precomp.h(26): fatal error C1083: Cannot open include file: 'atlbase.h': No such file or
 directory [C:\Terminal\Terminal\src\tsf\tsf.vcxproj]

Is there a way to fix this last error then I think I am good to go and maybe the commands above are useful for others as took me a while to figure out.

@robinwilson16 commented on GitHub (May 8, 2019): @handyjellyfish I have now managed to get further and am left with just one build error. The problem was that I needed to use a different version of msbuild (noticed the nuget command references this other one) so ran these commands: ``` mkdir C:\Terminal cd C:\Terminal git init git clone https://github.com/microsoft/Terminal.git cd Terminal git submodule update --init --recursive "C:\Terminal\Terminal\dep\nuget\nuget.exe" restore OpenConsole.sln "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\bin\msbuild.exe" OpenConsole.sln ``` This results in a single error which is: ``` "C:\Terminal\Terminal\OpenConsole.sln" (default target) (1) -> "C:\Terminal\Terminal\src\host\exe\Host.EXE.vcxproj.metaproj" (default target) (2) -> "C:\Terminal\Terminal\src\host\exe\Host.EXE.vcxproj" (default target) (4) -> "C:\Terminal\Terminal\src\tsf\tsf.vcxproj" (default target) (18) -> (ClCompile target) -> c:\terminal\terminal\src\tsf\precomp.h(26): fatal error C1083: Cannot open include file: 'atlbase.h': No such file or directory [C:\Terminal\Terminal\src\tsf\tsf.vcxproj] ``` Is there a way to fix this last error then I think I am good to go and maybe the commands above are useful for others as took me a while to figure out.

claunia commented

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

Thanks @cybercatgurrl now I finally have it working. :)
I really wish I could have built it myself but at least now I can try it.

For anyone trying this you need to first install the certificate into the Local Computer Trusted Root Certification Authorities store (by clicking it and picking where you want it to be installed) then the msixbundle should install it.

@robinwilson16 commented on GitHub (May 8, 2019): Thanks @cybercatgurrl now I finally have it working. :) I really wish I could have built it myself but at least now I can try it. _For anyone trying this you need to first install the certificate into the Local Computer Trusted Root Certification Authorities store (by clicking it and picking where you want it to be installed) then the msixbundle should install it._

claunia commented

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

can't see deploy after building. anyway we can run in cmd?

Do you see the Solution Explorer side menu?
If not, then press Ctrl+Alt+L or go to View -> Solution Explorer.
At the top of the Solution Explorer, the top most item is: Solution 'OpenConsole' (47 projects).
Right click it and choose Deploy Solution from the context menu.

saw it, deployed but got errors.

@xdagee commented on GitHub (May 8, 2019): > > can't see deploy after building. anyway we can run in cmd? > > Do you see the Solution Explorer side menu? > If not, then press Ctrl+Alt+L or go to View -> Solution Explorer. > At the top of the Solution Explorer, the top most item is: Solution 'OpenConsole' (47 projects). > Right click it and choose Deploy Solution from the context menu. > > ![image](https://user-images.githubusercontent.com/16970186/57322619-3c7acf00-7104-11e9-815e-4d7427fab4bf.png) saw it, deployed but got errors. ![CaptureErrorDeploying](https://user-images.githubusercontent.com/14103448/57366873-66210e00-7177-11e9-9b9f-ccf1b510e1a6.PNG)

claunia commented

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

I have followed the following steps:

I upgraded to insider build 1903.

Installed VS2019 Community

Installed Visual Studio Build Tools 2017 and 2019

Added:
    1. C++ (v142 & v141) Universal Windows Platform tools
    2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0)
    3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools
    4. C++ ATL for v141 & v142 build tools (x86 & x64)
    5. C++/WinRT
Installed WinRT package

Run:
    1. git clone https://github.com/microsoft/Terminal.git
    2. git submodule update --init --recursive
    3. nuget restore OpenConsole.sln
Opened Project/Solution from VSCode

Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded)

Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance

And after all this:

Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808.
I have the same problem as you.

I have followed the following steps:

I upgraded to insider build 1903.

Installed VS2019 Community

Installed Visual Studio Build Tools 2017 and 2019

Added:
    1. C++ (v142 & v141) Universal Windows Platform tools
    2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0)
    3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools
    4. C++ ATL for v141 & v142 build tools (x86 & x64)
    5. C++/WinRT
Installed WinRT package

Run:
    1. git clone https://github.com/microsoft/Terminal.git
    2. git submodule update --init --recursive
    3. nuget restore OpenConsole.sln
Opened Project/Solution from VSCode

Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded)

Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance

And after all this:

Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808.

Edit: I think the team had a reason there's not a binary, it's not ready yet.
I think I'll wait till mid June. Have some good sprints!

@Berrysoft still not working, got some errors this time (unfortunately I deleted all repos and tools related with Terminal (40+ gb together with the components installed)

How did you succeed at first time? I even got tons of errors.

@hereistheusername commented on GitHub (May 8, 2019): > > I have followed the following steps: > > > > * I upgraded to insider build 1903. > > * Installed VS2019 Community > > * Installed Visual Studio Build Tools 2017 and 2019 > > * Added: > > > > ``` > > 1. C++ (v142 & v141) Universal Windows Platform tools > > 2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0) > > 3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools > > 4. C++ ATL for v141 & v142 build tools (x86 & x64) > > 5. C++/WinRT > > ``` > > > > > > > > * Installed WinRT package > > * Run: > > > > ``` > > 1. git clone https://github.com/microsoft/Terminal.git > > 2. git submodule update --init --recursive > > 3. nuget restore OpenConsole.sln > > ``` > > > > > > > > * Opened Project/Solution from VSCode > > * Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded) > > * Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance > > > > And after all this: > > ![exception_base h](https://user-images.githubusercontent.com/5703052/57343880-cbf8a000-714d-11e9-8bce-0d6ab2140d82.png) > > > Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808. > > I have the same problem as you. > I have followed the following steps: > > * I upgraded to insider build 1903. > * Installed VS2019 Community > * Installed Visual Studio Build Tools 2017 and 2019 > * Added: > > ``` > 1. C++ (v142 & v141) Universal Windows Platform tools > 2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0) > 3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools > 4. C++ ATL for v141 & v142 build tools (x86 & x64) > 5. C++/WinRT > ``` > > * Installed WinRT package > * Run: > > ``` > 1. git clone https://github.com/microsoft/Terminal.git > 2. git submodule update --init --recursive > 3. nuget restore OpenConsole.sln > ``` > > * Opened Project/Solution from VSCode > * Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded) > * Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance > > And after all this: > ![exception_base h](https://user-images.githubusercontent.com/5703052/57343880-cbf8a000-714d-11e9-8bce-0d6ab2140d82.png) > > > Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808. > > Edit: I think the team had a reason there's not a binary, it's not ready yet. > I think I'll wait till mid June. Have some good sprints! > > @Berrysoft still not working, got some errors this time (unfortunately I deleted all repos and tools related with Terminal (40+ gb together with the components installed) How did you succeed at first time? I even got tons of errors.

claunia commented

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

I have followed the following steps:
* I upgraded to insider build 1903.

* Installed VS2019 Community

* Installed Visual Studio Build Tools 2017 and 2019

* Added:
    1. C++ (v142 & v141) Universal Windows Platform tools
    2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0)
    3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools
    4. C++ ATL for v141 & v142 build tools (x86 & x64)
    5. C++/WinRT
* Installed WinRT package

* Run:
    1. git clone https://github.com/microsoft/Terminal.git
    2. git submodule update --init --recursive
    3. nuget restore OpenConsole.sln
* Opened Project/Solution from VSCode

* Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded)

* Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance
And after all this:

Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808.

Edit: I think the team had a reason there's not a binary, it's not ready yet.
I think I'll wait till mid June. Have some good sprints!

@Berrysoft still not working, got some errors this time (unfortunately I deleted all repos and tools related with Terminal (40+ gb together with the components installed)

this work, ty

@newbalancem5 commented on GitHub (May 8, 2019): > > > I have followed the following steps: > > * I upgraded to insider build 1903. > > * Installed VS2019 Community > > * Installed Visual Studio Build Tools 2017 and 2019 > > * Added: > > > ``` > 1. C++ (v142 & v141) Universal Windows Platform tools > 2. Windows 10 SDK (10.0.18362.0 & 10.0.17763.0) > 3. MSVC v142 & v141 – VS 2019 C++ x64/x86 build tools > 4. C++ ATL for v141 & v142 build tools (x86 & x64) > 5. C++/WinRT > ``` > > * Installed WinRT package > > * Run: > > > ``` > 1. git clone https://github.com/microsoft/Terminal.git > 2. git submodule update --init --recursive > 3. nuget restore OpenConsole.sln > ``` > > * Opened Project/Solution from VSCode > > * Right-click "Solution 'OpenConsole'" and "Build Solution" => no errors (succeeded) > > * Right-click "Terminal -> WindowsTerminal" and Debug -> New Instance > > > And after all this: > ![exception_base h](https://user-images.githubusercontent.com/5703052/57343880-cbf8a000-714d-11e9-8bce-0d6ab2140d82.png) > > > Exception thrown at 0x00007FFB6AF4A839 in WindowsTerminal.exe: Microsoft C++ exception: winrt::hresult_error at memory location 0x00000086DA31E808. > > Edit: I think the team had a reason there's not a binary, it's not ready yet. > I think I'll wait till mid June. Have some good sprints! > > @Berrysoft still not working, got some errors this time (unfortunately I deleted all repos and tools related with Terminal (40+ gb together with the components installed) this work, ty

claunia commented

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

@cybercatgurrl please don't use github threads as a place to redistribute third-party binaries. There's a reason binaries aren't available for download quite yet.

@hereistheusername Try deploying "CascadiaPackage" to run the new terminal. If you're having any build issues arround "Terminal.TerminalSettings", try manually building the TerminalSettings project first. There seems to be some sort of issue with the build order, where it doesn't always build it first.

@zadjii-msft commented on GitHub (May 8, 2019): @cybercatgurrl please don't use github threads as a place to redistribute third-party binaries. There's a reason binaries aren't available for download quite yet. @hereistheusername Try deploying "CascadiaPackage" to run the new terminal. If you're having any build issues arround "Terminal.TerminalSettings", try manually building the TerminalSettings project first. There seems to be some sort of issue with the build order, where it doesn't always build it first.

claunia commented

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

I'd rather sit and wait for and update rather than download 16 gig worth vstudio

@ghost commented on GitHub (May 8, 2019): I'd rather sit and wait for and update rather than download 16 gig worth vstudio

claunia commented

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

When I used Git bash，I was told bash：nuget：command not found
How to solve it？

Terminal/dep/nuget. You can find it there, and add the directory to path, or copy it to root directory of the project.

@hereistheusername commented on GitHub (May 8, 2019): > When I used Git bash，I was told `bash：nuget：command not found` > How to solve it？ Terminal/dep/nuget. You can find it there, and add the directory to path, or copy it to root directory of the project.

claunia commented

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

@cybercatgurrl please don't use github threads as a place to redistribute third-party binaries. There's a reason binaries aren't available for download quite yet.

@hereistheusername Try deploying "CascadiaPackage" to run the new terminal. If you're having any build issues arround "Terminal.TerminalSettings", try manually building the TerminalSettings project first. There seems to be some sort of issue with the build order, where it doesn't always build it first.

Ok. I'll try orderly.

@hereistheusername commented on GitHub (May 8, 2019): > @cybercatgurrl please don't use github threads as a place to redistribute third-party binaries. There's a reason binaries aren't available for download quite yet. > > @hereistheusername Try deploying "CascadiaPackage" to run the new terminal. If you're having any build issues arround "Terminal.TerminalSettings", try manually building the TerminalSettings project first. There seems to be some sort of issue with the build order, where it doesn't always build it first. Ok. I'll try orderly.

claunia commented

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

Where does one even download Visual Studio 2017? All I can find on Microsoft's site is 2019.

@sodle commented on GitHub (May 8, 2019): Where does one even download Visual Studio 2017? All I can find on Microsoft's site is 2019.

claunia commented

https://visualstudio.microsoft.com/vs/older-downloads/

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

Where does one even download Visual Studio 2017? All I can find on Microsoft's site is 2019.

@newbalancem5 commented on GitHub (May 8, 2019): > Where does one even download Visual Studio 2017? All I can find on Microsoft's site is 2019. https://visualstudio.microsoft.com/vs/older-downloads/

claunia commented

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

I've followed the steps, built the solution successfully, but I'm getting this error when I try to deploy:
17>LINK : fatal error C1007: unrecognized flag '-Yu' in 'p2'
Anyone else getting the same thing?

Me too.

@vsavic commented on GitHub (May 8, 2019): > > > I've followed the steps, built the solution successfully, but I'm getting this error when I try to deploy: > 17>LINK : fatal error C1007: unrecognized flag '-Yu' in 'p2' > Anyone else getting the same thing? Me too.

claunia commented

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

It absolutely needs to be put into the Readme that you can NOT use Visual Studio 2019, especially since Microsoft is known for making legacy software harder to access (including Visual Studio 2017, which after uninstalling it I still don't know how to re-download).

Using VS2019's update tool doesn't work either.

VS2019 works. We need to retarget the Solution File and Update the Framework to use 4.6 Then Build the Solution. It worked for me

@creatorsrk commented on GitHub (May 8, 2019): > > > It absolutely needs to be put into the Readme that you can NOT use Visual Studio 2019, especially since Microsoft is known for making legacy software harder to access (including Visual Studio 2017, which after uninstalling it I still don't know how to re-download). > > Using VS2019's update tool doesn't work either. VS2019 works. We need to retarget the Solution File and Update the Framework to use 4.6 Then Build the Solution. It worked for me

claunia commented

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

@zadjii-msft I'm really liking the new console and the fact it is open source and we can try out out early in dev and was able to set it up with PowerShell 6, WSL and am SSH'd into my Ubuntu box as I speak. However whilst I am a dev who uses VS 2017/2019 every day I couldn't get this to build whatever I tried so was only able to try it because of the binary that was kindly posted. Could more complete instructions be provided of a single working approach to save everyone running into the same issues if you will not allow binaries to be shared to avoid some of the frustrations?

@robinwilson16 commented on GitHub (May 8, 2019): @zadjii-msft I'm really liking the new console and the fact it is open source and we can try out out early in dev and was able to set it up with PowerShell 6, WSL and am SSH'd into my Ubuntu box as I speak. However whilst I am a dev who uses VS 2017/2019 every day I couldn't get this to build whatever I tried so was only able to try it because of the binary that was kindly posted. Could more complete instructions be provided of a single working approach to save everyone running into the same issues if you will not allow binaries to be shared to avoid some of the frustrations?

claunia commented

@handyjellyfish commented on GitHub (May 9, 2019):

@zadjii-msft I'm really liking the new console and the fact it is open source and we can try out out early in dev and was able to set it up with PowerShell 6, WSL and am SSH'd into my Ubuntu box as I speak. However whilst I am a dev who uses VS 2017/2019 every day I couldn't get this to build whatever I tried so was only able to try it because of the binary that was kindly posted. Could more complete instructions be provided of a single working approach to save everyone running into the same issues if you will not allow binaries to be shared to avoid some of the frustrations?

@robinwilson16 - after my fun with VS2019 Build Tools I got someone to run it in VS2017 and it was a breeze. These were the steps we took:

Install Windows 10 1903 (May Update)
CLONE (don't download) the repository.
Run the command "git submodule update --init --recursive" in the folder you cloned the repo
Open the solution in Visual Studio.
Make sure that nuget runs (should warn you that there are packages to restore - then restore).
Switch the active project to Cascadia Package.
Switch configuration to release.
Switch platform to x64.
Build and run as normal (f5) - this will install the package on your system and you should be good to go.

As an aside I'd guess that VS2019 would work exactly the same, just need to change the platform toolset to VS2019, but haven't tried it.

I don't think it's quite ready for command line building - you can get it done, but with the self signing of the installer etc etc it's just a bit convoluted.

@handyjellyfish commented on GitHub (May 9, 2019): > @zadjii-msft I'm really liking the new console and the fact it is open source and we can try out out early in dev and was able to set it up with PowerShell 6, WSL and am SSH'd into my Ubuntu box as I speak. However whilst I am a dev who uses VS 2017/2019 every day I couldn't get this to build whatever I tried so was only able to try it because of the binary that was kindly posted. Could more complete instructions be provided of a single working approach to save everyone running into the same issues if you will not allow binaries to be shared to avoid some of the frustrations? @robinwilson16 - after my fun with VS2019 Build Tools I got someone to run it in VS2017 and it was a breeze. These were the steps we took: - Install Windows 10 1903 (May Update) - CLONE (don't download) the repository. - Run the command "git submodule update --init --recursive" in the folder you cloned the repo - Open the solution in Visual Studio. - Make sure that nuget runs (should warn you that there are packages to restore - then restore). - Switch the active project to Cascadia Package. - Switch configuration to release. - Switch platform to x64. - Build and run as normal (f5) - this will install the package on your system and you should be good to go. As an aside I'd *guess* that VS2019 would work exactly the same, just need to change the platform toolset to VS2019, but haven't tried it. I don't think it's quite ready for command line building - you can get it done, but with the self signing of the installer etc etc it's just a bit convoluted.

claunia commented

@chunliu commented on GitHub (May 9, 2019):

See #565 for build with VS2019 and from command line.

@chunliu commented on GitHub (May 9, 2019): See #565 for build with VS2019 and from command line.

claunia commented

@vstoms commented on GitHub (May 9, 2019):

Quick blogpost about how to build Windows Terminal in Azure Dev-Ops: https://blog.stomsvik.com/posts/2019/terminal-azure-devops/

@vstoms commented on GitHub (May 9, 2019): Quick blogpost about how to build Windows Terminal in Azure Dev-Ops: https://blog.stomsvik.com/posts/2019/terminal-azure-devops/

claunia commented

@knilecrack commented on GitHub (May 9, 2019):

gotta love github

@knilecrack commented on GitHub (May 9, 2019): gotta love github

claunia commented

@snooopcatt commented on GitHub (May 9, 2019):

@robinwilson16

c:\terminal\terminal\src\tsf\precomp.h(26): fatal error C1083: Cannot open include file: 'atlbase.h': No such file or directory [C:\Terminal\Terminal\src\tsf\tsf.vcxproj]

you need to install C++ ATL. you can do it via same tool you use to install visual studio

@snooopcatt commented on GitHub (May 9, 2019): @robinwilson16 > c:\terminal\terminal\src\tsf\precomp.h(26): fatal error C1083: Cannot open include file: 'atlbase.h': No such file or directory [C:\Terminal\Terminal\src\tsf\tsf.vcxproj] you need to install C++ ATL. you can do it via same tool you use to install visual studio

claunia commented

@Remi-Tuy commented on GitHub (May 9, 2019):

hello. can I download the binary file of you build ? I don`t want to build it . no environment . 😆

@clearcodecn did you manage to get a binary from anybody ?

Does anybody have a link to the binary ? No environment to build on my machines :/

@Remi-Tuy commented on GitHub (May 9, 2019): > hello. can I download the binary file of you build ? I don`t want to build it . no environment . 😆 @clearcodecn did you manage to get a binary from anybody ? Does anybody have a link to the binary ? No environment to build on my machines :/

claunia commented

@l1005268416 commented on GitHub (May 9, 2019):

Thank you.

@l1005268416 commented on GitHub (May 9, 2019): Thank you.

claunia commented

@davidfries commented on GitHub (May 9, 2019):

@Remi-Tuy

I got a link from a reddit thread, just installed on an updated Win10 insider VM and it works!

Here's a link (edited: please don’t share binaries) for a build. This is not my build, and you're responsible for any damages that result from installing. From this thread

@davidfries commented on GitHub (May 9, 2019): @Remi-Tuy I got a link from a reddit thread, just installed on an updated Win10 insider VM and it works! ![term](https://user-images.githubusercontent.com/12002376/57466803-55dc6200-724f-11e9-88e5-6dc826c05086.gif) Here's a link (edited: please don’t share binaries) for a build. This is not my build, and you're responsible for any damages that result from installing. [From this thread](https://old.reddit.com/r/programming/comments/bltm2e/the_new_windows_terminal_youtube_promo/emrljnz/)

claunia commented

@vsavic commented on GitHub (May 9, 2019):

Any idea why this error:

@vsavic commented on GitHub (May 9, 2019): Any idea why this error: <img src="https://image.prntscr.com/image/TMNL97OlTp2hL1bpzB61tA.png"/>

claunia commented

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

Any idea why this error:

@vsavic Just had the exact error as you. Retargeted the whole solution to v142, and then manually right clicked TerminalApp in the Solution Explorer, and then Add->Reference to TerminalSettings

@venabled commented on GitHub (May 10, 2019): > Any idea why this error: > @vsavic Just had the exact error as you. Retargeted the whole solution to v142, and then manually right clicked `TerminalApp` in the Solution Explorer, and then Add->Reference to `TerminalSettings`

claunia commented

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

i have added WSL setting in profile.json,but i can't open WLS window.

@jintianzhouyine commented on GitHub (May 10, 2019): i have added WSL setting in profile.json,but i can't open WLS window. ![image](https://user-images.githubusercontent.com/23045159/57498874-2c373f80-7310-11e9-82c3-70129b604dc0.png)

claunia commented

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

非常感谢。Windows Terminal我已利用vs2017编译部署成功。

1005268416@qq.com

From: blurredpixel
Date: 2019-05-09 23:47
To: microsoft/Terminal
CC: l1005268416; Comment
Subject: Re: [microsoft/Terminal] Guide for build and installation (#489)
@Remi-Tuy
I got a link from a reddit thread, just installed on an updated Win10 insider VM and it works!
Here's a link for a build. This is not my build, and you're responsible for any damages that result from installing. From this thread
―
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@l1005268416 commented on GitHub (May 10, 2019): 非常感谢。Windows Terminal我已利用vs2017编译部署成功。 1005268416@qq.com From: blurredpixel Date: 2019-05-09 23:47 To: microsoft/Terminal CC: l1005268416; Comment Subject: Re: [microsoft/Terminal] Guide for build and installation (#489) @Remi-Tuy I got a link from a reddit thread, just installed on an updated Win10 insider VM and it works! Here's a link for a build. This is not my build, and you're responsible for any damages that result from installing. From this thread ― You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

claunia commented

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

你如果已经编译成功的话，可以按照以下步骤来安装Windows Terminal：
1.选中CascadiaPackage项目，点击鼠标右键，选择部署，等待其部署成功。

2.部署成功后，开始菜单中就会显示Windows Terminal，启动它就可以了。

3.效果图：ctrl+T 可以打开新标签。

1005268416@qq.com

From: FrancescoPacifico
Date: 2019-05-10 03:31
To: microsoft/Terminal
CC: l1005268416; Comment
Subject: Re: [microsoft/Terminal] Guide for build and installation (#489)
Hi, I've succesfully built the solution:

But when I try to deploy it I get this error:

Can you help me getting rid of this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@l1005268416 commented on GitHub (May 10, 2019): 你如果已经编译成功的话，可以按照以下步骤来安装Windows Terminal： 1.选中CascadiaPackage项目，点击鼠标右键，选择部署，等待其部署成功。 2.部署成功后，开始菜单中就会显示Windows Terminal，启动它就可以了。 3.效果图：ctrl+T 可以打开新标签。 1005268416@qq.com From: FrancescoPacifico Date: 2019-05-10 03:31 To: microsoft/Terminal CC: l1005268416; Comment Subject: Re: [microsoft/Terminal] Guide for build and installation (#489) Hi, I've succesfully built the solution: But when I try to deploy it I get this error: Can you help me getting rid of this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

claunia commented

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

I followed the guide and tried to deploy the project, but failed with so many MIDL2003 errors.

My Env:
Win 10,
SDK 10.0.18362.0
VS2017
Any prerequisites installed I think. I cannot found any issues like mine.

I also tried 10.0.17763.0 in VS2017 but it tells I have to deploy with the 10.0.18362.0.
Could anyone can tell me the solution ? I really hope to try this new one.

@klize commented on GitHub (May 10, 2019): I followed the guide and tried to deploy the project, but failed with so many MIDL2003 errors. My Env: Win 10, SDK 10.0.18362.0 VS2017 Any prerequisites installed I think. I cannot found any issues like mine. I also tried 10.0.17763.0 in VS2017 but it tells I have to deploy with the 10.0.18362.0. Could anyone can tell me the solution ? I really hope to try this new one.

claunia commented

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

Even if you need Windows 10 "1903" to run (and possibly other tools installed locally), why not publish the Cascadia package as a build artifact as a last step in the already existing Azure Pipelines CI?

@fredrikaverpil commented on GitHub (May 10, 2019): Even if you need Windows 10 "1903" to run (and possibly other tools installed locally), why not publish the Cascadia package as a build artifact as a last step in the already existing Azure Pipelines CI?

claunia commented

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

Even if you need Windows 10 "1903" to run (and possibly other tools installed locally), why not publish the Cascadia package as a build artifact as a last step in the already existing Azure Pipelines CI?

Thanks, that may work. I realize that i cannot get os build 1903 , as i am not the insider. just preparing the sdk doesn't solve my problem. (vs only reads the system version 1809 )

@klize commented on GitHub (May 10, 2019): > Even if you need Windows 10 "1903" to run (and possibly other tools installed locally), why not publish the Cascadia package as a build artifact as a last step in the already existing Azure Pipelines CI? Thanks, that may work. I realize that i cannot get os build 1903 , as i am not the insider. just preparing the sdk doesn't solve my problem. (vs only reads the system version 1809 )

claunia commented

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

Quick blogpost about how to build Windows Terminal in Azure Dev-Ops: https://blog.stomsvik.com/posts/2019/terminal-azure-devops/

Thanks for the tutorial. This seems to be the best way to build since you don't need to install VS2019 or any libs.

@chithangduong commented on GitHub (May 10, 2019): > Quick blogpost about how to build Windows Terminal in Azure Dev-Ops: https://blog.stomsvik.com/posts/2019/terminal-azure-devops/ Thanks for the tutorial. This seems to be the best way to build since you don't need to install VS2019 or any libs.

claunia commented

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

Can anybody clarify why the 10.0.18362.0 SDK is needed? will this terminal not run on Windows 10 versions before 1903?

I was excited about the new terminal and tried to build the app in VS but then I learned that you actually need a yet unreleased version of Windows in order to do it...

@sryze commented on GitHub (May 10, 2019): Can anybody clarify why the 10.0.18362.0 SDK is needed? will this terminal not run on Windows 10 versions before 1903? I was excited about the new terminal and tried to build the app in VS but then I learned that you actually need a yet unreleased version of Windows in order to do it...

claunia commented

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

@sryze Because we depend on features that only shipped in the newest version of Windows, namely certain XAML Islands functionality.

@zadjii-msft commented on GitHub (May 10, 2019): @sryze Because we depend on features that only shipped in the newest version of Windows, namely certain XAML Islands functionality.

claunia commented

2026-01-30 22:01:22 +00:00

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

Though this is not an serious issue VS/msbuild shows double slashes in project paths in build output.

@Biswa96 commented on GitHub (May 10, 2019): Though this is not an serious issue VS/msbuild shows double slashes in project paths in build output.

claunia commented

@krokofant commented on GitHub (May 11, 2019):

If you've managed to deploy once via Visual Studio you can use the devenv.exe to do it smoothly via command-line next time:

devenv .\OpenConsole.sln /Deploy

I'm using posh-vsdev to enter the VS dev environment but you might also just reference that executable directly.

@krokofant commented on GitHub (May 11, 2019): If you've managed to deploy once via Visual Studio you can use the devenv.exe to do it smoothly via command-line next time: ```powershell devenv .\OpenConsole.sln /Deploy ``` I'm using [posh-vsdev](https://github.com/rbuckton/posh-vsdev) to enter the VS dev environment but you might also just reference that executable directly.

claunia commented

2026-01-30 22:01:22 +00:00

@paddymcd-MSFT commented on GitHub (May 11, 2019):

Worked through a few issues but I've got OpenConsole.sln building from the command-line with VS2019 installed. Thanks to @olgaark

You need the following optional Workloads / Components installed:

On the Workloads tab

Select the "Universal Windows Platform development" Workload
In the Installation details on the left under the Optional elements select
- "C++ (v141) Universal Windows Platform tools"
- "Windows 10 SDK (10.0.18362.0)"

For x86 / x64 builds (some of the SDKs may not be necessary - I haven't checked)

On the Individual components tab

Under "Compilers, build tools, and runtimes"
- "C++ Universal Windows Platform runtime for v142 build tools"
- "MSVC v141 - VS 2017 C++ x64/x86 build tools (v14.16)"
Under "SDKs, libraries, and frameworks"
- "C++ ATL for v141 build tools (x86 & x64)"
- "C++ MFC for v141 build tools (x86 & x64)"

Then running msbuild.exe OpenConsole.sln using msbuild.exe from the VS2019 installation should work. This does not require any dev console or use of vcvarsall.bat.

@paddymcd-MSFT commented on GitHub (May 11, 2019): Worked through a few issues but I've got OpenConsole.sln building from the command-line with VS2019 installed. Thanks to @olgaark You need the following optional Workloads / Components installed: On the Workloads tab - Select the "Universal Windows Platform development" Workload - In the Installation details on the left under the Optional elements select - "C++ (v141) Universal Windows Platform tools" - "Windows 10 SDK (10.0.18362.0)" For x86 / x64 builds (some of the SDKs may not be necessary - I haven't checked) On the Individual components tab - Under "Compilers, build tools, and runtimes" - "C++ Universal Windows Platform runtime for v142 build tools" - "MSVC v141 - VS 2017 C++ x64/x86 build tools (v14.16)" - Under "SDKs, libraries, and frameworks" - "C++ ATL for v141 build tools (x86 & x64)" - "C++ MFC for v141 build tools (x86 & x64)" Then running `msbuild.exe OpenConsole.sln` using msbuild.exe from the VS2019 installation should work. This does not require any dev console or use of vcvarsall.bat.

claunia commented

2026-01-30 22:01:22 +00:00

@upupming commented on GitHub (May 11, 2019):

@ZgblKylin You are my hero, thanks! For me, I forgot to change from arm64 to x64 build type. You saved me, thanks again.

Another question, 4.1 & 4.2 are true problems I faced, but why didn't Microsoft fix them? Okay, I see the PRs you mentioned, hope they will be merged or resolved someday!

@upupming commented on GitHub (May 11, 2019): @ZgblKylin You are my hero, thanks! For me, I forgot to change from `arm64` to `x64` build type. You saved me, thanks again. Another question, 4.1 & 4.2 are true problems I faced, but why didn't Microsoft fix them? Okay, I see the PRs you mentioned, hope they will be merged or resolved someday!

claunia commented

@krystian-mw commented on GitHub (May 11, 2019):

========== Build: 0 succeeded, 45 failed, 2 up-to-date, 0 skipped ==========

You forgot to change the architecture. Right next the "Debug" dropdown (next to the redo button) you should change the architecture to your own system. I initially thought to myself there's no way I'll get it working :P

@krystian-mw commented on GitHub (May 11, 2019): > ========== Build: 0 succeeded, 45 failed, 2 up-to-date, 0 skipped ========== You forgot to change the architecture. Right next the "Debug" dropdown (next to the redo button) you should change the architecture to your own system. I initially thought to myself there's no way I'll get it working :P

claunia commented

@roshan-raj commented on GitHub (May 12, 2019):

I am currently running Windows 1903, Build 18334.19h1 , but i have set the target version to 18362, as i had downloaded 10.0; Build 18362.
SO now should i be upgrading my windows or is there a workaround ?

@roshan-raj commented on GitHub (May 12, 2019): ![image](https://user-images.githubusercontent.com/31264823/57577753-98927a00-749b-11e9-81c0-3f3e7aa70d44.png) I am currently running Windows 1903, Build 18334.19h1 , but i have set the target version to 18362, as i had downloaded 10.0; Build 18362. SO now should i be upgrading my windows or is there a workaround ?

claunia commented

@CaptainMorgans commented on GitHub (May 12, 2019):

How do I do this in the "Terminal" folder which doesn't exist as a folder in the console?

Run git submodule update --init --recursive in Terminal folder

I can however find the CascadiaPackage folder.

I managed to run this command in the CascadiaPackage folder and yet I still get errors "wil/Common.h: No such file or directory"

@CaptainMorgans commented on GitHub (May 12, 2019): How do I do this in the "Terminal" folder which doesn't exist as a folder in the console? Run git submodule update --init --recursive in Terminal folder I can however find the CascadiaPackage folder. I managed to run this command in the CascadiaPackage folder and yet I still get errors "wil/Common.h: No such file or directory"

claunia commented

2026-01-30 22:01:24 +00:00

@christian-korneck commented on GitHub (May 12, 2019):

This is how it worked for me:

upgrade to Windows 10 1903 (there’s no working MediaCreation tool available for 1903 yet, an easy way to obtain it is to generate an ISO file with: https://uup.rg-adguard.net/)
enable Developer Mode (to be able to install unsigned UWP apps out of Visual Studio)

reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock /v AllowDevelopmentWithoutDevLicense /d 0 /t REG_DWORD /f

install Visual Studio 2019 Community ( https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16 )
- make sure to install the Visual Studio .NET desktop, UWP, C++ Desktop roles
- in addition, in individual components, also select all C++ v142 components, C++ ATL support and the Windows 10 SDK 10.0.18362.0
after the Visual Studio installation, add the C++/WinRT extension from https://marketplace.visualstudio.com/items?itemName=CppWinRTTeam.cppwinrt101804264
download nuget.exe and place it in a folder that is part of the PATH env var (i.e. c:\windows\system32)
https://www.nuget.org/downloads

git clone https://github.com/microsoft/Terminal.git
cd Terminal
git submodule update --init --recursive
nuget restore OpenConsole.sln

open OpenConsole.sln in Visual Studio 2019. Switch the configuration (in the menu bar) to Release / x64.
in the Solution explorer on the right, right-click on the CascadiaPackage project and select Deploy. This builds all required projects and, if successful, installs the UWP app in Windows.

Result: There's a new start menu entry Windows Terminal (Preview)

@christian-korneck commented on GitHub (May 12, 2019): This is how it worked for me: - upgrade to Windows 10 1903 (there’s no working MediaCreation tool available for 1903 yet, an easy way to obtain it is to generate an ISO file with: https://uup.rg-adguard.net/) - enable Developer Mode (to be able to install unsigned UWP apps out of Visual Studio) ``` reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock /v AllowDevelopmentWithoutDevLicense /d 0 /t REG_DWORD /f ``` - install Visual Studio 2019 Community ( https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16 ) - make sure to install the Visual Studio `.NET desktop`, `UWP`, `C++ Desktop` roles - in addition, in `individual components`, also select all `C++ v142` components, `C++ ATL support` and the Windows 10 SDK `10.0.18362.0` - after the Visual Studio installation, add the `C++/WinRT` extension from https://marketplace.visualstudio.com/items?itemName=CppWinRTTeam.cppwinrt101804264 - download `nuget.exe` and place it in a folder that is part of the PATH env var (i.e. `c:\windows\system32`) https://www.nuget.org/downloads ``` git clone https://github.com/microsoft/Terminal.git cd Terminal git submodule update --init --recursive nuget restore OpenConsole.sln ``` - open `OpenConsole.sln` in Visual Studio 2019. Switch the configuration (in the menu bar) to `Release` / `x64`. - in the `Solution explorer` on the right, right-click on the `CascadiaPackage` project and select `Deploy`. This builds all required projects and, if successful, installs the UWP app in Windows. Result: There's a new start menu entry `Windows Terminal (Preview)`

claunia commented

@CaptainMorgans commented on GitHub (May 12, 2019):

@christian-korneck Thank you for the steps. All worked up until the Deploy step.

========== Build: 21 succeeded, 4 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========

Errors below

Severity Code Description Project File Line Suppression State
Error C1007 unrecognized flag '-Yu' in 'p2' TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1

Error LNK1257 code generation failed TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1

Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Parameter 'chord' of Procedure 'SetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ] TerminalApp C:\Terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 62

Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.IKeyBindings [ RuntimeClass 'TerminalApp.AppKeyBindings' ] TerminalApp C:\Terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 59

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

Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7

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

@CaptainMorgans commented on GitHub (May 12, 2019): @christian-korneck Thank you for the steps. All worked up until the Deploy step. ========== Build: 21 succeeded, 4 failed, 0 up-to-date, 0 skipped ========== ========== Deploy: 0 succeeded, 0 failed, 0 skipped ========== Errors below ========= Severity Code Description Project File Line Suppression State Error C1007 unrecognized flag '-Yu' in 'p2' TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1 Error LNK1257 code generation failed TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1 Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Parameter 'chord' of Procedure 'SetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ] TerminalApp C:\Terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 62 Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.IKeyBindings [ RuntimeClass 'TerminalApp.AppKeyBindings' ] TerminalApp C:\Terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 59 Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\AppHost.h 7 Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\AppHost.h 7 Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7 Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7 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 ![image](https://user-images.githubusercontent.com/3514724/57584952-a965de80-74e1-11e9-819b-35b5b3cfb0df.png)

claunia commented

2026-01-30 22:01:24 +00:00

@mehulmpt commented on GitHub (May 12, 2019):

Here is what I get on building. I've tried everything mentioned above, but couldn't find solution to it. Can anybody check it out and see what should be done?

@mehulmpt commented on GitHub (May 12, 2019): ![screen](https://user-images.githubusercontent.com/10388889/57584819-5c900100-74fd-11e9-93f4-e1d06811142b.jpg) Here is what I get on building. I've tried everything mentioned above, but couldn't find solution to it. Can anybody check it out and see what should be done?

claunia commented

2026-01-30 22:01:25 +00:00

@dantenull commented on GitHub (May 12, 2019):

“wil/Common.h”: No such file or directory how is this error resolved???

@dantenull commented on GitHub (May 12, 2019): “wil/Common.h”: No such file or directory how is this error resolved???

claunia commented

2026-01-30 22:01:25 +00:00

@kjhajeh commented on GitHub (May 12, 2019):

Run git submodule update --init --recursive in Terminal folder
Run nuget restore OpenConsole.sln (This step can be skipped, then Visual Studio should warn you that there are packages to restore - then restore)

I found that these steps didn't work for me when I downloaded the ZIP file. It's better to just clone it using git clone, then use those steps. Hopefully this helps someone who might have run into the same problem that I did :D

@kjhajeh commented on GitHub (May 12, 2019): > Run git submodule update --init --recursive in Terminal folder > Run nuget restore OpenConsole.sln (This step can be skipped, then Visual Studio should warn you that there are packages to restore - then restore) I found that these steps didn't work for me when I downloaded the ZIP file. It's better to just clone it using git clone, then use those steps. Hopefully this helps someone who might have run into the same problem that I did :D

claunia commented

2026-01-30 22:01:25 +00:00

@kjhajeh commented on GitHub (May 12, 2019):

“wil/Common.h”: No such file or directory how is this error resolved???

You should try cloning the repository again via git clone (not downloading the ZIP file).
Then you run these two commands within the Terminal directory:

git submodule update --init --recursive

Then, change directory into dep/nuget

Then, run: > nuget restore OpenConsole.sln

TIP: you may also try >nuget restore (path to openconsole sln)
if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory.

Hope this helps!

@kjhajeh commented on GitHub (May 12, 2019): > “wil/Common.h”: No such file or directory how is this error resolved??? You should try cloning the repository again via git clone (not downloading the ZIP file). Then you run these two commands within the Terminal directory: >git submodule update --init --recursive Then, change directory into dep/nuget Then, run: > nuget restore OpenConsole.sln TIP: you may also try >nuget restore (path to openconsole sln) if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory. Hope this helps!

claunia commented

@fredrikaverpil commented on GitHub (May 12, 2019):

I jotted down some notes on how to run the terminal (from scratch) with VS2019 here.

The main juice is here (installs requirements from commandline):

"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installershell.exe" modify --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community" --passive --norestart --add Microsoft.VisualStudio.Workload.NativeDesktop --add Microsoft.VisualStudio.Workload.Universal --add Microsoft.VisualStudio.Component.Windows10SDK.18362 --add Microsoft.VisualStudio.ComponentGroup.UWP.Support --add Microsoft.Component.VC.Runtime.OSSupport --add Microsoft.VisualStudio.Component.VC.v141.x86.x64 --add Microsoft.VisualStudio.ComponentGroup.UWP.VC.v141 --add Microsoft.VisualStudio.Component.VC.v141.ATL --add Microsoft.VisualStudio.Component.VC.v141.MFC

The above command assumes the community edition. So if you are on another edition, double-check your paths. The workload/component IDs can be found here.

@fredrikaverpil commented on GitHub (May 12, 2019): I jotted down some notes on how to run the terminal (from scratch) with VS2019 [here](https://fredrikaverpil.github.io/2019/05/12/building-windows-terminal/). The main juice is here (installs requirements from commandline): ```bat "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installershell.exe" modify --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community" --passive --norestart --add Microsoft.VisualStudio.Workload.NativeDesktop --add Microsoft.VisualStudio.Workload.Universal --add Microsoft.VisualStudio.Component.Windows10SDK.18362 --add Microsoft.VisualStudio.ComponentGroup.UWP.Support --add Microsoft.Component.VC.Runtime.OSSupport --add Microsoft.VisualStudio.Component.VC.v141.x86.x64 --add Microsoft.VisualStudio.ComponentGroup.UWP.VC.v141 --add Microsoft.VisualStudio.Component.VC.v141.ATL --add Microsoft.VisualStudio.Component.VC.v141.MFC ``` The above command assumes the community edition. So if you are on another edition, double-check your paths. The workload/component IDs can be found [here](https://docs.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-build-tools?view=vs-2019).

claunia commented

@mehulmpt commented on GitHub (May 12, 2019):

Nevermind, I downgraded to VS2017 and it works like a charm now

@mehulmpt commented on GitHub (May 12, 2019): Nevermind, I downgraded to VS2017 and it works like a charm now

claunia commented

@snooopcatt commented on GitHub (May 12, 2019):

“wil/Common.h”: No such file or directory how is this error resolved???

I had similar issues because my file system was case-senstive. Converted it to non-sensitive and it went well

@snooopcatt commented on GitHub (May 12, 2019): > “wil/Common.h”: No such file or directory how is this error resolved??? I had similar issues because my file system was case-senstive. Converted it to non-sensitive and it went well

claunia commented

2026-01-30 22:01:27 +00:00

@christian-korneck commented on GitHub (May 12, 2019):

and the filesystem needs to be NTFS (building the sources from an exFat volume didn't work for me)

@christian-korneck commented on GitHub (May 12, 2019): and the filesystem needs to be NTFS (building the sources from an exFat volume didn't work for me)

claunia commented

@snooopcatt commented on GitHub (May 12, 2019):

Here is a solution which I used to disable that recursively: https://stackoverflow.com/questions/51591091/apply-setcasesensitiveinfo-recursively-to-all-folders-and-subfolders

@snooopcatt commented on GitHub (May 12, 2019): Here is a solution which I used to disable that recursively: https://stackoverflow.com/questions/51591091/apply-setcasesensitiveinfo-recursively-to-all-folders-and-subfolders

claunia commented

2026-01-30 22:01:27 +00:00

@CaptainMorgans commented on GitHub (May 12, 2019):

“wil/Common.h”: No such file or directory how is this error resolved???

You should try cloning the repository again via git clone (not downloading the ZIP file).
Then you run these two commands within the Terminal directory:

git submodule update --init --recursive

Then, change directory into dep/nuget

Then, run: > nuget restore OpenConsole.sln

TIP: you may also try >nuget restore (path to openconsole sln)
if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory.

Hope this helps!

Agreed, cloning the Git repository and then running the steps appears to have solved the “wil/Common.h”: No such file or directory once the command >> git submodule update --init --recursive has been run.

I used these steps: from @christian-korneck post above.

git clone https://github.com/microsoft/Terminal.git
cd Terminal
git submodule update --init --recursive
nuget restore OpenConsole.sln

I still get other errors when trying to build / deploy . I am now going to try downgrading to VS2017 and try the build.

@CaptainMorgans commented on GitHub (May 12, 2019): > > “wil/Common.h”: No such file or directory how is this error resolved??? > > You should try cloning the repository again via git clone (not downloading the ZIP file). > Then you run these two commands within the Terminal directory: > > > git submodule update --init --recursive > > Then, change directory into dep/nuget > > Then, run: > nuget restore OpenConsole.sln > > TIP: you may also try >nuget restore (path to openconsole sln) > if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory. > > Hope this helps! Agreed, cloning the Git repository and then running the steps appears to have solved the “wil/Common.h”: No such file or directory once the command >> git submodule update --init --recursive has been run. I used these steps: from @christian-korneck post above. git clone https://github.com/microsoft/Terminal.git cd Terminal git submodule update --init --recursive nuget restore OpenConsole.sln I still get other errors when trying to build / deploy . I am now going to try downgrading to VS2017 and try the build.

claunia commented

2026-01-30 22:01:27 +00:00

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

One small hint for these who manage to build it (I managed only with VS2017).

Once deployed, in official doc says (...and also in one of the comments above) that will appear under: Windows Terminal (Preview) ...so if you search for this you won't find anything.

On my machine after I deployed it it's showing as: Windows Terminal (Dev Build)

Cheers

@vsavic commented on GitHub (May 13, 2019): One small hint for these who manage to build it (I managed only with VS2017). Once deployed, in official doc says (...and also in one of the comments above) that will appear under: `Windows Terminal (Preview)` ...so if you search for this you won't find anything. On my machine after I deployed it it's showing as: `Windows Terminal (Dev Build)` Cheers

claunia commented

2026-01-30 22:01:28 +00:00

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

I confirm that I also only managed to get it built with VS2017.

Can't wait to play with the code a bit and see what cool things we can come up with.

@CaptainMorgans commented on GitHub (May 13, 2019): I confirm that I also only managed to get it built with VS2017. Can't wait to play with the code a bit and see what cool things we can come up with. ![image](https://user-images.githubusercontent.com/3514724/57597035-d8199e80-754d-11e9-98df-c11a2b5cb23f.png)

claunia commented

2026-01-30 22:01:28 +00:00

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

nice

@Meowv commented on GitHub (May 13, 2019): ![1](https://user-images.githubusercontent.com/13010050/57598941-b5a47700-7587-11e9-8a48-16dbe5433ba3.png) **nice**

claunia commented

2026-01-30 22:01:28 +00:00

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

Would it be possible to have a tab for running pwsh.exe as administrator?
How would such a configuration look like?

@hasselrot commented on GitHub (May 13, 2019): Would it be possible to have a tab for running pwsh.exe as administrator? How would such a configuration look like?

claunia commented

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

Would it be possible to have a tab for running pwsh.exe as administrator?
How would such a configuration look like?

Not for now, see #691

@mKay00 commented on GitHub (May 13, 2019): > Would it be possible to have a tab for running pwsh.exe as administrator? > How would such a configuration look like? Not for now, see #691

claunia commented

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

FWIW, I was having errors because I didn't have ATL support. This StackOverflow answer helped me out.

@HarryTheWulf commented on GitHub (May 13, 2019): FWIW, I was having errors because I didn't have ATL support. This [StackOverflow](https://stackoverflow.com/a/46304843/3578036) answer helped me out.

claunia commented

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

“wil/Common.h”: No such file or directory how is this error resolved???

You should try cloning the repository again via git clone (not downloading the ZIP file).
Then you run these two commands within the Terminal directory:

git submodule update --init --recursive

Then, change directory into dep/nuget

Then, run: > nuget restore OpenConsole.sln

TIP: you may also try >nuget restore (path to openconsole sln)
if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory.

Hope this helps!

Thank you very much! I made it.But there are other problems.

@dantenull commented on GitHub (May 13, 2019): > > “wil/Common.h”: No such file or directory how is this error resolved??? > > You should try cloning the repository again via git clone (not downloading the ZIP file). > Then you run these two commands within the Terminal directory: > > > git submodule update --init --recursive > > Then, change directory into dep/nuget > > Then, run: > nuget restore OpenConsole.sln > > TIP: you may also try >nuget restore (path to openconsole sln) > if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory. > > Hope this helps! Thank you very much! I made it.But there are other problems. ![屏幕快照 2019-05-14 上午1 23 16](https://user-images.githubusercontent.com/29767985/57641829-8c680300-75e8-11e9-90e1-4f75675e4a73.png)

claunia commented

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

“wil/Common.h”: No such file or directory how is this error resolved???

You should try cloning the repository again via git clone (not downloading the ZIP file).
Then you run these two commands within the Terminal directory:

git submodule update --init --recursive

Then, change directory into dep/nuget
Then, run: > nuget restore OpenConsole.sln
TIP: you may also try >nuget restore (path to openconsole sln)
if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory.
Hope this helps!

Agreed, cloning the Git repository and then running the steps appears to have solved the “wil/Common.h”: No such file or directory once the command >> git submodule update --init --recursive has been run.

I used these steps: from @christian-korneck post above.

git clone https://github.com/microsoft/Terminal.git
cd Terminal
git submodule update --init --recursive
nuget restore OpenConsole.sln

I still get other errors when trying to build / deploy . I am now going to try downgrading to VS2017 and try the build.

Thank you very much! I made it.I forget to cd Terminal..But I have another problem and I have no idea..

@dantenull commented on GitHub (May 13, 2019): > > > “wil/Common.h”: No such file or directory how is this error resolved??? > > > > > > You should try cloning the repository again via git clone (not downloading the ZIP file). > > Then you run these two commands within the Terminal directory: > > > git submodule update --init --recursive > > > > > > Then, change directory into dep/nuget > > Then, run: > nuget restore OpenConsole.sln > > TIP: you may also try >nuget restore (path to openconsole sln) > > if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory. > > Hope this helps! > > Agreed, cloning the Git repository and then running the steps appears to have solved the “wil/Common.h”: No such file or directory once the command >> git submodule update --init --recursive has been run. > > I used these steps: from @christian-korneck post above. > > git clone https://github.com/microsoft/Terminal.git > cd Terminal > git submodule update --init --recursive > nuget restore OpenConsole.sln > > I still get other errors when trying to build / deploy . I am now going to try downgrading to VS2017 and try the build. Thank you very much! I made it.I forget to cd Terminal..But I have another problem and I have no idea.. ![屏幕快照 2019-05-14 上午1 23 16](https://user-images.githubusercontent.com/29767985/57642299-8cb4ce00-75e9-11e9-9f15-da78b83ca480.png)

claunia commented

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

This is really fun. The green glow is awesome.

Can't wait to really dive into the code and get some things working.

Next order of business is to change the tab labels to the profile name.

@CaptainMorgans commented on GitHub (May 13, 2019): This is really fun. The green glow is awesome. Can't wait to really dive into the code and get some things working. Next order of business is to change the tab labels to the profile name. ![image](https://user-images.githubusercontent.com/3514724/57650019-0c32a500-75ca-11e9-88d6-031407a78952.png)

claunia commented

@schuettecarsten commented on GitHub (May 14, 2019):

For me, building with VS2019 fails with:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(261,5):
error MSB3774: SDK "Microsoft.VCLibs.Desktop, Version=14.0" konnte nicht gefunden werden.
[d:\Projekte\Terminal\pkg\appx\OpenConsolePackage.wapproj]

@schuettecarsten commented on GitHub (May 14, 2019): For me, building with VS2019 fails with: ``` C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(261,5): error MSB3774: SDK "Microsoft.VCLibs.Desktop, Version=14.0" konnte nicht gefunden werden. [d:\Projekte\Terminal\pkg\appx\OpenConsolePackage.wapproj]

claunia commented

@hasselrot commented on GitHub (May 14, 2019):

@CaptainMorgans @Meowv I seem to have missed something, how did you get the icons working?

@hasselrot commented on GitHub (May 14, 2019): @CaptainMorgans @Meowv I seem to have missed something, how did you get the icons working?

claunia commented

2026-01-30 22:01:31 +00:00

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

@hasselrot You have to copy image files into %LOCALAPPDATA%\packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState
and use them in the profile.json

@mKay00 commented on GitHub (May 14, 2019): @hasselrot You have to copy image files into %LOCALAPPDATA%\packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState and use them in the profile.json

claunia commented

@hasselrot commented on GitHub (May 14, 2019):

@mKay00 Excellent!
What is the key used in profile.json?

@hasselrot commented on GitHub (May 14, 2019): @mKay00 Excellent! What is the key used in profile.json?

claunia commented

2026-01-30 22:01:31 +00:00

@drekryan commented on GitHub (May 14, 2019):

“wil/Common.h”: No such file or directory how is this error resolved???

You should try cloning the repository again via git clone (not downloading the ZIP file).
Then you run these two commands within the Terminal directory:

git submodule update --init --recursive

Then, change directory into dep/nuget
Then, run: > nuget restore OpenConsole.sln
TIP: you may also try >nuget restore (path to openconsole sln)
if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory.
Hope this helps!

Agreed, cloning the Git repository and then running the steps appears to have solved the “wil/Common.h”: No such file or directory once the command >> git submodule update --init --recursive has been run.
I used these steps: from @christian-korneck post above.
git clone https://github.com/microsoft/Terminal.git
cd Terminal
git submodule update --init --recursive
nuget restore OpenConsole.sln
I still get other errors when trying to build / deploy . I am now going to try downgrading to VS2017 and try the build.

Thank you very much! I made it.I forget to cd Terminal..But I have another problem and I have no idea..

Hey I ran into this issue as well and resolved it by deleting any saved settings and allowing the app to regenerate them.

I went to the following location

%LOCALAPPDATA%\packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState
may also be %LOCALAPPDATA%\packages\Microsoft.WindowsDevTerminal_8wekyb3d8bbwe\RoamingState

and deleted any profiles.json file located there and relaunched the app.

@drekryan commented on GitHub (May 14, 2019): > > > > “wil/Common.h”: No such file or directory how is this error resolved??? > > > > > > > > > You should try cloning the repository again via git clone (not downloading the ZIP file). > > > Then you run these two commands within the Terminal directory: > > > > git submodule update --init --recursive > > > > > > > > > Then, change directory into dep/nuget > > > Then, run: > nuget restore OpenConsole.sln > > > TIP: you may also try >nuget restore (path to openconsole sln) > > > if nuget isn't in your PATH (which it probably isn't). Just remember to be in the nuget directory. > > > Hope this helps! > > > > > > Agreed, cloning the Git repository and then running the steps appears to have solved the “wil/Common.h”: No such file or directory once the command >> git submodule update --init --recursive has been run. > > I used these steps: from @christian-korneck post above. > > git clone https://github.com/microsoft/Terminal.git > > cd Terminal > > git submodule update --init --recursive > > nuget restore OpenConsole.sln > > I still get other errors when trying to build / deploy . I am now going to try downgrading to VS2017 and try the build. > > Thank you very much! I made it.I forget to cd Terminal..But I have another problem and I have no idea.. > ![屏幕快照 2019-05-14 上午1 23 16](https://user-images.githubusercontent.com/29767985/57642299-8cb4ce00-75e9-11e9-9f15-da78b83ca480.png) Hey I ran into this issue as well and resolved it by deleting any saved settings and allowing the app to regenerate them. I went to the following location %LOCALAPPDATA%\packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState may also be %LOCALAPPDATA%\packages\Microsoft.WindowsDevTerminal_8wekyb3d8bbwe\RoamingState and deleted any profiles.json file located there and relaunched the app.

claunia commented

2026-01-30 22:01:31 +00:00

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

@hasselrot "icon"
See the blog post of Scott Hanselman for a reference: https://www.hanselman.com/blog/ANewConsoleForWindowsItsTheOpenSourceWindowsTerminal.aspx

@mKay00 commented on GitHub (May 14, 2019): @hasselrot "icon" See the blog post of Scott Hanselman for a reference: https://www.hanselman.com/blog/ANewConsoleForWindowsItsTheOpenSourceWindowsTerminal.aspx

claunia commented

2026-01-30 22:01:32 +00:00

@GeekRicardo commented on GitHub (May 14, 2019):

当我使用Git bash时，我被告知bash：nuget：command not found
如何解决它？

You should

When I used Git bash，I was told bash：nuget：command not found
How to solve it？

You should use it in cmd

@GeekRicardo commented on GitHub (May 14, 2019): > 当我使用Git bash时，我被告知`bash：nuget：command not found` > 如何解决它？ You should > When I used Git bash，I was told `bash：nuget：command not found` > How to solve it？ You should use it in `cmd`

claunia commented

2026-01-30 22:01:32 +00:00

@xpwn3rx commented on GitHub (May 14, 2019):

@christian-korneck Thank you for the steps. All worked up until the Deploy step.

========== Build: 21 succeeded, 4 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========

Errors below

Severity Code Description Project File Line Suppression State
Error C1007 unrecognized flag '-Yu' in 'p2' TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1

Error LNK1257 code generation failed TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1

Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Parameter 'chord' of Procedure 'SetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ] TerminalApp C:\Terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 62

Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.IKeyBindings [ RuntimeClass 'TerminalApp.AppKeyBindings' ] TerminalApp C:\Terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 59

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

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

Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7

Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7

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 had these same problems. I was able to get this to build using VS2017 but I had to manually add the UWP C++ framework. I followed the instructions above with VS2017 and it worked.

@xpwn3rx commented on GitHub (May 14, 2019): > @christian-korneck Thank you for the steps. All worked up until the Deploy step. > > ========== Build: 21 succeeded, 4 failed, 0 up-to-date, 0 skipped ========== > ========== Deploy: 0 succeeded, 0 failed, 0 skipped ========== > > # Errors below > Severity Code Description Project File Line Suppression State > Error C1007 unrecognized flag '-Yu' in 'p2' TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1 > > Error LNK1257 code generation failed TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1 > > Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Parameter 'chord' of Procedure 'SetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ] TerminalApp C:\Terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 62 > > Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.IKeyBindings [ RuntimeClass 'TerminalApp.AppKeyBindings' ] TerminalApp C:\Terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 59 > > Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\AppHost.h 7 > > Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\AppHost.h 7 > > Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7 > > Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\Terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7 > > 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 > > ![image](https://user-images.githubusercontent.com/3514724/57584952-a965de80-74e1-11e9-819b-35b5b3cfb0df.png) I had these same problems. I was able to get this to build using VS2017 but I had to manually add the UWP C++ framework. I followed the instructions above with VS2017 and it worked.

claunia commented

2026-01-30 22:01:32 +00:00

@miniksa commented on GitHub (May 14, 2019):

We expect a lot of this to get fixed by #565. Otherwise, the README has been updated a lot in the past few days with additional information. And there have been a lot of config odds and ends merged into master that have lit up functionality in VS2019 like automatically installing the dependent packages.

@miniksa commented on GitHub (May 14, 2019): We expect a lot of this to get fixed by #565. Otherwise, the README has been updated a lot in the past few days with additional information. And there have been a lot of config odds and ends merged into master that have lit up functionality in VS2019 like automatically installing the dependent packages.

claunia commented

2026-01-30 22:01:33 +00:00

@a1850524995 commented on GitHub (May 15, 2019):

我可以使用VS 2019构建它吗？

我恐怕你不能，我已经失败了23与VS2019建立......

Can I build it with VS 2019?

I'm afraid you can't, I have got 23 FAILED to build with VS2019...

I have been built with vs2019 sucessfully, in vs Installer,choose all v141 tools

@a1850524995 commented on GitHub (May 15, 2019): > > 我可以使用VS 2019构建它吗？ > > 我恐怕你不能，我已经失败了23与VS2019建立...... > > Can I build it with VS 2019? > > I'm afraid you can't, I have got 23 FAILED to build with VS2019... I have been built with vs2019 sucessfully, in vs Installer,choose all v141 tools

claunia commented

2026-01-30 22:01:33 +00:00

@csy19960309 commented on GitHub (May 15, 2019):

Can I build it with VS 2019?

Absolutely you can. If you update the tool sets and strictly follow the steps you can easily build the code successfully. I have no idea why someone failed

@csy19960309 commented on GitHub (May 15, 2019): > Can I build it with VS 2019? Absolutely you can. If you update the tool sets and strictly follow the steps you can easily build the code successfully. I have no idea why someone failed

claunia commented

2026-01-30 22:01:33 +00:00

@gottahavebling commented on GitHub (May 15, 2019):

I am trying to build using VS2017 and getting missing .h file error. How do I fix these?

@gottahavebling commented on GitHub (May 15, 2019): I am trying to build using VS2017 and getting missing .h file error. How do I fix these? ![Capture](https://user-images.githubusercontent.com/1761101/57775896-1d73d280-76ec-11e9-9fda-5e192ffd7a7e.PNG)

claunia commented

2026-01-30 22:01:34 +00:00

@gaohongkui commented on GitHub (May 15, 2019):

I want to know that I am now Windows10 1809 Build 17763.503, but I have not received the update file of Windows10 1903, how should I update it?I have successfully generated the terminal project, but there is no SDK for Win10 1903, so I cannot deploy and run the project.Who can help me?

@gaohongkui commented on GitHub (May 15, 2019): I want to know that I am now `Windows10 1809 Build 17763.503`, but I have not received the update file of `Windows10 1903`, how should I update it?I have successfully generated the terminal project, but there is no `SDK` for `Win10 1903`, so I cannot deploy and run the project.Who can help me? ![MB7 QIQK819WQ2H%V4HP4WO](https://user-images.githubusercontent.com/38203359/57794072-62901700-7775-11e9-8665-1d8c066be7f7.png)

claunia commented

2026-01-30 22:01:34 +00:00

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

You have to be a Windows Insider. I think Release preview ring is enough. Go to Windows Settings, Update and Security and there is Windows Insider Program.

@mKay00 commented on GitHub (May 15, 2019): You have to be a Windows Insider. I think Release preview ring is enough. Go to Windows Settings, Update and Security and there is Windows Insider Program.

claunia commented

2026-01-30 22:01:34 +00:00

@gaohongkui commented on GitHub (May 15, 2019):

You have to be a Windows Insider. I think Release preview ring is enough. Go to Windows Settings, Update and Security and there is Windows Insider Program.

That is failed! It is sad.

@gaohongkui commented on GitHub (May 15, 2019): > You have to be a Windows Insider. I think Release preview ring is enough. Go to Windows Settings, Update and Security and there is Windows Insider Program. That is failed! It is sad. ![image](https://user-images.githubusercontent.com/38203359/57795351-4f327b00-7778-11e9-8853-e26aa4f474e7.png)

claunia commented

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

I assume you have games installed on your PC? There are issues with anti-cheat software and thus it won't install, if you have anti cheat software installed. This workaround worked for me to install 1903, but I can't guarantee that you'll be able to play (all) online games after installing. I just moved the folder and moved it back after the update.
https://twitter.com/zman982/status/1122049491140599808

@mKay00 commented on GitHub (May 15, 2019): I assume you have games installed on your PC? There are issues with anti-cheat software and thus it won't install, if you have anti cheat software installed. This workaround worked for me to install 1903, but I can't guarantee that you'll be able to play (all) online games after installing. I just moved the folder and moved it back after the update. https://twitter.com/zman982/status/1122049491140599808

claunia commented

@gaohongkui commented on GitHub (May 15, 2019):

Yes,it works. Thanks a lot.

@gaohongkui commented on GitHub (May 15, 2019): Yes,it works. Thanks a lot.

claunia commented

@j-ae commented on GitHub (May 16, 2019):

I am trying to build using VS2019 and getting the namespace error.

https://docs.microsoft.com/en-us/uwp/api/microsoft.ui.xaml.controls?view=winui-2.1#classes
From above the link, I tried to find the TabViewItem. There is no TabViewItem class.

Edit:
I also checked "https://github.com/Microsoft/microsoft-ui-xaml".
I installed "Microsoft.UI.Xaml.2.1.190405004.2".
Maybe, it was on the old version(Microsoft.UI.Xaml.2.1.190405001-prerelease) but removed now?

@j-ae commented on GitHub (May 16, 2019): ![image](https://user-images.githubusercontent.com/44935193/57817918-8a13bf00-7736-11e9-9e59-2c02e8fab274.png) I am trying to build using VS2019 and getting the namespace error. https://docs.microsoft.com/en-us/uwp/api/microsoft.ui.xaml.controls?view=winui-2.1#classes From above the link, I tried to find the TabViewItem. There is no TabViewItem class. Edit: I also checked "https://github.com/Microsoft/microsoft-ui-xaml". I installed "Microsoft.UI.Xaml.2.1.190405004.2". Maybe, it was on the old version(Microsoft.UI.Xaml.2.1.190405001-prerelease) but removed now?

claunia commented

@l1005268416 commented on GitHub (May 16, 2019):

需要加入Windows预览体验计划，才能收到1903（insider）的推送。否则需要等到正式发布。

1005268416@qq.com

From: GodK
Date: 2019-05-16 00:55
To: microsoft/terminal
CC: l1005268416; Comment
Subject: Re: [microsoft/terminal] Guide for build and installation (#489)
我想知道我现在是Windows10 1809 Build 17763.503，但是我没有收到Windows10 1903的更新文件，我应该怎么更新呢。我已经成功生成了terminal项目，但是因为没有Win10 1903的SDK导致没有办法部署运行该项目？谁能帮帮我？
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@l1005268416 commented on GitHub (May 16, 2019): 需要加入Windows预览体验计划，才能收到1903（insider）的推送。否则需要等到正式发布。 1005268416@qq.com From: GodK Date: 2019-05-16 00:55 To: microsoft/terminal CC: l1005268416; Comment Subject: Re: [microsoft/terminal] Guide for build and installation (#489) 我想知道我现在是Windows10 1809 Build 17763.503，但是我没有收到Windows10 1903的更新文件，我应该怎么更新呢。我已经成功生成了terminal项目，但是因为没有Win10 1903的SDK导致没有办法部署运行该项目？谁能帮帮我？ — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

claunia commented

@SwimmingTiger commented on GitHub (May 16, 2019):

@schuettecarsten I have the same issue before in both VS2017 and VS2019, and I solved it via repair my VS2017 (see https://github.com/microsoft/terminal/issues/837 for detail).
Repair VS2019 may also works.

For me, building with VS2019 fails with:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(261,5):
error MSB3774: SDK "Microsoft.VCLibs.Desktop, Version=14.0" konnte nicht gefunden werden.
[d:\Projekte\Terminal\pkg\appx\OpenConsolePackage.wapproj]

@SwimmingTiger commented on GitHub (May 16, 2019): @schuettecarsten I have the same issue before in both VS2017 and VS2019, and I solved it via repair my VS2017 (see https://github.com/microsoft/terminal/issues/837 for detail). Repair VS2019 may also works. > > > For me, building with VS2019 fails with: > > ``` > C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets(261,5): > error MSB3774: SDK "Microsoft.VCLibs.Desktop, Version=14.0" konnte nicht gefunden werden. > [d:\Projekte\Terminal\pkg\appx\OpenConsolePackage.wapproj] > ```

claunia commented

@AndrewGong2016 commented on GitHub (May 17, 2019):

Information you may needed (for chinese)
1 window 10 1903版本成功安装，done
2 VS 2019 部署该项目，done
Oh yeah
first time use the great VS

@AndrewGong2016 commented on GitHub (May 17, 2019): Information you may needed (for chinese) 1 window 10 1903版本成功安装，done 2 VS 2019 部署该项目，done Oh yeah first time use the great VS

claunia commented

@AndrewGong2016 commented on GitHub (May 17, 2019):

This is really fun. The green glow is awesome.

Can't wait to really dive into the code and get some things working.

Next order of business is to change the tab labels to the profile name.

I have deploy start the same window, but how can I add a ubuntu cmd ? what can I do ?

@AndrewGong2016 commented on GitHub (May 17, 2019): > This is really fun. The green glow is awesome. > > Can't wait to really dive into the code and get some things working. > > Next order of business is to change the tab labels to the profile name. > > ![image](https://user-images.githubusercontent.com/3514724/57650019-0c32a500-75ca-11e9-88d6-031407a78952.png) I have deploy start the same window, but how can I add a ubuntu cmd ? what can I do ?

claunia commented

@gottahavebling commented on GitHub (May 17, 2019):

Was finally able to build and deploy the solution. I see a new shortcut named "Windows Terminal (Dev Build" but upon clicking, powershell window opens up and dont see any plus sign on the toolbar. What am I doing wrong?

@gottahavebling commented on GitHub (May 17, 2019): Was finally able to build and deploy the solution. I see a new shortcut named "Windows Terminal (Dev Build" but upon clicking, powershell window opens up and dont see any plus sign on the toolbar. What am I doing wrong?

claunia commented

@drekryan commented on GitHub (May 17, 2019):

Tab bar is hidden by default. Press Ctrl-T to create a new tab or go into settings in the drop down next to the plus button and change “Always show tab bar” to true.

@drekryan commented on GitHub (May 17, 2019): Tab bar is hidden by default. Press Ctrl-T to create a new tab or go into settings in the drop down next to the plus button and change “Always show tab bar” to true.

claunia commented

@gottahavebling commented on GitHub (May 17, 2019):

Tab bar is hidden by default. Press Ctrl-T to create a new tab or go into settings in the drop down next to the plus button and change “Always so tab bar” to true.

Ah. That did it. Thank you!

@gottahavebling commented on GitHub (May 17, 2019): > Tab bar is hidden by default. Press Ctrl-T to create a new tab or go into settings in the drop down next to the plus button and change “Always so tab bar” to true. Ah. That did it. Thank you!

claunia commented

@MichaelE919 commented on GitHub (May 18, 2019):

There are several header files which have the line "#include <Windows.h>", sometimes with a "windows.h." This file doesn't exist in the repo. Did Windows.h get replaced with another file?

@MichaelE919 commented on GitHub (May 18, 2019): There are several header files which have the line "#include <Windows.h>", sometimes with a "windows.h." This file doesn't exist in the repo. Did Windows.h get replaced with another file?

claunia commented

@DHowett-MSFT commented on GitHub (May 18, 2019):

Huh? windows.h is part of the Windows SDK. It has been for about a hundred years.

@DHowett-MSFT commented on GitHub (May 18, 2019): Huh? `windows.h` is part of the Windows SDK. It has been for about a hundred years.

claunia commented

2026-01-30 22:01:38 +00:00

@dantenull commented on GitHub (May 18, 2019):

Hey I ran into this issue as well and resolved it by deleting any saved settings and allowing the app to regenerate them.

I went to the following location

%LOCALAPPDATA%\packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState
may also be %LOCALAPPDATA%\packages\Microsoft.WindowsDevTerminal_8wekyb3d8bbwe\RoamingState

and deleted any profiles.json file located there and relaunched the app.

@drekryan Thank you.I tried and didn't make the mistake last time.But it didn't run correctly.I can't use it.

@dantenull commented on GitHub (May 18, 2019): > > Hey I ran into this issue as well and resolved it by deleting any saved settings and allowing the app to regenerate them. > > I went to the following location > > %LOCALAPPDATA%\packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState > may also be %LOCALAPPDATA%\packages\Microsoft.WindowsDevTerminal_8wekyb3d8bbwe\RoamingState > > and deleted any profiles.json file located there and relaunched the app. @drekryan Thank you.I tried and didn't make the mistake last time.But it didn't run correctly.I can't use it.

claunia commented

@iamdarknight commented on GitHub (May 18, 2019):

VS 2019 i used this successfully:

@iamdarknight commented on GitHub (May 18, 2019): VS 2019 i used this successfully: - https://github.com/microsoft/terminal/issues/489#issuecomment-490151997 - https://github.com/microsoft/terminal/issues/489#issuecomment-491489422 - https://github.com/microsoft/terminal/issues/489#issuecomment-491603111 - https://www.hanselman.com/blog/ANewConsoleForWindowsItsTheOpenSourceWindowsTerminal.aspx

claunia commented

2026-01-30 22:01:38 +00:00

@jduartedj commented on GitHub (May 20, 2019):

I was redirected here because of atlbase files missing but since the other thread was closed I wasn't able to see the resolution directly.
FYI: to newcomers with atlbase issue you need to install the ATL v142 (for me at this moment). Quoting it:

In Visual Studio, you can go to Tools->Get Tools and Features, which will open the Visual Studio Installer. From there you can click the Modify button for your Visual Studio version, then go to the Individual Components tab at the top. The C++ ATL components are in the section titled "SDKs, libraries, and frameworks" which is the last section in my list at least.

Fair warning, I had to install the V141 versions to get the atlbase error to go away, not the V142 versions in the picture.

@jduartedj commented on GitHub (May 20, 2019): I was redirected here because of atlbase files missing but since the other thread was closed I wasn't able to see the resolution directly. FYI: to newcomers with atlbase issue you need to install the ATL v142 (for me at this moment). [Quoting it](https://github.com/microsoft/terminal/issues/483#issuecomment-490022957): > In Visual Studio, you can go to Tools->Get Tools and Features, which will open the Visual Studio Installer. From there you can click the Modify button for your Visual Studio version, then go to the Individual Components tab at the top. The C++ ATL components are in the section titled "SDKs, libraries, and frameworks" which is the last section in my list at least. > > Fair warning, I had to install the V141 versions to get the atlbase error to go away, not the V142 versions in the picture.

claunia commented

2026-01-30 22:01:38 +00:00

@zugazagoitia commented on GitHub (May 20, 2019):

I'm getting the following error:

Details

"C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\OpenConsole.sln" (default target) (1) ->
"C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\src\host\ft_uia\Host.Tests.UIA.csproj.metaproj" (default targe
t) (34) ->
"C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\src\host\ft_uia\Host.Tests.UIA.csproj" (default target) (37) -

(PostBuildEvent target) ->
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.ta
rgets(5179,5): error MSB3073: The command "copy C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\dep\WinAppDriv
er* C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\bin\x64\Release\" exited with code 1. [C:\Users\Alberto
Zugazagoitia\Documents\GitHub\Terminal\src\host\ft_uia\Host.Tests.UIA.csproj]

It may have to do with the path double slashes, how can i get this solved?

@zugazagoitia commented on GitHub (May 20, 2019): I'm getting the following error: <details> <summary>Details</summary> "C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\OpenConsole.sln" (default target) (1) -> "C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\src\host\ft_uia\Host.Tests.UIA.csproj.metaproj" (default targe t) (34) -> "C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\src\host\ft_uia\Host.Tests.UIA.csproj" (default target) (37) - > (PostBuildEvent target) -> C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.ta rgets(5179,5): error MSB3073: The command "copy C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\\dep\WinAppDriv er\* C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\\bin\x64\Release\\" exited with code 1. [C:\Users\Alberto Zugazagoitia\Documents\GitHub\Terminal\src\host\ft_uia\Host.Tests.UIA.csproj] </details> It may have to do with the path double slashes, how can i get this solved?

claunia commented

2026-01-30 22:01:39 +00:00

@PatrykZajac commented on GitHub (May 20, 2019):

I try to solve my problem, but I don't know what I make incorrect. I have error like:
Severity Code Description Project File Line Suppression State Error C1007 unrecognized flag '-Yu' in 'p2' TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1 Error LNK1257 code generation failed TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1 Error C1007 unrecognized flag '-Yu' in 'p2' TerminalApp C:\Terminal\src\cascadia\TerminalApp\LINK 1 Error LNK1257 code generation failed TerminalApp C:\Terminal\src\cascadia\TerminalApp\LINK 1
Can anyone tell me what I make wrong?

@PatrykZajac commented on GitHub (May 20, 2019): I try to solve my problem, but I don't know what I make incorrect. I have error like: `Severity Code Description Project File Line Suppression State Error C1007 unrecognized flag '-Yu' in 'p2' TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1 Error LNK1257 code generation failed TerminalControl C:\Terminal\src\cascadia\TerminalControl\LINK 1 Error C1007 unrecognized flag '-Yu' in 'p2' TerminalApp C:\Terminal\src\cascadia\TerminalApp\LINK 1 Error LNK1257 code generation failed TerminalApp C:\Terminal\src\cascadia\TerminalApp\LINK 1 ` Can anyone tell me what I make wrong?

claunia commented

2026-01-30 22:01:39 +00:00

@drekryan commented on GitHub (May 20, 2019):

@PatrykZajac are you using the latest Windows 10 SDK (10.0.18362.0). Be sure it’s downloaded then retarget your solution to use this version of the SDK

@drekryan commented on GitHub (May 20, 2019): @PatrykZajac are you using the latest Windows 10 SDK (10.0.18362.0). Be sure it’s downloaded then retarget your solution to use this version of the SDK

claunia commented

2026-01-30 22:01:39 +00:00

@PatrykZajac commented on GitHub (May 20, 2019):

@PatrykZajac are you using the latest Windows 10 SDK (10.0.18362.0). Be sure it’s downloaded then retarget your solution to use this version of the SDK

I upgraded windows to 1903 and now it's works. Thanks

@PatrykZajac commented on GitHub (May 20, 2019): > @PatrykZajac are you using the latest Windows 10 SDK (10.0.18362.0). Be sure it’s downloaded then retarget your solution to use this version of the SDK I upgraded windows to 1903 and now it's works. Thanks

claunia commented

2026-01-30 22:01:40 +00:00

@plop28 commented on GitHub (May 21, 2019):

This is really fun. The green glow is awesome.

Can't wait to really dive into the code and get some things working.

Next order of business is to change the tab labels to the profile name.

Nice, what theme or color did you used ?

@plop28 commented on GitHub (May 21, 2019): > This is really fun. The green glow is awesome. > > Can't wait to really dive into the code and get some things working. > > Next order of business is to change the tab labels to the profile name. > > ![image](https://user-images.githubusercontent.com/3514724/57650019-0c32a500-75ca-11e9-88d6-031407a78952.png) Nice, what theme or color did you used ?

claunia commented

2026-01-30 22:01:40 +00:00

@Spazattack4life commented on GitHub (May 21, 2019):

For all you having issues, I found this helpful. https://www.youtube.com/watch?v=4Rsr0NRHuBY

However, I can open the "Ubuntu Terminal" but nothing works, any clue on how to start troubleshooting this, kinda new and figured this would be a good way to start learning, guess I walked off a cliff, now im in over my head.

@Spazattack4life commented on GitHub (May 21, 2019): For all you having issues, I found this helpful. https://www.youtube.com/watch?v=4Rsr0NRHuBY However, I can open the "Ubuntu Terminal" but nothing works, any clue on how to start troubleshooting this, kinda new and figured this would be a good way to start learning, guess I walked off a cliff, now im in over my head.

claunia commented

2026-01-30 22:01:40 +00:00

@tensor-programming commented on GitHub (May 22, 2019):

Was able to build this thing easily enough with cmd/powershell but what about deployment? I really don't want to have to install VS and then the 11.6 gigs worth of tools that I already have just to make it run

@tensor-programming commented on GitHub (May 22, 2019): Was able to build this thing easily enough with cmd/powershell but what about deployment? I really don't want to have to install VS and then the 11.6 gigs worth of tools that I already have just to make it run

claunia commented

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

For all you having issues, I found this helpful. https://www.youtube.com/watch?v=4Rsr0NRHuBY

However, I can open the "Ubuntu Terminal" but nothing works, any clue on how to start troubleshooting this, kinda new and figured this would be a good way to start learning, guess I walked off a cliff, now im in over my head.

What do you mean with "but nothing works"? Be a bit more specific than that.

@tensor-programming As far as I know you need to use VS to deploy it. Or you wait for the release in the store, which is planned for June.

@mKay00 commented on GitHub (May 22, 2019): > For all you having issues, I found this helpful. https://www.youtube.com/watch?v=4Rsr0NRHuBY > > However, I can open the "Ubuntu Terminal" but nothing works, any clue on how to start troubleshooting this, kinda new and figured this would be a good way to start learning, guess I walked off a cliff, now im in over my head. What do you mean with "but nothing works"? Be a bit more specific than that. @tensor-programming As far as I know you need to use VS to deploy it. Or you wait for the release in the store, which is planned for June.

claunia commented

@derek-s commented on GitHub (May 22, 2019):

i successful deploy on my pc, thank you all

@derek-s commented on GitHub (May 22, 2019): i successful deploy on my pc, thank you all

claunia commented

@SakuraJensen commented on GitHub (May 23, 2019):

Anyone know how I can fix these errors when trying to compile?

Update: Apparently VS lied to me and its installed and running fine.

@SakuraJensen commented on GitHub (May 23, 2019): Anyone know how I can fix these errors when trying to compile? ![image](https://user-images.githubusercontent.com/33555092/58228166-c1b4d500-7cfb-11e9-8f3a-ccf394e6fa50.png) Update: Apparently VS lied to me and its installed and running fine.

claunia commented

2026-01-30 22:01:42 +00:00

@fredrikaverpil commented on GitHub (May 23, 2019):

With VS2019, here is how you can install all deps from the Powershell commandline (which will launch the installer UI):

& "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installershell.exe" `
    modify `
    --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community" `
    --passive --norestart `
    --add Microsoft.VisualStudio.Workload.NativeDesktop `
    --add Microsoft.VisualStudio.Workload.Universal `
    --add Microsoft.VisualStudio.Component.Windows10SDK.18362 `
    --add Microsoft.VisualStudio.ComponentGroup.UWP.Support `
    --add Microsoft.Component.VC.Runtime.OSSupport `
    --add Microsoft.VisualStudio.Component.VC.v141.x86.x64 `
    --add Microsoft.VisualStudio.ComponentGroup.UWP.VC.v141 `
    --add Microsoft.VisualStudio.Component.VC.v141.ATL `
    --add Microsoft.VisualStudio.Component.VC.v141.MFC

You may have to change the paths above depending on where your VS2019 is installed.

I jotted down my build/deploy notes on my blog: https://fredrikaverpil.github.io/2019/05/12/building-windows-terminal/

@fredrikaverpil commented on GitHub (May 23, 2019): With VS2019, here is how you can install all deps from the Powershell commandline (which will launch the installer UI): ```powershell & "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installershell.exe" ` modify ` --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community" ` --passive --norestart ` --add Microsoft.VisualStudio.Workload.NativeDesktop ` --add Microsoft.VisualStudio.Workload.Universal ` --add Microsoft.VisualStudio.Component.Windows10SDK.18362 ` --add Microsoft.VisualStudio.ComponentGroup.UWP.Support ` --add Microsoft.Component.VC.Runtime.OSSupport ` --add Microsoft.VisualStudio.Component.VC.v141.x86.x64 ` --add Microsoft.VisualStudio.ComponentGroup.UWP.VC.v141 ` --add Microsoft.VisualStudio.Component.VC.v141.ATL ` --add Microsoft.VisualStudio.Component.VC.v141.MFC ``` You may have to change the paths above depending on where your VS2019 is installed. I jotted down my build/deploy notes on my blog: https://fredrikaverpil.github.io/2019/05/12/building-windows-terminal/

claunia commented

@jackluo923 commented on GitHub (May 23, 2019):

After deployment, Windows Terminal (Dev Build) showed up instead of Windows Terminal (Preview). After opening Windows Terminal (Dev Build), powershell popped up rather than Windows Terminal. Any fix to this problem?

@jackluo923 commented on GitHub (May 23, 2019): After deployment, Windows Terminal (Dev Build) showed up instead of Windows Terminal (Preview). After opening Windows Terminal (Dev Build), powershell popped up rather than Windows Terminal. Any fix to this problem?

claunia commented

2026-01-30 22:01:42 +00:00

@xpwn3rx commented on GitHub (May 23, 2019):

I'm sorry, but if you read the instructions or the documentation you would know that is how it works. The tabs don't show up until you press CTRL+T or you force them on in the configuration json file.

@xpwn3rx commented on GitHub (May 23, 2019): I'm sorry, but if you read the instructions or the documentation you would know that is how it works. The tabs don't show up until you press CTRL+T or you force them on in the configuration json file.

claunia commented

2026-01-30 22:01:42 +00:00

@jackluo923 commented on GitHub (May 23, 2019):

Thanks for the clarification. I was expecting the GUI screenshot from few post up, but the resulting GUI was different. I guess the default GUI for the windows terminal looks exactly like powershell (which after thinking about it should be the correct behavior).

FYI: To make the title bar disappear, you'll need to take a look at this feature request:
https://github.com/microsoft/Terminal/issues/433

@jackluo923 commented on GitHub (May 23, 2019): Thanks for the clarification. I was expecting the GUI screenshot from few post up, but the resulting GUI was different. I guess the default GUI for the windows terminal looks exactly like powershell (which after thinking about it should be the correct behavior). ![Capture](https://user-images.githubusercontent.com/8986643/58288174-d1c2c800-7d80-11e9-86b1-351abd71e73d.PNG) ![image](https://user-images.githubusercontent.com/8986643/58288568-fec3aa80-7d81-11e9-8086-1b5d77a64b72.png) FYI: To make the title bar disappear, you'll need to take a look at this feature request: https://github.com/microsoft/Terminal/issues/433

claunia commented

2026-01-30 22:01:43 +00:00

@TheFern2 commented on GitHub (May 24, 2019):

Followed build steps, opened snl project, update to V142 (Do not skip step 3 if you are having issues)

If I skip step3:
Opening with Visual Studio 2019, installed missing components, and it didn't want to restore nugets even when settings were correct and even when I manually restore nugets on cmd prompt they were already up to date, build failed every time. So do not skip step 3 if you are having issues with nuget restore in visual studio is a known bug.

@TheFern2 commented on GitHub (May 24, 2019): Followed build steps, opened snl project, update to V142 **(Do not skip step 3 if you are having issues)** If I skip step3: Opening with Visual Studio 2019, installed missing components, and it didn't want to restore nugets even when settings were correct and even when I manually restore nugets on cmd prompt they were already up to date, build failed every time. So do not skip step 3 if you are having issues with nuget restore in visual studio is a known bug.

claunia commented

2026-01-30 22:01:43 +00:00

@TheFern2 commented on GitHub (May 24, 2019):

@Code7thDay Yes you can, I just did. Don't skip step 3. VS2019 has a bug with nuget restore.

@TheFern2 commented on GitHub (May 24, 2019): @Code7thDay Yes you can, I just did. Don't skip step 3. VS2019 has a bug with nuget restore.

claunia commented

2026-01-30 22:01:43 +00:00

@Morgy93 commented on GitHub (May 25, 2019):

I read in another issue, that you want build errors to be discussed in this issue only, but mine are not listed here:

Severity	Code	Description	Project	File	Line	Suppression State
Error	MIDL2011	[msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Procedure 'GetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ]	TerminalApp	C:\dev\terminal\src\cascadia\TerminalApp\AppKeyBindings.idl	70	
Error	C1007	unrecognized flag '-Yu' in 'p2'	TerminalConnection	C:\dev\terminal\src\cascadia\TerminalConnection\LINK	1	
Error	LNK1257	code generation failed	TerminalConnection	C:\dev\terminal\src\cascadia\TerminalConnection\LINK	1	
Error	C1007	unrecognized flag '-Yu' in 'p2'	TerminalControl	C:\dev\terminal\src\cascadia\TerminalControl\LINK	1	
Error	LNK1257	code generation failed	TerminalControl	C:\dev\terminal\src\cascadia\TerminalControl\LINK	1	
Error	MIDL2011	[msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Parameter 'chord' of Procedure 'SetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ]	TerminalApp	C:\dev\terminal\src\cascadia\TerminalApp\AppKeyBindings.idl	69	
Error	MIDL9008	internal compiler problem - See documentation for suggestions on how to find a workaround.	TerminalApp	C:\dev\terminal\src\cascadia\TerminalApp\midl	1	
Error	C1083	 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory	WindowsTerminal	C:\dev\terminal\src\cascadia\WindowsTerminal\AppHost.h	7	
Error	C1083	 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory	WindowsTerminal	C:\dev\terminal\src\cascadia\WindowsTerminal\AppHost.h	7	
Error	C1083	 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory	WindowsTerminal	C:\dev\terminal\src\cascadia\WindowsTerminal\IslandWindow.h	7	
Error	C1083	 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory	WindowsTerminal	C:\dev\terminal\src\cascadia\WindowsTerminal\IslandWindow.h	7	
Warning		The project 'OpenConsolePackage.wapproj' has both an EntryPointExe property and one or more application references. The generated package will use the entry point specified in the EntryPointExe property.	OpenConsolePackage	C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets	413	
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

Win1903; VS2019

@Morgy93 commented on GitHub (May 25, 2019): I read in another issue, that you want build errors to be discussed in this issue only, but mine are not listed here: ``` Severity Code Description Project File Line Suppression State Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Procedure 'GetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ] TerminalApp C:\dev\terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 70 Error C1007 unrecognized flag '-Yu' in 'p2' TerminalConnection C:\dev\terminal\src\cascadia\TerminalConnection\LINK 1 Error LNK1257 code generation failed TerminalConnection C:\dev\terminal\src\cascadia\TerminalConnection\LINK 1 Error C1007 unrecognized flag '-Yu' in 'p2' TerminalControl C:\dev\terminal\src\cascadia\TerminalControl\LINK 1 Error LNK1257 code generation failed TerminalControl C:\dev\terminal\src\cascadia\TerminalControl\LINK 1 Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Parameter 'chord' of Procedure 'SetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ] TerminalApp C:\dev\terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 69 Error MIDL9008 internal compiler problem - See documentation for suggestions on how to find a workaround. TerminalApp C:\dev\terminal\src\cascadia\TerminalApp\midl 1 Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\dev\terminal\src\cascadia\WindowsTerminal\AppHost.h 7 Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\dev\terminal\src\cascadia\WindowsTerminal\AppHost.h 7 Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\dev\terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7 Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\dev\terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7 Warning The project 'OpenConsolePackage.wapproj' has both an EntryPointExe property and one or more application references. The generated package will use the entry point specified in the EntryPointExe property. OpenConsolePackage C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets 413 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 ``` ![image](https://user-images.githubusercontent.com/7961978/58365156-56683000-7ec0-11e9-9388-e4bb20cda734.png) Win1903; VS2019

claunia commented

2026-01-30 22:01:44 +00:00

@LKI commented on GitHub (May 25, 2019):

Thanks, these are very useful instructions.
It would be better to have these instructions updated in README.

@LKI commented on GitHub (May 25, 2019): Thanks, these are very useful instructions. It would be better to have these instructions updated in README.

claunia commented

2026-01-30 22:01:44 +00:00

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

@LKI feel free to change it and make a PR.

@mKay00 commented on GitHub (May 25, 2019): @LKI feel free to change it and make a PR.

claunia commented

@TheFern2 commented on GitHub (May 25, 2019):

I read in another issue, that you want build errors to be discussed in this issue only, but mine are not listed here:

Severity	Code	Description	Project	File	Line	Suppression State
Error	MIDL2011	[msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Procedure 'GetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ]	TerminalApp	C:\dev\terminal\src\cascadia\TerminalApp\AppKeyBindings.idl	70	
Error	C1007	unrecognized flag '-Yu' in 'p2'	TerminalConnection	C:\dev\terminal\src\cascadia\TerminalConnection\LINK	1	
Error	LNK1257	code generation failed	TerminalConnection	C:\dev\terminal\src\cascadia\TerminalConnection\LINK	1	
Error	C1007	unrecognized flag '-Yu' in 'p2'	TerminalControl	C:\dev\terminal\src\cascadia\TerminalControl\LINK	1	
Error	LNK1257	code generation failed	TerminalControl	C:\dev\terminal\src\cascadia\TerminalControl\LINK	1	
Error	MIDL2011	[msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Parameter 'chord' of Procedure 'SetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ]	TerminalApp	C:\dev\terminal\src\cascadia\TerminalApp\AppKeyBindings.idl	69	
Error	MIDL9008	internal compiler problem - See documentation for suggestions on how to find a workaround.	TerminalApp	C:\dev\terminal\src\cascadia\TerminalApp\midl	1	
Error	C1083	 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory	WindowsTerminal	C:\dev\terminal\src\cascadia\WindowsTerminal\AppHost.h	7	
Error	C1083	 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory	WindowsTerminal	C:\dev\terminal\src\cascadia\WindowsTerminal\AppHost.h	7	
Error	C1083	 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory	WindowsTerminal	C:\dev\terminal\src\cascadia\WindowsTerminal\IslandWindow.h	7	
Error	C1083	 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory	WindowsTerminal	C:\dev\terminal\src\cascadia\WindowsTerminal\IslandWindow.h	7	
Warning		The project 'OpenConsolePackage.wapproj' has both an EntryPointExe property and one or more application references. The generated package will use the entry point specified in the EntryPointExe property.	OpenConsolePackage	C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets	413	
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

Win1903; VS2019

@Morgy93 I was getting the exact errors before updating my windows version to 1903. Have you checked that?
On cmd prompt you'll see it at the top when launched, or just type ver to get your windows version.

@TheFern2 commented on GitHub (May 25, 2019): > I read in another issue, that you want build errors to be discussed in this issue only, but mine are not listed here: > > ``` > Severity Code Description Project File Line Suppression State > Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Procedure 'GetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ] TerminalApp C:\dev\terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 70 > Error C1007 unrecognized flag '-Yu' in 'p2' TerminalConnection C:\dev\terminal\src\cascadia\TerminalConnection\LINK 1 > Error LNK1257 code generation failed TerminalConnection C:\dev\terminal\src\cascadia\TerminalConnection\LINK 1 > Error C1007 unrecognized flag '-Yu' in 'p2' TerminalControl C:\dev\terminal\src\cascadia\TerminalControl\LINK 1 > Error LNK1257 code generation failed TerminalControl C:\dev\terminal\src\cascadia\TerminalControl\LINK 1 > Error MIDL2011 [msg]unresolved type declaration [context]: Microsoft.Terminal.Settings.KeyChord [ Parameter 'chord' of Procedure 'SetKeyBinding' ( RuntimeClass 'TerminalApp.AppKeyBindings' ) ] TerminalApp C:\dev\terminal\src\cascadia\TerminalApp\AppKeyBindings.idl 69 > Error MIDL9008 internal compiler problem - See documentation for suggestions on how to find a workaround. TerminalApp C:\dev\terminal\src\cascadia\TerminalApp\midl 1 > Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\dev\terminal\src\cascadia\WindowsTerminal\AppHost.h 7 > Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\dev\terminal\src\cascadia\WindowsTerminal\AppHost.h 7 > Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\dev\terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7 > Error C1083 Cannot open include file: 'winrt/TerminalApp.h': No such file or directory WindowsTerminal C:\dev\terminal\src\cascadia\WindowsTerminal\IslandWindow.h 7 > Warning The project 'OpenConsolePackage.wapproj' has both an EntryPointExe property and one or more application references. The generated package will use the entry point specified in the EntryPointExe property. OpenConsolePackage C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\DesktopBridge\Microsoft.DesktopBridge.targets 413 > 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 > ``` > > ![image](https://user-images.githubusercontent.com/7961978/58365156-56683000-7ec0-11e9-9388-e4bb20cda734.png) > > Win1903; VS2019 @Morgy93 I was getting the exact errors before updating my windows version to 1903. Have you checked that? On cmd prompt you'll see it at the top when launched, or just type **_ver_** to get your windows version.

claunia commented

@mirogon commented on GitHub (May 25, 2019):

After I built and deployed it, when I start the terminal, its just an empty window.

@mirogon commented on GitHub (May 25, 2019): After I built and deployed it, when I start the terminal, its just an empty window. ![Capture](https://user-images.githubusercontent.com/25257182/58372016-a6261600-7f17-11e9-9035-d01107a0f465.PNG)

claunia commented

@idealsparks commented on GitHub (May 26, 2019):

Can I build it with VS 2019?

I deployed with VS 2019

@idealsparks commented on GitHub (May 26, 2019): > Can I build it with VS 2019? I deployed with VS 2019

claunia commented

@ghost commented on GitHub (May 26, 2019):

@Morgy93 Have you fixed this error? I get the exact errors.
And I'm using win10 1903(10.0.18362.116), microsoft sdk 10.0.18362.0, vs2019, platformtoolset 142.

@ghost commented on GitHub (May 26, 2019): @Morgy93 Have you fixed this error? I get the exact errors. And I'm using win10 1903(10.0.18362.116), microsoft sdk 10.0.18362.0, vs2019, platformtoolset 142.

claunia commented

2026-01-30 22:01:46 +00:00

@ghost commented on GitHub (May 26, 2019):

@Morgy93 I build and depoly succeed with debug config (release build failed).

@ghost commented on GitHub (May 26, 2019): @Morgy93 I build and depoly succeed with debug config (release build failed).

claunia commented

@Morgy93 commented on GitHub (May 26, 2019):

@erDaren Yeah I can confirm. Release fails, but debug works.

@Morgy93 commented on GitHub (May 26, 2019): @erDaren Yeah I can confirm. Release fails, but debug works.

claunia commented

2026-01-30 22:01:46 +00:00

@Gowee commented on GitHub (May 27, 2019):

@erDaren Yeah I can confirm. Release fails, but debug works.

~~I can build it successfully in debug but not release. However, when I try to deploy, it errors out with~~

Severity	Code	Description	Project	File	Line	Suppression State
Error		DEP0700: Registration of the app failed. [0x80073CF6] error 0x87AF000D: The Visual Elements extension failed while processing the Notification element.	CascadiaPackage

.
It works now after several retrying.

@Gowee commented on GitHub (May 27, 2019): > > > @erDaren Yeah I can confirm. Release fails, but debug works. ~I can build it successfully in debug but not release. However, when I try to deploy, it errors out with~ ``` Severity Code Description Project File Line Suppression State Error DEP0700: Registration of the app failed. [0x80073CF6] error 0x87AF000D: The Visual Elements extension failed while processing the Notification element. CascadiaPackage ``` . It works now after several retrying.

claunia commented

@pvginkel commented on GitHub (May 27, 2019):

So, I got the MSIX from the CI build to install. Steps are roughly as follows:

### These steps only need to be done once.

# Create a self signed certificate. See https://docs.microsoft.com/en-us/windows/uwp/packaging/create-certificate-package-signing for more information.

New-SelfSignedCertificate -Type Custom -Subject "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" -KeyUsage DigitalSignature -FriendlyName "WindowsTerminal" -CertStoreLocation "Cert:\LocalMachine\My" -TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.3", "2.5.29.19={text}")

# This will show a thumbprint. Replace the C5C9D98CE9A23FB72C20B4D039876F3D93C3E1FF below with that thumbprint.

$password = ConvertTo-SecureString -String "changeme" -Force -AsPlainText 
Export-PfxCertificate -cert "Cert:\LocalMachine\My\C5C9D98CE9A23FB72C20B4D039876F3D93C3E1FF" -FilePath WindowsTerminal.pfx -Password $password
Remove-Item -Path "Cert:\LocalMachine\My\C5C9D98CE9A23FB72C20B4D039876F3D93C3E1FF"

# Now we'll have a WindowsTerminal.pfx file. This needs to be imported into the "Trusted People" certificate store. Open the "Manage Computer Certificates" application, right click on "Trusted People" and click "Import". Select the PFX and complete the wizard.

# You need to enable "Developer mode" in "Developer settings" before installing this package.

### These steps need to be repeated for every build.

# Sign CascadiaPackage from https://dev.azure.com/ms/Terminal/_build?definitionId=136&_a=summary (pick the latest master branch one and download the artifacts). See https://github.com/MicrosoftDocs/msix-docs/blob/master/msix-src/packaging-tool/bundle-msix-packages.md for more information.

"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\SignTool.exe" sign /fd SHA256 /a  /f WindowsTerminal.pfx /p changeme CascadiaPackage_0.0.1.0_x64.msix

@pvginkel commented on GitHub (May 27, 2019): So, I got the MSIX from the CI build to install. Steps are roughly as follows: ``` ### These steps only need to be done once. # Create a self signed certificate. See https://docs.microsoft.com/en-us/windows/uwp/packaging/create-certificate-package-signing for more information. New-SelfSignedCertificate -Type Custom -Subject "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" -KeyUsage DigitalSignature -FriendlyName "WindowsTerminal" -CertStoreLocation "Cert:\LocalMachine\My" -TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.3", "2.5.29.19={text}") # This will show a thumbprint. Replace the C5C9D98CE9A23FB72C20B4D039876F3D93C3E1FF below with that thumbprint. $password = ConvertTo-SecureString -String "changeme" -Force -AsPlainText Export-PfxCertificate -cert "Cert:\LocalMachine\My\C5C9D98CE9A23FB72C20B4D039876F3D93C3E1FF" -FilePath WindowsTerminal.pfx -Password $password Remove-Item -Path "Cert:\LocalMachine\My\C5C9D98CE9A23FB72C20B4D039876F3D93C3E1FF" # Now we'll have a WindowsTerminal.pfx file. This needs to be imported into the "Trusted People" certificate store. Open the "Manage Computer Certificates" application, right click on "Trusted People" and click "Import". Select the PFX and complete the wizard. # You need to enable "Developer mode" in "Developer settings" before installing this package. ### These steps need to be repeated for every build. # Sign CascadiaPackage from https://dev.azure.com/ms/Terminal/_build?definitionId=136&_a=summary (pick the latest master branch one and download the artifacts). See https://github.com/MicrosoftDocs/msix-docs/blob/master/msix-src/packaging-tool/bundle-msix-packages.md for more information. "C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\SignTool.exe" sign /fd SHA256 /a /f WindowsTerminal.pfx /p changeme CascadiaPackage_0.0.1.0_x64.msix ```

claunia commented

@itaysk commented on GitHub (May 27, 2019):

@pvginkel Thanks, that's a cool workaround. I couldn't sign the package though.. logged

error 0x800B0100: The app package must be digitally signed for signature validation.

I could sign and run the OpenConsole package.. but not the Casadia one.

@itaysk commented on GitHub (May 27, 2019): @pvginkel Thanks, that's a cool workaround. I couldn't sign the package though.. logged ``` error 0x800B0100: The app package must be digitally signed for signature validation. ``` I could sign and run the OpenConsole package.. but not the Casadia one.

claunia commented

@ingenika commented on GitHub (May 28, 2019):

Ctrl + T not open tab here
Microsoft Windows [Version 10.0.18362.116]

@ingenika commented on GitHub (May 28, 2019): `Ctrl + T` not open tab here Microsoft Windows [Version 10.0.18362.116]

claunia commented

@LKI commented on GitHub (May 29, 2019):

@alloai maybe you can try modify open tab key mapping in settings, to avoid key mapping conflict.

@LKI commented on GitHub (May 29, 2019): @alloai maybe you can try modify open tab key mapping in settings, to avoid key mapping conflict.

claunia commented

@archongum commented on GitHub (May 29, 2019):

@Morgy93 @kodaman2
Notice this

Nuget.exe (Needed in build step 2, can be found in Terminal/dep/nuget)
nuget restore OpenConsole.sln

I have the same errors as you do but after doing:

git reset --hard to a release commit
In project root, run dep/nuget/nuget restore OpenConsole.sln

Finally, it worked.

1>------ Deploy started: Project: CascadiaPackage, Configuration: Release x64 ------
Updating the layout...
Deployment complete (0:00:00.068). Full package name: "WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe"
========== Build: 0 succeeded, 0 failed, 25 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========

@archongum commented on GitHub (May 29, 2019): @Morgy93 @kodaman2 Notice this > `Nuget.exe` (Needed in build step 2, can be found in `Terminal/dep/nuget`) > `nuget restore OpenConsole.sln` I have the same errors as you do but after doing: 1. `git reset --hard` to a release commit 2. In project root, run `dep/nuget/nuget restore OpenConsole.sln` Finally, it worked. ``` 1>------ Deploy started: Project: CascadiaPackage, Configuration: Release x64 ------ Updating the layout... Deployment complete (0:00:00.068). Full package name: "WindowsTerminalDev_0.0.1.0_x64__8wekyb3d8bbwe" ========== Build: 0 succeeded, 0 failed, 25 up-to-date, 0 skipped ========== ========== Deploy: 1 succeeded, 0 failed, 0 skipped ========== ```

claunia commented

@Morgy93 commented on GitHub (May 29, 2019):

Could someone PLEASE upload a builded UWP in MEGA or others?

This answers your question:
https://github.com/microsoft/terminal/blob/master/README.md#there-are-no-binaries-to-download-quite-yet
TL;DR: Mid-June

@archongum What release commit did you reset to? I'd love to git bisect to find the error causing commit.

@Morgy93 commented on GitHub (May 29, 2019): > Could someone PLEASE upload a **builded** UWP in MEGA or others? This answers your question: https://github.com/microsoft/terminal/blob/master/README.md#there-are-no-binaries-to-download-quite-yet TL;DR: Mid-June ----- @archongum What release commit did you reset to? I'd love to `git bisect` to find the error causing commit.

claunia commented

@archongum commented on GitHub (May 29, 2019):

@Morgy93
This one: https://github.com/microsoft/terminal/commits/v0.1.1431.0

@archongum commented on GitHub (May 29, 2019): @Morgy93 This one: https://github.com/microsoft/terminal/commits/v0.1.1431.0

claunia commented

@ingenika commented on GitHub (May 30, 2019):

@LKI
Thanks, I've found that I've two builds install, one preview and one dev, for the dev build, the tab is displayed.

@ingenika commented on GitHub (May 30, 2019): @LKI Thanks, I've found that I've two builds install, one preview and one dev, for the dev build, the tab is displayed.

claunia commented

@ghost commented on GitHub (May 30, 2019):

Hi, so I am using vs 2019 and the build process went great but when I try to deploy I get this this error message, anyone can help please?

@ghost commented on GitHub (May 30, 2019): Hi, so I am using vs 2019 and the build process went great but when I try to deploy I get this this error message, anyone can help please? ![image](https://user-images.githubusercontent.com/45731575/58657549-c8a49e80-831e-11e9-9086-caa245b05509.png)

claunia commented

@ingenika commented on GitHub (May 30, 2019):

@NoobSaibot78 change to x64,

@ingenika commented on GitHub (May 30, 2019): @NoobSaibot78 change to x64, ![image](https://user-images.githubusercontent.com/23131104/58661337-e3f2b800-82e4-11e9-8310-6ba8c35be312.png)

claunia commented

@ghost commented on GitHub (May 31, 2019):

@alloai Thanks it works perfectly ✌️

@ghost commented on GitHub (May 31, 2019): @alloai Thanks it works perfectly ✌️

claunia commented

@tfenster commented on GitHub (Jun 3, 2019):

So, I got the MSIX from the CI build to install. Steps are roughly as follows:

### These steps only need to be done once.

...

### These steps need to be repeated for every build.

# Sign CascadiaPackage from https://dev.azure.com/ms/Terminal/_build?definitionId=136&_a=summary (pick the latest master branch one and download the artifacts). See https://github.com/MicrosoftDocs/msix-docs/blob/master/msix-src/packaging-tool/bundle-msix-packages.md for more information.

"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\SignTool.exe" sign /fd SHA256 /a  /f WindowsTerminal.pfx /p changeme CascadiaPackage_0.0.1.0_x64.msix

If you name the exported cert file CascadiaPackage_TemporaryKey.pfx, then it gets automatically picked up during build and you don't need to sign the msix manually

@tfenster commented on GitHub (Jun 3, 2019): > So, I got the MSIX from the CI build to install. Steps are roughly as follows: > > ``` > ### These steps only need to be done once. > > ... > > ### These steps need to be repeated for every build. > > # Sign CascadiaPackage from https://dev.azure.com/ms/Terminal/_build?definitionId=136&_a=summary (pick the latest master branch one and download the artifacts). See https://github.com/MicrosoftDocs/msix-docs/blob/master/msix-src/packaging-tool/bundle-msix-packages.md for more information. > > "C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\SignTool.exe" sign /fd SHA256 /a /f WindowsTerminal.pfx /p changeme CascadiaPackage_0.0.1.0_x64.msix > ``` If you name the exported cert file CascadiaPackage_TemporaryKey.pfx, then it gets automatically picked up during build and you don't need to sign the msix manually

claunia commented

@bgshacklett commented on GitHub (Jun 9, 2019):

Using the name CascadiaPackage_TemporaryKey.pfx did not have any effect for me. I still got the same error:

Ask the app developer for a new app package. This one isn't signed with a trusted certificate (0x800B0100)

I'm running into an issue with signtool.exe as well:

SignTool Error: This file format cannot be signed because it is not recognized.
SignTool Error: An error occurred while attempting to sign: CascadiaPackage_0.0.1.0_x64.msix

Number of errors: 1

Here's the script I'm running:
https://gist.github.com/bgshacklett/2cac67bf99ddfd9f85221d90767296fb

@bgshacklett commented on GitHub (Jun 9, 2019): Using the name `CascadiaPackage_TemporaryKey.pfx` did not have any effect for me. I still got the same error: ``` Ask the app developer for a new app package. This one isn't signed with a trusted certificate (0x800B0100) ``` I'm running into an issue with `signtool.exe` as well: ``` SignTool Error: This file format cannot be signed because it is not recognized. SignTool Error: An error occurred while attempting to sign: CascadiaPackage_0.0.1.0_x64.msix Number of errors: 1 ``` Here's the script I'm running: https://gist.github.com/bgshacklett/2cac67bf99ddfd9f85221d90767296fb

claunia commented

@musm commented on GitHub (Jun 10, 2019):

@musm commented on GitHub (Jun 10, 2019): ![image](https://user-images.githubusercontent.com/4319522/59215478-58e8ac00-8b87-11e9-9574-5502e48c670c.png)

claunia commented

@ca0abinary commented on GitHub (Jun 12, 2019):

This worked for me:

# Generate self-signed certificate
"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x64\MakeCert" /n "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /r /h 0 /eku "1.3.6.1.5.5.7.3.3,1.3.6.1.4.1.311.10.3.13" /e "01/01/2100" /sv WindowsTerminal.pvk WindowsTerminal.cer
"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x64\pvk2pfx" /pvk WindowsTerminal.pvk /pi pvkPassword /spc WindowsTerminal.cer /pfx WindowsTerminal.pfx /po changeme /f
# Add to trusted people store
Certutil -addStore TrustedPeople WindowsTerminal.cer
# Sign msix
"C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x64\SignTool.exe" sign /fd SHA256 /a  /f WindowsTerminal.pfx /p changeme CascadiaPackage_0.0.1.0_x64.msix

@ca0abinary commented on GitHub (Jun 12, 2019): This worked for me: ```powershell # Generate self-signed certificate "C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x64\MakeCert" /n "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /r /h 0 /eku "1.3.6.1.5.5.7.3.3,1.3.6.1.4.1.311.10.3.13" /e "01/01/2100" /sv WindowsTerminal.pvk WindowsTerminal.cer "C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x64\pvk2pfx" /pvk WindowsTerminal.pvk /pi pvkPassword /spc WindowsTerminal.cer /pfx WindowsTerminal.pfx /po changeme /f # Add to trusted people store Certutil -addStore TrustedPeople WindowsTerminal.cer # Sign msix "C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x64\SignTool.exe" sign /fd SHA256 /a /f WindowsTerminal.pfx /p changeme CascadiaPackage_0.0.1.0_x64.msix ```

claunia commented

@dash-mode commented on GitHub (Jun 13, 2019):

can't see deploy after building. anyway we can run in cmd?

Do you see the Solution Explorer side menu?
If not, then press Ctrl+Alt+L or go to View -> Solution Explorer.
At the top of the Solution Explorer, the top most item is: Solution 'OpenConsole' (47 projects).
Right click it and choose Deploy Solution from the context menu.

Hey! The tutorial says click on terminal > cascadia package, then right click on it and deploy. Do both of these methods work, or only one of them?

Also I noticed some people deploy the project in debug mode, while others deployed it in release mode?
What's the consensus regarding this?

@dash-mode commented on GitHub (Jun 13, 2019): > > can't see deploy after building. anyway we can run in cmd? > > Do you see the Solution Explorer side menu? > If not, then press Ctrl+Alt+L or go to View -> Solution Explorer. > At the top of the Solution Explorer, the top most item is: Solution 'OpenConsole' (47 projects). > Right click it and choose Deploy Solution from the context menu. > > ![image](https://user-images.githubusercontent.com/16970186/57322619-3c7acf00-7104-11e9-815e-4d7427fab4bf.png) Hey! The tutorial says click on terminal > cascadia package, then right click on it and deploy. Do both of these methods work, or only one of them? Also I noticed some people deploy the project in debug mode, while others deployed it in release mode? What's the consensus regarding this?

claunia commented

@dash-mode commented on GitHub (Jun 13, 2019):

Nvm, I figured it out. I deployed the root folder (solutions), and in release mode.
I just installed windows terminal, and I am excited to check it out.

@dash-mode commented on GitHub (Jun 13, 2019): Nvm, I figured it out. I deployed the root folder (solutions), and in release mode. I just installed windows terminal, and I am excited to check it out.

claunia commented

@AdrianoCahete commented on GitHub (Jun 14, 2019):

Also I noticed some people deploy the project in debug mode, while others deployed it in release mode?
What's the consensus regarding this?

In my understanding, there's no directly difference for your self use. Debug mode can contain some symbols and be a little bigger, when Release mode can be smaller since the deploy can run some improvements/optimization tasks.

But I really don't think that is something really different in that alpha stage.

@AdrianoCahete commented on GitHub (Jun 14, 2019): > Also I noticed some people deploy the project in debug mode, while others deployed it in release mode? > What's the consensus regarding this? In my understanding, there's no directly difference for your self use. Debug mode can contain some symbols and be a little bigger, when Release mode can be smaller since the deploy can run some improvements/optimization tasks. But I really don't think that is something *really* different in that alpha stage.

claunia commented

@Byloth commented on GitHub (Jun 14, 2019):

Hi, everybody!
I'm trying to run this new Windows Terminal.

After some difficulties and a few attempts I was able to build and deploy the project locally.
«Great! Finally!» I said to myself, just before clicking on the Windows Terminal (Dev Build) in the Start menu...

This was the result: an empty window.

After a few seconds, it simply disappeared and then...
Well... Nothing more!

I read some comments (like this one https://github.com/microsoft/Terminal/issues/489#issuecomment-492177267) and tried to delete any profiles.json files but nothing has changed.

Any other ideas?
Thank you all!

Here are some useful (hopefully) information about my current system:

Windows 10 1903 Build 18362.175
Developer mode enabled
Visual Studio 2019
Repo version built: v0.1.1621.0 (6fc0978ddb)

🚀 I recently opened the Issue #1364 related to this problem.

If you're experiencing the same behaviour, you can find here some other detailed information about it.

@Byloth commented on GitHub (Jun 14, 2019): Hi, everybody! I'm trying to run this new Windows Terminal. After some difficulties and a few attempts I was able to build and deploy the project locally. *«Great! Finally!»* I said to myself, just before clicking on the `Windows Terminal (Dev Build)` in the Start menu... This was the result: an empty window. > ![image](https://user-images.githubusercontent.com/14953974/59504305-f5ba8a80-8ea2-11e9-929f-4a56104b77b9.png) After a few seconds, it simply disappeared and then... Well... Nothing more! --- I read some comments (like this one https://github.com/microsoft/Terminal/issues/489#issuecomment-492177267) and tried to delete any `profiles.json` files but nothing has changed. Any other ideas? Thank you all! --- Here are some useful (hopefully) information about my current system: > Windows 10 1903 Build 18362.175 > `Developer mode` enabled > Visual Studio 2019 > Repo version built: v0.1.1621.0 (6fc0978ddb41a7276aa965dba70df49a13d2ab56) --- 🚀 I recently opened the **Issue #1364** related to this problem. If you're experiencing the same behaviour, you can find here some other detailed information about it.

claunia commented

[image]https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F14953974%2F59504305-f5ba8a80-8ea2-11e9-929f-4a56104b77b9.png&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290405684&sdata=rMk46apT2apEI8kTsaiuyBacg61ZqgwUQVX0NwnMV1s%3D&reserved=0

@pistons-2004 commented on GitHub (Jun 14, 2019):

Could you please unsubscribe me from all of these threads. Its overwhelming

From: Matteo Bilotta notifications@github.com
Sent: Friday, June 14, 2019 7:07 AM
To: microsoft/terminal terminal@noreply.github.com
Cc: Subscribed subscribed@noreply.github.com
Subject: Re: [microsoft/terminal] Guide for build and installation (#489)

Hi, everybody!
I'm trying to run this new Windows Terminal.

After some difficulties and a few attempts I was able to build and deploy the project locally.
«Great! Finally!» I said to myself, just before clicking on the Windows Terminal (Dev Build) in the Start menu...

This was the result: an empty window.

After a few seconds, it simply disappeared and then...
Well... Nothing more!

I read some comments (like this one #489 (comment)https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fissues%2F489%23issuecomment-492177267&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290415692&sdata=YGfemyxYCdZBtD%2F3U1bAaczZeJG2pAHV7IKrrANLMh4%3D&reserved=0) and tried to delete any profiles.json files but nothing has changed.

Any other ideas?
Thank you all!

Here are some useful (hopefully) information about my current system:

Windows 10 1903 Build 18362.175
Visual Studio 2019
Repo version built: v0.1.1621.0 (6fc0978https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fcommit%2F6fc0978ddb41a7276aa965dba70df49a13d2ab56&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290425701&sdata=ubqTm0Wa9xzJL8Jsf6tKDSmCMntRxafIPOoazPnEPFg%3D&reserved=0)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fissues%2F489%3Femail_source%3Dnotifications%26email_token%3DAMAAYZOTXBHT35VESGFBKWLP2N3VXA5CNFSM4HLHRKI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXWPDOQ%23issuecomment-502067642&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290425701&sdata=nsmHbdfbQJhW0qHQegsCU8w9tlriwrsTe5oNColnKoU%3D&reserved=0, or mute the threadhttps://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMAAYZICWRIFMDKMHSUHM7LP2N3VXANCNFSM4HLHRKIQ&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290435709&sdata=3LVEYEzkxE09SC1RZImkCT8%2BTptEPSQlWB3hI3s6xoA%3D&reserved=0.

@pistons-2004 commented on GitHub (Jun 14, 2019): Could you please unsubscribe me from all of these threads. Its overwhelming From: Matteo Bilotta <notifications@github.com> Sent: Friday, June 14, 2019 7:07 AM To: microsoft/terminal <terminal@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: Re: [microsoft/terminal] Guide for build and installation (#489) Hi, everybody! I'm trying to run this new Windows Terminal. After some difficulties and a few attempts I was able to build and deploy the project locally. «Great! Finally!» I said to myself, just before clicking on the Windows Terminal (Dev Build) in the Start menu... This was the result: an empty window. [image]<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F14953974%2F59504305-f5ba8a80-8ea2-11e9-929f-4a56104b77b9.png&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290405684&sdata=rMk46apT2apEI8kTsaiuyBacg61ZqgwUQVX0NwnMV1s%3D&reserved=0> After a few seconds, it simply disappeared and then... Well... Nothing more! ________________________________ I read some comments (like this one #489 (comment)<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fissues%2F489%23issuecomment-492177267&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290415692&sdata=YGfemyxYCdZBtD%2F3U1bAaczZeJG2pAHV7IKrrANLMh4%3D&reserved=0>) and tried to delete any profiles.json files but nothing has changed. Any other ideas? Thank you all! ________________________________ Here are some useful (hopefully) information about my current system: Windows 10 1903 Build 18362.175 Visual Studio 2019 Repo version built: v0.1.1621.0 (6fc0978<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fcommit%2F6fc0978ddb41a7276aa965dba70df49a13d2ab56&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290425701&sdata=ubqTm0Wa9xzJL8Jsf6tKDSmCMntRxafIPOoazPnEPFg%3D&reserved=0>) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fterminal%2Fissues%2F489%3Femail_source%3Dnotifications%26email_token%3DAMAAYZOTXBHT35VESGFBKWLP2N3VXA5CNFSM4HLHRKI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXWPDOQ%23issuecomment-502067642&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290425701&sdata=nsmHbdfbQJhW0qHQegsCU8w9tlriwrsTe5oNColnKoU%3D&reserved=0>, or mute the thread<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMAAYZICWRIFMDKMHSUHM7LP2N3VXANCNFSM4HLHRKIQ&data=02%7C01%7Cbugbeed%40michigan.gov%7C5cefc88d219d4eb64b9408d6f0b87147%7Cd5fb7087377742ad966a892ef47225d1%7C0%7C0%7C636961072290435709&sdata=3LVEYEzkxE09SC1RZImkCT8%2BTptEPSQlWB3hI3s6xoA%3D&reserved=0>.

claunia commented

@AdrianoCahete commented on GitHub (Jun 14, 2019):

Could you please unsubscribe me from all of these threads. Its overwhelming

You're automatic subscribed if you comment or subscribe to issue.
You need to enter in the issue Github page, go to the right sidebar, on the Notification button, change to "Custom" or click on "Unsubscribe".

But remember that every time that you comment on a issue, you'll be auto subscribed again.

@AdrianoCahete commented on GitHub (Jun 14, 2019): > Could you please unsubscribe me from all of these threads. Its overwhelming You're automatic subscribed if you comment or subscribe to issue. You need to enter in the issue Github page, go to the right sidebar, on the Notification button, change to "Custom" or click on "Unsubscribe". **But remember that every time that you comment on a issue, you'll be auto subscribed again.**

claunia commented

@rdevraj950 commented on GitHub (Jun 16, 2019):

Open Windows Settings - Upgrade & Security - For Developers, switch App sources to Developer mode

Upgrade & Security should be Update & Security

@rdevraj950 commented on GitHub (Jun 16, 2019): > 1. Open `Windows Settings` - `Upgrade & Security` - `For Developers`, switch `App sources` to `Developer mode` `Upgrade & Security` should be `Update & Security`

claunia commented

@adeloyedeji commented on GitHub (Jun 19, 2019):

Open Windows Settings - Upgrade & Security - For Developers, switch App sources to Developer mode

Upgrade & Security should be Update & Security

This didn't work for me. Still loading blank screen

@adeloyedeji commented on GitHub (Jun 19, 2019): > > 1. Open `Windows Settings` - `Upgrade & Security` - `For Developers`, switch `App sources` to `Developer mode` > > `Upgrade & Security` should be `Update & Security` This didn't work for me. Still loading blank screen

claunia commented

@ihdavids commented on GitHub (Jun 19, 2019):

I had it running.
I am an avid emacs user and was excited at the prospect of this + WSL 2.
A little bit of tinkering and I had it building and running but I found it really bogs down on my surface. There are quite a few instances of WSL running after a little experimentation which I found a little surprising given I didn't have any tabs running WSL at that point.

I am also now unable to launch the terminal after changing the font and scheme now and it fails to launch every time. We are far from stable it seems. :(

@ihdavids commented on GitHub (Jun 19, 2019): I had it running. I am an avid emacs user and was excited at the prospect of this + WSL 2. A little bit of tinkering and I had it building and running but I found it really bogs down on my surface. There are quite a few instances of WSL running after a little experimentation which I found a little surprising given I didn't have any tabs running WSL at that point. I am also now unable to launch the terminal after changing the font and scheme now and it fails to launch every time. We are far from stable it seems. :(

claunia commented

2026-01-30 22:01:53 +00:00

@mKay00 commented on GitHub (Jun 19, 2019):

Of course it still takes time, but you are welcome to contribute 😉
Maybe you can try to figure out, why there are instances of WSL running although you have no tabs open.

If you are unable to open after you made changes in the settings, you probably corrupted your profiles.json. Go to "%LOCALAPPDATA%\packages\WindowsTerminalDev_8wekyb3d8bbwe\RoamingState" and delete your profiles.json to regenerate a new one with default settings.

@mKay00 commented on GitHub (Jun 19, 2019): Of course it still takes time, but you are welcome to [contribute](https://github.com/microsoft/terminal/blob/master/doc/contributing.md) 😉 Maybe you can try to figure out, why there are instances of WSL running although you have no tabs open. If you are unable to open after you made changes in the settings, you probably corrupted your profiles.json. Go to "%LOCALAPPDATA%\packages\WindowsTerminalDev_8wekyb3d8bbwe\RoamingState" and delete your profiles.json to regenerate a new one with default settings.

claunia commented

@musm commented on GitHub (Jun 19, 2019):

Now getting

@musm commented on GitHub (Jun 19, 2019): Now getting ![image](https://user-images.githubusercontent.com/4319522/59786764-fc2b7680-9295-11e9-968b-bdc421aab7da.png)

claunia commented

2026-01-30 22:01:53 +00:00

@DHowett-MSFT commented on GitHub (Jun 19, 2019):

@adeloyedeji if you are seeing a blank screen, make sure you are targeting the right architecture. you cannot run windows terminal x86 on an x64 machine.

@DHowett-MSFT commented on GitHub (Jun 19, 2019): @adeloyedeji if you are seeing a blank screen, make sure you are targeting the right architecture. you cannot run windows terminal x86 on an x64 machine.

claunia commented

@ihdavids commented on GitHub (Jun 20, 2019):

Of course it still takes time, but you are welcome to contribute 😉
Maybe you can try to figure out, why there are instances of WSL running although you have no tabs open.

If you are unable to open after you made changes in the settings, you probably corrupted your profiles.json. Go to "%LOCALAPPDATA%\packages\WindowsTerminalDev_8wekyb3d8bbwe\RoamingState" and delete your profiles.json to regenerate a new one with default settings.

Yup,
I made a typo in the font name! Thank you!

@ihdavids commented on GitHub (Jun 20, 2019): > Of course it still takes time, but you are welcome to [contribute](https://github.com/microsoft/terminal/blob/master/doc/contributing.md) 😉 > Maybe you can try to figure out, why there are instances of WSL running although you have no tabs open. > > If you are unable to open after you made changes in the settings, you probably corrupted your profiles.json. Go to "%LOCALAPPDATA%\packages\WindowsTerminalDev_8wekyb3d8bbwe\RoamingState" and delete your profiles.json to regenerate a new one with default settings. Yup, I made a typo in the font name! Thank you!

claunia commented

@ihdavids commented on GitHub (Jun 20, 2019):

With each WSL tab I open and then close there does seem to be something left behind. I currently have closed all WSL tabs and I am seeing the following in the process list?

@ihdavids commented on GitHub (Jun 20, 2019): ![WslLeak](https://user-images.githubusercontent.com/1059210/59819925-c2cb2900-92de-11e9-9e83-fb3a64b563a2.png) With each WSL tab I open and then close there does seem to be something left behind. I currently have closed all WSL tabs and I am seeing the following in the process list?

claunia commented

@DHowett-MSFT commented on GitHub (Jun 20, 2019):

@ihdavids The "WSL Background Host" processes are kept around for some time to support WSL background scenarios. This is not exactly a Terminal issue.

@DHowett-MSFT commented on GitHub (Jun 20, 2019): @ihdavids The "WSL Background Host" processes are kept around for some time to support WSL background scenarios. This is not exactly a Terminal issue.

claunia commented

@simkessy commented on GitHub (Jun 21, 2019):

I tried to build and I just got this instead:

@simkessy commented on GitHub (Jun 21, 2019): I tried to build and I just got this instead: ![image](https://user-images.githubusercontent.com/5871660/59887549-a380da00-9378-11e9-8f85-3112aa2d66d1.png)

claunia commented

@musm commented on GitHub (Jun 21, 2019):

I get the same errors. Can anyone help

@musm commented on GitHub (Jun 21, 2019): I get the same errors. Can anyone help

claunia commented

@yzlnew commented on GitHub (Jun 21, 2019):

It seems that we can get a preview build in mid-June. Is this still on track for a pre-release?
Edit: You can download it form the Microsoft Store now.

@yzlnew commented on GitHub (Jun 21, 2019): It seems that we can get a preview build in mid-June. Is this still on track for a pre-release? Edit: You can download it form the Microsoft Store now.

claunia commented

@adeloyedeji commented on GitHub (Jun 22, 2019):

@adeloyedeji if you are seeing a blank screen, make sure you are targeting the right architecture. you cannot run windows terminal x86 on an x64 machine.

And I still get a blank screen?

@adeloyedeji commented on GitHub (Jun 22, 2019): > @adeloyedeji if you are seeing a blank screen, make sure you are targeting the right architecture. you cannot run windows terminal x86 on an x64 machine. ![winspec1](https://user-images.githubusercontent.com/6009197/59960661-6bd27900-94c3-11e9-81af-de7c46292511.PNG) ![winspec2](https://user-images.githubusercontent.com/6009197/59960663-768d0e00-94c3-11e9-9388-cf33ed272c38.PNG) ![winrun](https://user-images.githubusercontent.com/6009197/59960720-51e56600-94c4-11e9-996e-20ffd54cb0fb.PNG) And I still get a blank screen?

claunia commented