Issue 1:
I'm trying to build Windows Terminal from command line using VS 2017 on Windows 10 x64 insider, build 18362.86. I kept getting the error below even after installing all the VS 2017 components that have something to do with C++ and .Net. From the error message it seems the build surprisingly involves VS 2019 (which I have installed as well). My expectation is VS 2019 should not be involved as I use VS 2017 command line. I then decided to install all the components that have something to do with C++ and .Net for VS 2019. I still get the same error message.

My steps for building:

Clone the repo from github

Do git submodule update --init --recursive

Do .\tools\razzle.cmd

Do bcz

What am I missing? The error message is as below:

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v150\Microsoft.CppCommon.targets(2128,3): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.Cpp.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. [c:\Users\Tembo\Desktop\qnd\cpp\Terminal10\src\cascadia\TerminalSetting\TerminalSettings.vcxproj]

Issue 2:
Tools needed

VS2017 or higher with the following packages ("Workloads" tab in Visual Studio Installer) :

1.1 Desktop Development with C++.

1.2 Universal Windows Platform Development.

1.3 Windows 10 SDK (10.0.18362.0).

1.4 If you're running VS2019, you'll also need to install either v141 Toolset or v142 Toolset.

Git command-line tool.

Nuget.exe (Needed in build step 3, can be found in Terminal/dep/nuget).

Build Steps

git clone this repository, not download .zip file.

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

Open OpenConsole.sln with Visual Studio.

Build whole solution(F7) with your platform(x86/x64) and release mode, you may need to fix some build errors:

5.1 C2220 and code page warnings: All errors and warnings are encoding error of unicode characters, a helpful workaround is to modify corresponding file encoding to UTF-8 BOM (Notepad++ is recommended).

5.2 Errors in src/tools/vtpipeterm/main.cpp: In addtion, you should also add u8 prefix before string literals with unicode characters, e.g. line 395, 398, 401 and 404.

Workaround

Try build with PR 458 or PR 549, both of them can build successfully.

Installation

Unfortunately, the generated .appx doesn't have any certificates, so it cannot be installed via double-click or powershell, the only way to install is to deploy the solution in VS.

Open Windows Settings - Upgrade & Security - For Developers, switch App sources to Developer mode.

Right click on CascadiaPackage project (under Solution/Terminal), select Deploy Solution to install, then you'll find Windows Terminal (Preview) in start menu.

Settings

After open the terminal, you can't see any menu buttons.

Just press Ctrl + T to open a new tab, and you'll see a drop-down button in the tab bar.

Click it and select Settings, then you can modify the configuration via opened profiles.json.

Add WSL

Create a new session in profiles, with content copied from profiles/cmd.

Give it a new guid.

Give it a new name, such as WSL.

Specify its commandline to wsl.exe.

Then you'll find WSL in the drop-down menu of tab bar.

Here're sample codes:

{
"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"
}