Fix the fact that win32 builds don't put the objects in a folder... apparently.

* Refactors TerminalApp into two projects: 
  - TerminalAppLib, which builds a .lib, and includes all the code
  - TerminalApp, which builds a dll by linking the lib
* Adds a TerminalApp.Unit.Tests project
  - Includes the ability to test cppwinrt types we've authored using a SxS manifest for unpackaged winrt activation
  - includes the ability to test types with XAML content using an appxmanifest
* Adds a giant doc explaining how this was all done. Really, just go read that doc, it'll really help you understand what's going on in this PR.

-------------------------
These are some previous commit messages. They may be helpful to future readers.

* Start adding unittests for json parsing, end up creating a TerminalAppLib project to make a lib. See #1042

* VS automatically did this for me

* This is a dead end

  I tried including the idl-y things into the lib, but that way leads insanity

  If you want to make a StaticLibrary, then suddenly the winrt toolchain forgets
  that ProjectReferences can have winmd's in them, so it won't be able to
  compile any types from the referenced projects. If you instead try to manually
  reference the types, you'll get duplicate types up the wazoo, which of course
  is insane, since we're referencing them the _one_ time

* Yea just follow #1042 on github for status

  So current state:

  1. If you try to add a `Reference` to all of MUX.Markup, TerminalControl and
     TerminalSettings, then mdmerge will complain about all   the types from
     TerminalSettings being defined twice. In this magic scenario, the
     dependencies of TerminalControl are used directly   for some reason:

```
  12>    Load input metadata file ...OpenConsole\x64\Debug\TerminalSettings\Microsoft.Terminal.Settings.winmd.
  12>    Load input metadata file ...OpenConsole\x64\Debug\TerminalControl\Microsoft.Terminal.Settings.winmd.
  12>    Load input metadata file ...OpenConsole\x64\Debug\TerminalControl\Microsoft.Terminal.TerminalConnection.winmd.
  12>    Load input metadata file ...OpenConsole\x64\Debug\TerminalControl\Microsoft.Terminal.TerminalControl.winmd.
  12>    Load input metadata file ...OpenConsole\x64\Debug\Microsoft.UI.Xaml.Markup\Microsoft.UI.Xaml.Markup.winmd.
```

  2. If you don't add a `Reference` TerminalControl, then it'll complain about
     being unable to find the type TitleChangedEventArgs,   which is defined in
     TerminalControl.

  3. If you don't add a `Reference` TerminalSettings, then it'll complain about
     being unable to find the type KeyChord and other   types from
     TerminalSettings. In this scenario, it doesn't recurse on the other
     dependencies from TerminalControl for whatever   reason.

  4. If you instead try to add all 3 as a `ProjectReference`, then it'll
     complain about being unable to find TitleChangedEventArgs,   as in 2.
     Presumably, it;ll have troubles with the other types too, as none of the 3
     are actually included in the midlrt.rsp file.

  5. If you add all 3 as a `ProjectReference`, then also add TerminalControl as
     a `Reference`, you'll get a `MIDL2011: [msg]  unresolved type declaration
     Microsoft.UI.Xaml.Markup.XamlApplication`

  6. If you add all 3 as a `ProjectReference`, then also add TerminalControl AND
     MUX.Markup as a `Reference`, you'll get the same   result as 3.

* what if we just don't idl

  This seems to compile

* This compiles but I broke the MUX resources

  look at the App.xaml change. in this changelist. That's what's broken right now. Lets fix that!

* lets do this

    If I leave the MUX nuget out of the project, I'll get a compile error in
    App.xaml:

    ```
    ...OpenConsole\src\cascadia\TerminalApp\App.xaml(21,40): XamlCompiler error WMC0001: Unknown type 'XamlControlsResources' in XML namespace 'using:Microsoft.UI.Xaml.Controls'
    ```

    If I add it back to the project, it works

* Some cleanup from the previous commit

* This is busted again.

  Doing a clean build didn't work.

    A clean rebuild of the project, paired with some removal of dead code
    revealed a problem with what I have so far.

    TerminalAppLib depends on the generation of two headers,
    `AppKeyBindings.g.h` and `App.g.h`, as those define some of bits of the
    winrt types. They're needed to be able to compile the implementations.
    Presumably that's not getting generated by the lib project, because the dll
    project is the one to generate that file.

    So we need to move the idl's to the lib project. This created maddness,
    because of course the Duplicate Type thing. The solution to that is to
    actually mark the winrt DLLs that we're chaining up through us as

    ```
        <Private>false</Private>
        <CopyLocalSatelliteAssemblies>false</CopyLocalSatelliteAssemblies>
    ```

    This will prevent them from getting double-included.

    This still doesn't work however, since
    ```
    app.cpp(40): error C2039: 'XamlMetaDataProvider': is not a member of 'winrt::TerminalApp'
    error C3861: 'XamlMetaDataProvider': identifier not found
    ```

    So we need to figure that out. The dll project is still generating the right
    header, so lets look there.

* Move the xaml stuff to the lib

  This compiles, but when we launch, we fail to load the tabviewcontrol
  resources again. So that's not what you want. Why is it not included?

* It works again!

  * Use the pri, xbf files from TerminalAppLib, not TerminalApp
  * Manually make TerminalApp include a reference to TerminalAppLib's
    TerminalApp.winmd. This will force the build to copy TerminalApp.winmd to
    TerminalApp/, which WindowsTerminal needs to be able to ProjectReference the
    TerminalApp project (it's expecting it to have a winmd)
  * Remove the module.g.cpp from TerminalApp, and move to TerminalAppLib. The
    dll doesn't do any codegen anymore.

* Agressively clean up these files

* Clean up unnecessary includes in the dll pch.h

* This does NOT work.

  The WindowsxamlManager call crashes. I'm thinking it has to do with activation
  of winrt types from a dll.

  Email out to @Austin-Lamb to see if he can assist

* This gets our cppwinrt types working, but xaml islands is still broken

* Split the tests apart, so they aren't insane

* These are the magic words to make xaml islands work

* All this witchcraft is necessary to make XAML+MUX work right

* Clean this up a bit and add comments

* Create an enormous doc explaining this madness

* Unsure how this got changed.

* Trying to get the CI build to work again.

  This resolves the MUX issue. We need to manually include it, because their package's target doesn't mark it as CopyLocalSatelliteAssemblies=false, Private=false.

  However, the TerminalApp project is still able to magically reason that the TerminalAppLib project should be included in the MdMerge step, because it think's it's a `GetCppWinRTStaticProjectReferences` reference.

* Update cppwinrt to the latest version - this fixes the MSBuild

  * I still need to re-add the KeyModifiers checks from TermControl. I think
    this update broke `operator&` for that enum.
  * There needs to be some cleanup obviously
  * The doc should be updated as well

* Clean up changes from cppwinrt update

* Try doing this, even though it seems wrong

* Lets try this (press x to doubt)

* Clean up vcxproj file, and remove appxmanifest change from previous commit

* Update to the latest TAEF release, maybe that'll work

* Let's try a prerelease version, shall we?

* Add notes about TAEF package, comment out tests

* Format the code

* Hopefully fix the arm64 and x86 builds

  also a typo

* Fix PR nits

* Fix some bad merge conflicts

* Some cleanup from the merge

* Well I was close to getting the merge right

* I believe this will fix CI

* Apply suggestions from code review

Co-Authored-By: Carlos Zamora <carlos.zamora@microsoft.com>

* These definitely need to be fixed

* Try version detecting in the test

  IDK if this will build, I'm letting the CI try while I clean rebuild locally

* Try blindly updating to the newest nuget version

* Revert "Try blindly updating to the newest nuget version"

This reverts commit b72bd9eb73.

* We're just going to see if these work in CI with this change

* Comment the tests back out. Windows Server 2019 is 10.0.17763.557

* Remove the nuget package

  We don't need this package anymore now that we're hosting it

* Okay this _was_ important

.clang-format

@@ -0,0 +1,93 @@
+
+AccessModifierOffset: -4
+AlignAfterOpenBracket: Align
+#AllowAllArgumentsOnNextLine: false
+AlignConsecutiveAssignments: false
+AlignConsecutiveDeclarations: false
+#AllowAllConstructorInitializersOnNextLine: false
+AlignEscapedNewlines: Left
+AlignOperands: true
+AlignTrailingComments: false
+AllowAllParametersOfDeclarationOnNextLine: false
+AllowShortFunctionsOnASingleLine: Inline
+AllowShortCaseLabelsOnASingleLine: false
+AllowShortIfStatementsOnASingleLine: false
+#AllowShortLambdasOnASingleLine: Inline
+AllowShortLoopsOnASingleLine: false
+AlwaysBreakAfterReturnType: None
+AlwaysBreakBeforeMultilineStrings: false
+AlwaysBreakTemplateDeclarations: Yes
+BinPackArguments: false
+BinPackParameters: false
+BraceWrapping:
+  AfterClass: true
+  AfterControlStatement: true
+  AfterEnum: true
+  AfterFunction: true
+  AfterNamespace: true
+  AfterObjCDeclaration: true
+  AfterStruct: true
+  AfterUnion: true
+  AfterExternBlock: false
+  BeforeCatch: true
+  BeforeElse: true
+  IndentBraces: false
+  SplitEmptyFunction: true
+  SplitEmptyRecord: true
+  SplitEmptyNamespace: true
+BreakBeforeBinaryOperators: None
+BreakBeforeBraces: Custom
+BreakBeforeTernaryOperators: false
+BreakConstructorInitializers: AfterColon
+BreakInheritanceList: AfterColon
+ColumnLimit: 0
+CommentPragmas: "suppress"
+CompactNamespaces: false
+ConstructorInitializerAllOnOneLineOrOnePerLine: true
+ConstructorInitializerIndentWidth: 4
+ContinuationIndentWidth: 4
+Cpp11BracedListStyle: false
+DerivePointerAlignment: false
+FixNamespaceComments: false
+IncludeBlocks: Regroup
+IncludeCategories:
+    - Regex: '^.*(precomp|pch|stdafx)'
+      Priority: -1
+    - Regex: '^".*"'
+      Priority: 1
+    - Regex: '^<.*>'
+      Priority: 2
+    - Regex: '.*'
+      Priority: 3
+IndentCaseLabels: false
+IndentPPDirectives: None
+IndentWidth: 4
+IndentWrappedFunctionNames: false
+KeepEmptyLinesAtTheStartOfBlocks: false
+MacroBlockBegin: "BEGIN_TEST_METHOD_PROPERTIES|BEGIN_MODULE|BEGIN_TEST_CLASS|BEGIN_TEST_METHOD"
+MacroBlockEnd: "END_TEST_METHOD_PROPERTIES|END_MODULE|END_TEST_CLASS|END_TEST_METHOD"
+MaxEmptyLinesToKeep: 1
+NamespaceIndentation: All
+PointerAlignment: Left
+ReflowComments: false
+SortIncludes: false
+SortUsingDeclarations: true
+SpaceAfterCStyleCast: false
+#SpaceAfterLogicalNot: false
+SpaceAfterTemplateKeyword: false
+SpaceBeforeAssignmentOperators: true
+SpaceBeforeCpp11BracedList: false
+SpaceBeforeCtorInitializerColon: true
+SpaceBeforeInheritanceColon: true
+SpaceBeforeParens: ControlStatements
+SpaceBeforeRangeBasedForLoopColon: true
+SpaceInEmptyParentheses: false
+SpacesBeforeTrailingComments: 1
+SpacesInAngles: false
+SpacesInCStyleCastParentheses: false
+SpacesInContainerLiterals: false
+SpacesInParentheses: false
+SpacesInSquareBrackets: false
+Standard: Cpp11
+TabWidth: 4
+UseTab: Never

.editorconfig

@@ -0,0 +1,13 @@
+root = true
+
+[*]
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[{*.cpp,*.c,*.hpp,*.h,*.cs}]
+indent_style = space
+indent_size = 4
+
+[*.json]
+indent_style = space
+indent_size = 2

.gitattributes

@@ -0,0 +1,63 @@
+###############################################################################
+# Set default behavior to automatically normalize line endings.
+###############################################################################
+* -text
+
+###############################################################################
+# Set default behavior for command prompt diff.
+#
+# This is need for earlier builds of msysgit that does not have it on by
+# default for csharp files.
+# Note: This is only used by command line
+###############################################################################
+#*.cs     diff=csharp
+
+###############################################################################
+# Set the merge driver for project and solution files
+#
+# Merging from the command prompt will add diff markers to the files if there
+# are conflicts (Merging from VS is not affected by the settings below, in VS
+# the diff markers are never inserted). Diff markers may cause the following 
+# file extensions to fail to load in VS. An alternative would be to treat
+# these files as binary and thus will always conflict and require user
+# intervention with every merge. To do so, just uncomment the entries below
+###############################################################################
+#*.sln       merge=binary
+#*.csproj    merge=binary
+#*.vbproj    merge=binary
+#*.vcxproj   merge=binary
+#*.vcproj    merge=binary
+#*.dbproj    merge=binary
+#*.fsproj    merge=binary
+#*.lsproj    merge=binary
+#*.wixproj   merge=binary
+#*.modelproj merge=binary
+#*.sqlproj   merge=binary
+#*.wwaproj   merge=binary
+
+###############################################################################
+# behavior for image files
+#
+# image files are treated as binary by default.
+###############################################################################
+#*.jpg   binary
+#*.png   binary
+#*.gif   binary
+
+###############################################################################
+# diff behavior for common document formats
+# 
+# Convert binary document formats to text before diffing them. This feature
+# is only available from the command line. Turn it on by uncommenting the 
+# entries below.
+###############################################################################
+#*.doc   diff=astextplain
+#*.DOC   diff=astextplain
+#*.docx  diff=astextplain
+#*.DOCX  diff=astextplain
+#*.dot   diff=astextplain
+#*.DOT   diff=astextplain
+#*.pdf   diff=astextplain
+#*.PDF   diff=astextplain
+#*.rtf   diff=astextplain
+#*.RTF   diff=astextplain

.github/ISSUE_TEMPLATE/Bug_Report.md

@@ -0,0 +1,52 @@
+---
+name: Bug report 🐛
+about: Report errors or unexpected behavior
+title: "Bug Report (IF I DO NOT CHANGE THIS THE ISSUE WILL BE AUTO-CLOSED)"
+labels: ''
+assignees: ''
+
+---
+
+<!-- 
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
+2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
+3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
+5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.
+
+All good? Then proceed!
+-->
+
+<!--
+This bug tracker is monitored by Windows Terminal development team and other technical folks.
+
+**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
+Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.
+
+Please use this form and describe your issue, concisely but precisely, with as much detail as possible.
+
+-->
+
+# Environment
+
+```none
+Windows build number: [run "ver" at a command prompt]
+Windows Terminal version (if applicable):
+
+Any other software?
+```
+
+# Steps to reproduce
+
+<!-- A description of how to trigger this bug. -->
+
+# Expected behavior
+
+<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->
+
+# Actual behavior
+
+<!-- What's actually happening? -->

.github/ISSUE_TEMPLATE/Documentation_Issue.md

@@ -0,0 +1,10 @@
+---
+name: Documentation Issue 📚
+about: Report issues in our documentation
+title: "Documentation Issue"
+labels: Issue-Docs
+assignees: ''
+
+---
+
+<!-- Briefly describe which document needs to be corrected and why. -->

.github/ISSUE_TEMPLATE/Feature_Request.md

@@ -0,0 +1,34 @@
+---
+name: Feature Request/Idea 🚀
+about: Suggest a new feature or improvement (this does not mean you have to implement it)
+title: "Feature Request"
+labels: Issue-Feature
+assignees: ''
+
+---
+
+<!-- 
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
+2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
+3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
+5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.
+
+All good? Then proceed!
+-->
+
+# Summary of the new feature/enhancement
+
+<!-- 
+A clear and concise description of what the problem is that the new feature would solve.
+Describe why and how a user would use this new functionality (if applicable).
+-->
+
+# Proposed technical implementation details (optional)
+
+<!-- 
+A clear and concise description of what you want to happen.
+-->

.github/ISSUE_TEMPLATE/Guidance_Issue.md

@@ -0,0 +1,10 @@
+---
+name: Community Guidance Request ✨
+about: Suggest somewhere the Windows Terminal Team needs to provide community guidance through new documentation or process.
+title: "Guidance"
+labels: Issue-Docs
+assignees: 'bitcrazed'
+
+---
+
+<!-- What needs to change? Who is responsible for it? Why is it an open question? -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,19 @@
+<!-- Enter a brief description/summary of your PR here. What does it fix/what does it change/how was it tested (even manually, if necessary)? -->
+## Summary of the Pull Request
+
+<!-- Other than the issue solved, is this relevant to any other issues/existing PRs? --> 
+## References
+
+<!-- Please review the items on the PR checklist before submitting-->
+## PR Checklist
+* [ ] Closes #xxx
+* [ ] CLA signed. If not, go over [here](https://cla.opensource.microsoft.com/microsoft/Terminal) and sign the CLA
+* [ ] Tests added/passed
+* [ ] Requires documentation to be updated
+* [ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx
+
+<!-- Provide a more detailed description of the PR, other things fixed or any additional comments/features here -->
+## Detailed Description of the Pull Request / Additional comments
+
+<!-- Describe how you validated the behavior. Add automated tests wherever possible, but list manual validation steps taken as well -->
+## Validation Steps Performed

.gitignore

@@ -1,253 +1,281 @@
-## Ignore Visual Studio temporary files, build results, and
-## files generated by popular Visual Studio add-ons.
-
-# User-specific files
-*.suo
-*.user
-*.userosscache
-*.sln.docstates
-
-# User-specific files (MonoDevelop/Xamarin Studio)
-*.userprefs
-
-# Build results
-[Dd]ebug/
-[Dd]ebugPublic/
-[Rr]elease/
-[Rr]eleases/
-x64/
-x86/
-bld/
-[Bb]in/
-[Oo]bj/
-[Ll]og/
-
-# Visual Studio 2015 cache/options directory
-.vs/
-# Uncomment if you have tasks that create the project's static files in wwwroot
-#wwwroot/
-
-# MSTest test Results
-[Tt]est[Rr]esult*/
-[Bb]uild[Ll]og.*
-
-# NUNIT
-*.VisualState.xml
-TestResult.xml
-
-# Build Results of an ATL Project
-[Dd]ebugPS/
-[Rr]eleasePS/
-dlldata.c
-
-# DNX
-project.lock.json
-artifacts/
-
-*_i.c
-*_p.c
-*_i.h
-*.ilk
-*.meta
-*.obj
-*.pch
-*.pdb
-*.pgc
-*.pgd
-*.rsp
-*.sbr
-*.tlb
-*.tli
-*.tlh
-*.tmp
-*.tmp_proj
-*.log
-*.vspscc
-*.vssscc
-.builds
-*.pidb
-*.svclog
-*.scc
-
-# Chutzpah Test files
-_Chutzpah*
-
-# Visual C++ cache files
-ipch/
-*.aps
-*.ncb
-*.opendb
-*.opensdf
-*.sdf
-*.cachefile
-*.VC.db
-*.VC.VC.opendb
-
-# Visual Studio profiler
-*.psess
-*.vsp
-*.vspx
-*.sap
-
-# TFS 2012 Local Workspace
-$tf/
-
-# Guidance Automation Toolkit
-*.gpState
-
-# ReSharper is a .NET coding add-in
-_ReSharper*/
-*.[Rr]e[Ss]harper
-*.DotSettings.user
-
-# JustCode is a .NET coding add-in
-.JustCode
-
-# TeamCity is a build add-in
-_TeamCity*
-
-# DotCover is a Code Coverage Tool
-*.dotCover
-
-# NCrunch
-_NCrunch_*
-.*crunch*.local.xml
-nCrunchTemp_*
-
-# MightyMoose
-*.mm.*
-AutoTest.Net/
-
-# Web workbench (sass)
-.sass-cache/
-
-# Installshield output folder
-[Ee]xpress/
-
-# DocProject is a documentation generator add-in
-DocProject/buildhelp/
-DocProject/Help/*.HxT
-DocProject/Help/*.HxC
-DocProject/Help/*.hhc
-DocProject/Help/*.hhk
-DocProject/Help/*.hhp
-DocProject/Help/Html2
-DocProject/Help/html
-
-# Click-Once directory
-publish/
-
-# Publish Web Output
-*.[Pp]ublish.xml
-*.azurePubxml
-# TODO: Comment the next line if you want to checkin your web deploy settings
-# but database connection strings (with potential passwords) will be unencrypted
-*.pubxml
-*.publishproj
-
-# Microsoft Azure Web App publish settings. Comment the next line if you want to
-# checkin your Azure Web App publish settings, but sensitive information contained
-# in these scripts will be unencrypted
-PublishScripts/
-
-# NuGet Packages
-*.nupkg
-# The packages folder can be ignored because of Package Restore
-**/packages/*
-# except build/, which is used as an MSBuild target.
-!**/packages/build/
-# Uncomment if necessary however generally it will be regenerated when needed
-#!**/packages/repositories.config
-# NuGet v3's project.json files produces more ignoreable files
-*.nuget.props
-*.nuget.targets
-
-# Microsoft Azure Build Output
-csx/
-*.build.csdef
-
-# Microsoft Azure Emulator
-ecf/
-rcf/
-
-# Windows Store app package directories and files
-AppPackages/
-BundleArtifacts/
-Package.StoreAssociation.xml
-_pkginfo.txt
-
-# Visual Studio cache files
-# files ending in .cache can be ignored
-*.[Cc]ache
-# but keep track of directories ending in .cache
-!*.[Cc]ache/
-
-# Others
-ClientBin/
-~$*
-*~
-*.dbmdl
-*.dbproj.schemaview
-*.pfx
-*.publishsettings
-node_modules/
-orleans.codegen.cs
-
-# Since there are multiple workflows, uncomment next line to ignore bower_components
-# (https://github.com/github/gitignore/pull/1529#issuecomment-104372622)
-#bower_components/
-
-# RIA/Silverlight projects
-Generated_Code/
-
-# Backup & report files from converting an old project file
-# to a newer Visual Studio version. Backup files are not needed,
-# because we have git ;-)
-_UpgradeReport_Files/
-Backup*/
-UpgradeLog*.XML
-UpgradeLog*.htm
-
-# SQL Server files
-*.mdf
-*.ldf
-
-# Business Intelligence projects
-*.rdl.data
-*.bim.layout
-*.bim_*.settings
-
-# Microsoft Fakes
-FakesAssemblies/
-
-# GhostDoc plugin setting file
-*.GhostDoc.xml
-
-# Node.js Tools for Visual Studio
-.ntvs_analysis.dat
-
-# Visual Studio 6 build log
-*.plg
-
-# Visual Studio 6 workspace options file
-*.opt
-
-# Visual Studio LightSwitch build output
-**/*.HTMLClient/GeneratedArtifacts
-**/*.DesktopClient/GeneratedArtifacts
-**/*.DesktopClient/ModelManifest.xml
-**/*.Server/GeneratedArtifacts
-**/*.Server/ModelManifest.xml
-_Pvt_Extensions
-
-# Paket dependency manager
-.paket/paket.exe
-paket-files/
-
-# FAKE - F# Make
-.fake/
-
-# JetBrains Rider
-.idea/
-*.sln.iml
-*.exe
+## Ignore Visual Studio temporary files, build results, and
+## files generated by popular Visual Studio add-ons.
+
+# User-specific files
+*.suo
+*.user
+*.userosscache
+*.sln.docstates
+
+# User-specific files (MonoDevelop/Xamarin Studio)
+*.userprefs
+
+# Build results
+[Dd]ebug/
+[Dd]ebugPublic/
+[Rr]elease/
+[Rr]eleases/
+x64/
+x86/
+ARM64/
+bld/
+[Bb]in/
+[Oo]bj/
+[Ll]og/
+objfre/
+objchk/
+
+# Visual Studio 2015 cache/options directory
+.vs/
+
+# Visual Studio Code cache/options directory
+.vscode/
+
+# MSTest test Results
+[Tt]est[Rr]esult*/
+[Bb]uild[Ll]og.*
+
+# NUNIT
+*.VisualState.xml
+TestResult.xml
+
+# Build Results of an ATL Project
+[Dd]ebugPS/
+[Rr]eleasePS/
+dlldata.c
+
+# DNX
+project.lock.json
+artifacts/
+
+*_i.c
+*_p.c
+*_i.h
+*.ilk
+*.meta
+*.obj
+*.pch
+*.pdb
+*.pgc
+*.pgd
+*.rsp
+*.sbr
+*.tlb
+*.tli
+*.tlh
+*.tmp
+*.tmp_proj
+*.log
+*.vspscc
+*.vssscc
+.builds
+*.pidb
+*.svclog
+*.scc
+
+# Chutzpah Test files
+_Chutzpah*
+
+# Visual C++ cache files
+ipch/
+*.aps
+*.ncb
+*.opendb
+*.opensdf
+*.sdf
+*.cachefile
+*.VC.db
+*.VC.VC.opendb
+
+# Visual Studio profiler
+*.psess
+*.vsp
+*.vspx
+*.sap
+
+# TFS 2012 Local Workspace
+$tf/
+
+# Guidance Automation Toolkit
+*.gpState
+
+# ReSharper is a .NET coding add-in
+_ReSharper*/
+*.[Rr]e[Ss]harper
+*.DotSettings.user
+
+# JustCode is a .NET coding add-in
+.JustCode
+
+# TeamCity is a build add-in
+_TeamCity*
+
+# DotCover is a Code Coverage Tool
+*.dotCover
+
+# NCrunch
+_NCrunch_*
+.*crunch*.local.xml
+nCrunchTemp_*
+
+# MightyMoose
+*.mm.*
+AutoTest.Net/
+
+# Web workbench (sass)
+.sass-cache/
+
+# Installshield output folder
+[Ee]xpress/
+
+# DocProject is a documentation generator add-in
+DocProject/buildhelp/
+DocProject/Help/*.HxT
+DocProject/Help/*.HxC
+DocProject/Help/*.hhc
+DocProject/Help/*.hhk
+DocProject/Help/*.hhp
+DocProject/Help/Html2
+DocProject/Help/html
+
+# Click-Once directory
+publish/
+
+# Publish Web Output
+*.[Pp]ublish.xml
+*.azurePubxml
+# TODO: Comment the next line if you want to checkin your web deploy settings
+# but database connection strings (with potential passwords) will be unencrypted
+*.pubxml
+*.publishproj
+
+# Microsoft Azure Web App publish settings. Comment the next line if you want to
+# checkin your Azure Web App publish settings, but sensitive information contained
+# in these scripts will be unencrypted
+PublishScripts/
+
+# NuGet Packages
+*.nupkg
+# The packages folder can be ignored because of Package Restore
+**/packages/*
+# except build/, which is used as an MSBuild target.
+!**/packages/build/
+# Uncomment if necessary however generally it will be regenerated when needed
+#!**/packages/repositories.config
+# NuGet v3's project.json files produces more ignoreable files
+*.nuget.props
+*.nuget.targets
+
+# Microsoft Azure Build Output
+csx/
+*.build.csdef
+
+# Microsoft Azure Emulator
+ecf/
+rcf/
+
+# Windows Store app package directories and files
+AppPackages/
+BundleArtifacts/
+Package.StoreAssociation.xml
+_pkginfo.txt
+
+# Visual Studio cache files
+# files ending in .cache can be ignored
+*.[Cc]ache
+# but keep track of directories ending in .cache
+!*.[Cc]ache/
+
+# Others
+ClientBin/
+[Ss]tyle[Cc]op.*
+~$*
+*~
+*.dbmdl
+*.dbproj.schemaview
+*.pfx
+*.publishsettings
+node_modules/
+orleans.codegen.cs
+
+# RIA/Silverlight projects
+Generated_Code/
+
+# Backup & report files from converting an old project file
+# to a newer Visual Studio version. Backup files are not needed,
+# because we have git ;-)
+_UpgradeReport_Files/
+Backup*/
+UpgradeLog*.XML
+UpgradeLog*.htm
+
+# SQL Server files
+*.mdf
+*.ldf
+
+# Business Intelligence projects
+*.rdl.data
+*.bim.layout
+*.bim_*.settings
+
+# Microsoft Fakes
+FakesAssemblies/
+
+# Node.js Tools for Visual Studio
+.ntvs_analysis.dat
+
+# Visual Studio 6 build log
+*.plg
+
+# Visual Studio 6 workspace options file
+*.opt
+
+# Visual Studio LightSwitch build output
+**/*.HTMLClient/GeneratedArtifacts
+**/*.DesktopClient/GeneratedArtifacts
+**/*.DesktopClient/ModelManifest.xml
+**/*.Server/GeneratedArtifacts
+**/*.Server/ModelManifest.xml
+_Pvt_Extensions
+
+# Paket dependency manager
+.paket/paket.exe
+paket-files/
+
+# FAKE - F# Make
+.fake/
+
+# JetBrains Rider
+.idea/
+*.sln.iml
+*.exe
+
+# Windows Build System files
+build*.dbb
+build*.err
+build*.evt
+build*.log
+build*.prf
+build*.trc
+build*.rec
+build*.wrn
+build*.metadata
+
+# .razzlerc.cmd file - used by dev environment
+tools/.razzlerc.*
+# .PowershellModules - if one needs a powershell module dependency, one
+# can save it here. used by tools/OpenConsole.psm1
+.PowershellModules
+# message compiler output
+MSG*.bin
+/*.exe
+
+# python
+*.pyc
+
+**/Generated Files/
+**/Merged/*
+**/Unmerged/*
+profiles.json
+*.metaproj
+*.swp

.gitmodules

@@ -0,0 +1,6 @@
+[submodule "dep/gsl"]
+	path = dep/gsl
+	url = https://github.com/microsoft/gsl
+[submodule "dep/wil"]
+	path = dep/wil
+	url = https://github.com/microsoft/wil

.nuget/packages.config

@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="utf-8"?>
+<packages>
+  <package id="vswhere" version="2.6.7" />
+</packages>

.vsconfig

@@ -0,0 +1,34 @@
+{
+  "version": "1.0",
+  "components": [
+    "Microsoft.VisualStudio.Component.CoreEditor",
+    "Microsoft.VisualStudio.Workload.CoreEditor",
+    "Microsoft.VisualStudio.Workload.Universal",
+    "Microsoft.VisualStudio.Workload.NativeDesktop",
+    "Microsoft.VisualStudio.Workload.ManagedDesktop",
+    "Microsoft.VisualStudio.Component.ManagedDesktop.Prerequisites",
+    "Microsoft.VisualStudio.Component.NuGet",
+    "Microsoft.VisualStudio.Component.Roslyn.Compiler",
+    "Microsoft.VisualStudio.Component.Roslyn.LanguageServices",
+    "Microsoft.Net.ComponentGroup.DevelopmentPrerequisites",
+    "Microsoft.Component.MSBuild",
+    "Microsoft.VisualStudio.Component.ManagedDesktop.Core",
+    "Microsoft.Net.Component.4.TargetingPack",
+    "Microsoft.Net.Component.4.5.TargetingPack",
+    "Microsoft.VisualStudio.Component.DiagnosticTools",
+    "Microsoft.VisualStudio.Component.Debugger.JustInTime",
+    "Microsoft.VisualStudio.Component.Windows10SDK.18362",
+    "Microsoft.VisualStudio.ComponentGroup.UWP.Support",
+    "Microsoft.VisualStudio.Component.VC.CoreIde",
+    "Microsoft.VisualStudio.ComponentGroup.NativeDesktop.Core",
+    "Microsoft.VisualStudio.Component.Graphics",
+    "Microsoft.VisualStudio.Component.VC.Redist.14.Latest",
+    "Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
+    "Microsoft.VisualStudio.Component.VC.Tools.ARM64",
+    "Microsoft.VisualStudio.Component.VC.v141.x86.x64",
+    "Microsoft.VisualStudio.Component.VC.v141.ARM64",
+    "Microsoft.VisualStudio.ComponentGroup.UWP.VC",
+    "Microsoft.VisualStudio.ComponentGroup.UWP.VC.v141",
+    "Microsoft.VisualStudio.Component.UWP.VC.ARM64"
+  ]
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,8 @@
+# Code of Conduct
+
+This project has adopted the [Microsoft Open Source Code of Conduct][conduct-code].
+For more information see the [Code of Conduct FAQ][conduct-FAQ] or contact [opencode@microsoft.com][conduct-email] with any additional questions or comments.
+
+[conduct-code]: https://opensource.microsoft.com/codeofconduct/
+[conduct-FAQ]: https://opensource.microsoft.com/codeofconduct/faq/
+[conduct-email]: mailto:opencode@microsoft.com

LICENSE

@@ -0,0 +1,21 @@
+Copyright (c) Microsoft Corporation. All rights reserved.
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

NOTICE.md

@@ -0,0 +1,49 @@
+# NOTICES AND INFORMATION
+Do Not Translate or Localize
+
+This software incorporates material from third parties. Microsoft makes certain
+open source code available at http://3rdpartysource.microsoft.com, or you may
+send a check or money order for US $5.00, including the product name, the open
+source component name, and version number, to:
+
+```
+Source Code Compliance Team
+Microsoft Corporation
+One Microsoft Way
+Redmond, WA 98052
+USA
+```
+
+Notwithstanding any other terms, you may reverse engineer this software to the
+extent required to debug changes to any libraries licensed under the GNU Lesser
+General Public License.
+
+## jsoncpp
+
+**Source**: https://github.com/open-source-parsers/jsoncpp
+
+### License
+
+```
+Copyright (c) 2007-2010 Baptiste Lepilleur and The JsonCpp Authors
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use, copy,
+modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
+BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
+ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```

NuGet.Config

@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <add key="NuGet.org" value="https://api.nuget.org/v3/index.json" />
+        <!-- Add repositories here to the list of available repositories -->
+        
+        <!-- Dependencies that we must carry because they're not on public nuget feeds right now. -->
+        <!--<add key="Static Package Dependencies" value="dep\packages" />-->
+        
+        <!-- Use our own NuGet Feed -->
+        <add key="Windows Terminal NuGet Feed" value="https://terminalnuget.blob.core.windows.net/feed/index.json" />
+        
+        <!-- Internal NuGet feeds that may not be accessible outside Microsoft corporate network -->
+        <!--<add key="TAEF - internal" value="https://microsoft.pkgs.visualstudio.com/DefaultCollection/_packaging/Taef/nuget/v3/index.json" />
+        <add key="OpenConsole - Internal" value="https://microsoft.pkgs.visualstudio.com/_packaging/OpenConsole/nuget/v3/index.json" />-->
+    </packageSources>
+    <config>
+        <add key="repositorypath" value=".\packages" />
+    </config>
+</configuration>

README.md

@@ -1,16 +1,177 @@
-# Console
+# Welcome\! 
+#### This repository contains the source code for:
 
-This is the Official Windows Console Github Repo. 
-Here you'll find assorted console tools in the `tools/` directory, such as the 
-  [ColorTool](https://github.com/Microsoft/Console/tree/master/tools/ColorTool).
+  * Windows Terminal
+  * The Windows console host (`conhost.exe`)
+  * Components shared between the two projects
+  * [ColorTool](https://github.com/Microsoft/Terminal/tree/master/src/tools/ColorTool)
+  * [Sample projects](https://github.com/Microsoft/Terminal/tree/master/samples) that show how to consume the Windows Console APIs
+  
+#### Other related repositories include:
+  * [Console API Documentation](https://github.com/MicrosoftDocs/Console-Docs)
 
-## Issues
-
-We will be monitoring and responding to issues as best we can. 
-Please attempt to avoid filing duplicates of open or closed items when possible.
-
-## Build Status
+### Build Status
 
 Project|Build Status
 ---|---
-tools/ColorTool|![](https://microsoft.visualstudio.com/_apis/public/build/definitions/c93e867a-8815-43c1-92c4-e7dd5404f1e1/17023/badge)
+Terminal|[![Build Status](https://dev.azure.com/ms/Terminal/_apis/build/status/Terminal%20CI?branchName=master)](https://dev.azure.com/ms/Terminal/_build?definitionId=136)
+ColorTool|![](https://microsoft.visualstudio.com/_apis/public/build/definitions/c93e867a-8815-43c1-92c4-e7dd5404f1e1/17023/badge)
+
+# Terminal & Console Overview
+
+Please take a few minutes to review the overview below before diving into the code:
+
+## Windows Terminal
+
+Windows Terminal is a new, modern, feature-rich, productive terminal application for command-line users. It includes many of the features most frequently requested by the Windows command-line community including support for tabs, rich text, globalization, configurability, theming & styling, and more.
+
+The Terminal will also need to meet our goals and measures to ensure it remains fast, and efficient, and doesn't consume vast amounts of memory or power.
+
+## The Windows console host
+
+The Windows console host, `conhost.exe`, is Windows' original command-line user experience. It implements Windows' command-line infrastructure, and is responsible for hosting the Windows Console API, input engine, rendering engine, and user preferences. The console host code in this repository is the actual source from which the `conhost.exe` in Windows itself is built.
+
+Console's primary goal is to remain backwards-compatible with existing console subsystem applications.
+
+Since assuming ownership of the Windows command-line in 2014, the team has added several new features to the Console, including window transparency, line-based selection, support for [ANSI / Virtual Terminal sequences](https://en.wikipedia.org/wiki/ANSI_escape_code), [24-bit color](https://devblogs.microsoft.com/commandline/24-bit-color-in-the-windows-console/), a [Pseudoconsole ("ConPTY")](https://devblogs.microsoft.com/commandline/windows-command-line-introducing-the-windows-pseudo-console-conpty/), and more.
+
+However, because the Console's primary goal is to maintain backward compatibility, we've been unable to add many of the features the community has been asking for, and which we've been wanting to add for the last several years--like tabs!
+
+These limitations led us to create the new Windows Terminal.
+
+## Shared Components
+
+While overhauling the Console, we've modernized its codebase considerably. We've cleanly separated logical entities into modules and classes, introduced some key extensibility points, replaced several old, home-grown collections and containers with safer, more efficient [STL containers](https://docs.microsoft.com/en-us/cpp/standard-library/stl-containers?view=vs-2019), and made the code simpler and safer by using Microsoft's [WIL](https://github.com/Microsoft/wil) header library.
+
+This overhaul work resulted in the creation of several key components that would be useful for any terminal implementation on Windows, including a new DirectWrite-based text layout and rendering engine, a text buffer capable of storing both UTF-16 and UTF-8, and a VT parser/emitter.
+
+## Building a new terminal
+
+When we started building the new terminal application, we explored and evaluated several approaches and technology stacks. We ultimately decided that our goals would be best met by sticking with C++ and sharing the aforementioned modernized components, placing them atop the modern Windows application platform and UI framework.
+
+Further, we realized that this would allow us to build the terminal's renderer and input stack as a reusable Windows UI control that others can incorporate into their applications.
+
+# FAQ
+
+## Where can I download Windows Terminal?
+
+### The Windows Terminal preview can be downloaded from the Microsoft Store.
+
+[https://www.microsoft.com/en-us/p/windows-terminal-preview/9n0dx20hk701](https://www.microsoft.com/en-us/p/windows-terminal-preview/9n0dx20hk701)
+
+## I built and ran the new Terminal, but I just get a blank window app!
+
+Make sure you are building for your computer's architecture. If your box has a 64-bit Windows, change your Solution Platform to x64.  
+To check your OS architecture go to Settings -> System -> About (or Win+X -> System) and under `Device specifications` check for the  `System type`.
+
+## I built and ran the new Terminal, but it looks just like the old console! What gives?
+
+Firstly, make sure you're building & deploying `CascadiaPackage` in Visual Studio, _NOT_ `Host.EXE`. `OpenConsole.exe` is just `conhost.exe`, the same old console you know and love. `opencon.cmd` will launch `openconsole.exe`, and unfortunately, `openterm.cmd` is currently broken.
+
+Secondly, try pressing <kbd>Ctrl</kbd> + <kbd>T</kbd>. The tabs are hidden when you only have one tab by default. In the future, the UI will be dramatically different, but for now, the defaults are _supposed_ to look like the console defaults.
+
+## I tried running WindowsTerminal.exe and it crashes!
+
+* Don't try to run it unpackaged. Make sure to build & deploy `CascadiaPackage` from Visual Studio, and run the Windows Terminal (Dev Build) app.
+* Make sure you're on the right version of Windows. You'll need to be on Insider's builds, or wait for the 1903 release, as the Windows Terminal **REQUIRES** features from the latest Windows release.
+
+# Getting Started
+
+## Debugging
+
+* To debug in VS, right click on CascadiaPackage (from VS Solution Explorer) and go to properties, in the Debug menu, change "Application process" and "Background task process" to "Native Only".
+
+## Contributing
+
+We are excited to work alongside you, our amazing community, to build and enhance Windows Terminal\!
+
+We ask that **before you start work on a feature that you would like to contribute**, please read our [Contributor's Guide](https://github.com/microsoft/terminal/blob/master/doc/contributing.md). We will be happy to work with you to figure out the best approach, provide guidance and mentorship throughout feature development, and help avoid any wasted or duplicate effort.
+
+> 👉 **Remember\!** Your contributions may be incorporated into future versions of Windows\! Because of this, all pull requests will be subject to the same level of scrutiny for quality, coding standards, performance, globalization, accessibility, and compatibility as those of our internal contributors.
+
+> ⚠ **Note**: The Command-Line Team is actively working out of this repository and will be periodically re-structuring the code to make it easier to comprehend, navigate, build, test, and contribute to, so **DO expect significant changes to code layout on a regular basis**.
+
+## Documentation
+
+All documentation is located in the `./doc` folder. If you would like to contribute to the documentation, please submit a pull request.
+
+## Communicating with the Team
+
+The easiest way to communicate with the team is via GitHub issues. Please file new issues, feature requests and suggestions, but **DO search for similar open/closed pre-existing issues before you do**.
+
+Please help us keep this repository clean, inclusive, and fun\! We will not tolerate any abusive, rude, disrespectful or inappropriate behavior. Read our [Code of Conduct](https://opensource.microsoft.com/codeofconduct/) for more details.
+
+If you would like to ask a question that you feel doesn't warrant an issue (yet), please reach out to us via Twitter:
+
+  * Rich Turner, Program Manager: [@richturn\_ms](https://twitter.com/richturn_ms)
+
+  * Dustin Howett, Engineering Lead: [@dhowett](https://twitter.com/DHowett)
+  
+  * Michael Niksa, Senior Developer: [@michaelniksa](https://twitter.com/MichaelNiksa)
+
+  * Kayla Cinnamon, Program Manager (especially for UX issues): [@cinnamon\_msft](https://twitter.com/cinnamon_msft)
+
+# Developer Guidance
+
+## Build Prerequisites
+
+* You must be running Windows 1903 (build >= 10.0.18362.0) or above in order to run Windows Terminal.
+* You must have the [1903 SDK](https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk) (build 10.0.18362.0) installed.
+* You must have at least [VS 2019](https://visualstudio.microsoft.com/downloads/) installed.
+* You must install the following Workloads via the VS Installer. Opening the solution will [prompt you to install missing components automatically](https://devblogs.microsoft.com/setup/configure-visual-studio-across-your-organization-with-vsconfig/).
+  - Desktop Development with C++
+  - Universal Windows Platform Development
+  - **The following Individual Components**
+     - C++ (v142) Universal Windows Platform Tools
+
+* You must also [enable Developer Mode in the Windows Settings app](https://docs.microsoft.com/en-us/windows/uwp/get-started/enable-your-device-for-development) to locally install and run the Terminal app.
+
+
+## Building the Code
+
+This repository uses [git submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules) for some of its dependencies. To make sure submodules are restored or updated, be sure to run the following prior to building:
+
+```shell
+git submodule update --init --recursive
+```
+
+OpenConsole.sln may be built from within Visual Studio or from the command-line using MSBuild. To build from the command line, find your shell below.
+
+### PowerShell
+
+```powershell
+Import-Module .\tools\OpenConsole.psm1
+Set-MsBuildDevEnvironment
+Invoke-OpenConsoleBuild
+```
+
+### CMD
+
+```shell
+.\tools\razzle.cmd
+bcz
+```
+
+We've provided a set of convenience scripts as well as [README](./tools/README.md) in the **/tools** directory to help automate the process of building and running tests.
+
+## Coding Guidance
+
+Please review these brief docs below relating to our coding standards etc.
+
+> 👉 If you find something missing from these docs, feel free to contribute to any of our documentation files anywhere in the repository (or make some new ones\!)
+
+This is a work in progress as we learn what we'll need to provide people in order to be effective contributors to our project.
+
+  - [Coding Style](https://github.com/Microsoft/Terminal/blob/master/doc/STYLE.md)
+  - [Code Organization](https://github.com/Microsoft/Terminal/blob/master/doc/ORGANIZATION.md)
+  - [Exceptions in our legacy codebase](https://github.com/Microsoft/Terminal/blob/master/doc/EXCEPTIONS.md)
+  - [Helpful smart pointers and macros for interfacing with Windows in WIL](https://github.com/Microsoft/Terminal/blob/master/doc/WIL.md)
+
+# Code of Conduct
+
+This project has adopted the [Microsoft Open Source Code of Conduct][conduct-code].
+For more information see the [Code of Conduct FAQ][conduct-FAQ] or contact [opencode@microsoft.com][conduct-email] with any additional questions or comments.
+
+[conduct-code]: https://opensource.microsoft.com/codeofconduct/
+[conduct-FAQ]: https://opensource.microsoft.com/codeofconduct/faq/
+[conduct-email]: mailto:opencode@microsoft.com

build/.nuget/packages.config

@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="utf-8"?>
+<packages>
+  <package id="Taef.TestAdapter" version="10.30.180808002" />
+</packages>

build/config/NuGet.config

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <add key="TAEF Internal" value="https://microsoft.pkgs.visualstudio.com/_packaging/Taef/nuget/v3/index.json" />
+    </packageSources>
+    <config>
+        <add key="repositorypath" value="..\..\packages" />
+    </config>
+</configuration>

build/config/SignConfig.WindowsTerminal.xml

@@ -0,0 +1,5 @@
+<SignConfigXML>
+  <job platform="" configuration="" certSubject="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" jobname="EngFunSimpleSign" approvers="">
+   <file src="__INPATHROOT__\Microsoft.WindowsTerminal_8wekyb3d8bbwe.msixbundle" signType="136020001" dest="__OUTPATHROOT__\Microsoft.WindowsTerminal_8wekyb3d8bbwe.msixbundle" /> 
+  </job>
+</SignConfigXML>

build/pipelines/ci.yml

@@ -0,0 +1,38 @@
+trigger:
+  batch: true
+  branches:
+    include:
+      - master
+  paths:
+    exclude:
+      - doc/*
+      - samples/*
+      - tools/*
+
+pr:
+  branches:
+    include:
+      - master
+
+#     0.0.yyMM.dd##
+#     0.0.1904.0900
+name: 0.0.$(Date:yyMM).$(Date:dd)$(Rev:rr)
+
+jobs:
+  - template: ./templates/build-console-audit-job.yml
+    parameters:
+      platform: x64
+
+  - template: ./templates/build-console-ci.yml
+    parameters:
+      platform: x64
+
+  - template: ./templates/build-console-ci.yml
+    parameters:
+      platform: x86
+
+  - template: ./templates/build-console-ci.yml
+    parameters:
+      platform: ARM64
+
+  - template: ./templates/check-formatting.yml

build/pipelines/release.yml

@@ -0,0 +1,40 @@
+trigger: none
+pr: none
+
+variables:
+  baseYearForVersioning: 2019 # Used by build-console-int
+  versionMajor: 0
+  versionMinor: 1
+
+# When we move off PackageES for Versioning, we'll need to switch
+# name to this format. For now, though, we need to use DayOfYear.Rev
+# to unique our builds, as mandated by PackageES's Setup task.
+# name: '$(versionMajor).$(versionMinor).$(DayOfYear)$(Rev:r).0'
+#
+# Build name/version number above must end with .0 to make the
+# store publication machinery happy.
+name: 'Terminal_$(date:yyMM).$(date:dd)$(rev:rrr)'
+
+jobs:
+  - template: ./templates/build-console-audit-job.yml
+    parameters:
+      platform: x64
+
+  - template: ./templates/build-console-int.yml
+    parameters:
+      platform: x64
+      additionalBuildArguments: /p:WindowsTerminalReleaseBuild=true
+
+  - template: ./templates/build-console-int.yml
+    parameters:
+      platform: x86
+      additionalBuildArguments: /p:WindowsTerminalReleaseBuild=true
+
+  - template: ./templates/build-console-int.yml
+    parameters:
+      platform: arm64
+      additionalBuildArguments: /p:WindowsTerminalReleaseBuild=true
+
+  - template: ./templates/check-formatting.yml
+
+  - template: ./templates/release-sign-and-bundle.yml

build/pipelines/templates/build-console-audit-job.yml

@@ -0,0 +1,53 @@
+parameters:
+  platform: ''
+  additionalBuildArguments: ''
+
+jobs:
+- job: Build${{ parameters.platform }}AuditMode
+  displayName: Static Analysis Build ${{ parameters.platform }}
+  variables:
+    BuildConfiguration: AuditMode
+    BuildPlatform: ${{ parameters.platform }}
+  pool: { vmImage: windows-2019 }
+
+  steps:
+  - checkout: self
+    submodules: true
+    clean: true
+
+  - task: NuGetToolInstaller@0
+    displayName: Ensure NuGet 4.8.1
+    inputs:
+      versionSpec: 4.8.1
+
+  # In the Microsoft Azure DevOps tenant, NuGetCommand is ambiguous.
+  # This should be `task: NuGetCommand@2`
+  - task: 333b11bd-d341-40d9-afcf-b32d5ce6f23b@2
+    displayName: Restore NuGet packages
+    inputs:
+      command: restore
+      feedsToUse: config
+      configPath: NuGet.config
+      restoreSolution: OpenConsole.sln
+      restoreDirectory: '$(Build.SourcesDirectory)\packages'
+
+  - task: 333b11bd-d341-40d9-afcf-b32d5ce6f23b@2
+    displayName: 'NuGet restore packages for CI'
+    inputs:
+      command: restore
+      restoreSolution: build/.nuget/packages.config
+      feedsToUse: config
+      externalFeedCredentials: 'TAEF NuGet Feed'
+      nugetConfigPath: build/config/NuGet.config
+      restoreDirectory: '$(Build.SourcesDirectory)/packages'
+
+  - task: VSBuild@1
+    displayName: 'Build solution **\OpenConsole.sln'
+    inputs:
+      solution: '**\OpenConsole.sln'
+      vsVersion: 16.0
+      platform: '$(BuildPlatform)'
+      configuration: '$(BuildConfiguration)'
+      msbuildArgs: ${{ parameters.additionalBuildArguments }}
+      clean: true
+      maximumCpuCount: true

build/pipelines/templates/build-console-ci.yml

@@ -0,0 +1,17 @@
+parameters:
+  configuration: 'Release'
+  platform: ''
+  additionalBuildArguments: ''
+
+jobs:
+- job: Build${{ parameters.platform }}${{ parameters.configuration }}
+  displayName: Build ${{ parameters.platform }} ${{ parameters.configuration }}
+  variables:
+    BuildConfiguration: ${{ parameters.configuration }}
+    BuildPlatform: ${{ parameters.platform }}
+  pool: { vmImage: windows-2019 }
+
+  steps:
+  - template: build-console-steps.yml
+    parameters:
+      additionalBuildArguments: ${{ parameters.additionalBuildArguments }}

build/pipelines/templates/build-console-int.yml

@@ -0,0 +1,30 @@
+parameters:
+  configuration: 'Release'
+  platform: ''
+  additionalBuildArguments: ''
+
+jobs:
+- job: Build${{ parameters.platform }}${{ parameters.configuration }}
+  displayName: Build ${{ parameters.platform }} ${{ parameters.configuration }}
+  variables:
+    BuildConfiguration: ${{ parameters.configuration }}
+    BuildPlatform: ${{ parameters.platform }}
+
+  pool:
+    name: Package ES Lab E
+    demands:
+    - msbuild
+    - visualstudio
+    - vstest
+
+  steps:
+  - task: PkgESSetupBuild@10
+    displayName: 'Package ES - Setup Build'
+    inputs:
+      useDfs: false
+      productName: WindowsTerminal
+      disableOutputRedirect: true
+
+  - template: build-console-steps.yml
+    parameters:
+      additionalBuildArguments: "/p:XesUseOneStoreVersioning=true;XesBaseYearForStoreVersion=$(baseYearForVersioning) ${{ parameters.additionalBuildArguments }}"

build/pipelines/templates/build-console-steps.yml

@@ -0,0 +1,95 @@
+parameters:
+  additionalBuildArguments: ''
+
+steps:
+- checkout: self
+  submodules: true
+  clean: true
+
+- task: NuGetToolInstaller@0
+  displayName: Ensure NuGet 4.8.1
+  inputs:
+    versionSpec: 4.8.1
+
+- task: VisualStudioTestPlatformInstaller@1
+  displayName: Ensure VSTest Platform
+
+# In the Microsoft Azure DevOps tenant, NuGetCommand is ambiguous.
+# This should be `task: NuGetCommand@2`
+- task: 333b11bd-d341-40d9-afcf-b32d5ce6f23b@2
+  displayName: Restore NuGet packages
+  inputs:
+    command: restore
+    feedsToUse: config
+    configPath: NuGet.config
+    restoreSolution: OpenConsole.sln
+    restoreDirectory: '$(Build.SourcesDirectory)\packages'
+
+- task: 333b11bd-d341-40d9-afcf-b32d5ce6f23b@2
+  displayName: 'NuGet restore packages for CI'
+  inputs:
+    command: restore
+    restoreSolution: build/.nuget/packages.config
+    feedsToUse: config
+    externalFeedCredentials: 'TAEF NuGet Feed'
+    nugetConfigPath: build/config/NuGet.config
+    restoreDirectory: '$(Build.SourcesDirectory)/packages'
+
+- task: VSBuild@1
+  displayName: 'Build solution **\OpenConsole.sln'
+  inputs:
+    solution: '**\OpenConsole.sln'
+    vsVersion: 16.0
+    platform: '$(BuildPlatform)'
+    configuration: '$(BuildConfiguration)'
+    msbuildArgs: ${{ parameters.additionalBuildArguments }}
+    clean: true
+    maximumCpuCount: true
+
+- task: VSTest@2
+  displayName: 'Run Unit Tests'
+  inputs:
+    testAssemblyVer2: |
+      $(BUILD.SOURCESDIRECTORY)\**\*unit.test*.dll
+      !**\obj\**
+    runSettingsFile: '$(BUILD.SOURCESDIRECTORY)\src\unit.tests.$(BuildPlatform).runsettings'
+    codeCoverageEnabled: true
+    runInParallel: False
+    testRunTitle: 'Console Unit Tests'
+    platform: '$(BuildPlatform)'
+    configuration: '$(BuildConfiguration)'
+  condition: and(succeeded(), or(eq(variables['BuildPlatform'], 'x64'), eq(variables['BuildPlatform'], 'x86')))
+
+- task: VSTest@2
+  displayName: 'Run Feature Tests (x64 only)'
+  inputs:
+    testAssemblyVer2: |
+      $(BUILD.SOURCESDIRECTORY)\**\*feature.test*.dll
+      !**\obj\**
+    runSettingsFile: '$(BUILD.SOURCESDIRECTORY)\src\unit.tests.$(BuildPlatform).runsettings'
+    codeCoverageEnabled: true
+    runInParallel: False
+    testRunTitle: 'Console Feature Tests'
+    platform: '$(BuildPlatform)'
+    configuration: '$(BuildConfiguration)'
+  condition: and(succeeded(), eq(variables['BuildPlatform'], 'x64'))
+
+- task: CopyFiles@2
+  displayName: 'Copy *.appx/*.msix to Artifacts (Non-PR builds only)'
+  inputs:
+    Contents: |
+     **/*.appx
+     **/*.msix
+     **/*.appxsym
+     !**/Microsoft.VCLibs*.appx
+    TargetFolder: '$(Build.ArtifactStagingDirectory)/appx'
+    OverWrite: true
+    flattenFolders: true
+  condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'))
+
+- task: PublishBuildArtifacts@1
+  displayName: 'Publish Artifact (appx) (Non-PR builds only)'
+  inputs:
+    PathtoPublish: '$(Build.ArtifactStagingDirectory)/appx'
+    ArtifactName: 'appx-$(BuildConfiguration)'
+  condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'))

build/pipelines/templates/check-formatting.yml

@@ -0,0 +1,16 @@
+
+jobs:
+- job: CodeFormatCheck
+  displayName: Proper Code Formatting Check
+  pool: { vmImage: windows-2019 }
+
+  steps:
+  - checkout: self
+    submodules: false
+    clean: true
+
+  - task: PowerShell@2
+    displayName: 'Code Formattting Check'
+    inputs:
+      targetType: filePath
+      filePath: '.\build\scripts\Invoke-FormattingCheck.ps1'

build/pipelines/templates/release-sign-and-bundle.yml

@@ -0,0 +1,74 @@
+parameters:
+  configuration: 'Release'
+
+jobs:
+- job: SignDeploy${{ parameters.configuration }}
+  displayName: Sign and Deploy for ${{ parameters.configuration }}
+
+  dependsOn:
+    - Buildx64AuditMode
+    - Buildx64Release
+    - Buildx86Release
+    - Buildarm64Release
+    - CodeFormatCheck
+  condition: |
+    and
+    (
+      in(dependencies.Buildx64AuditMode.result, 'Succeeded', 'SucceededWithIssues', 'Skipped'),
+      in(dependencies.Buildx64Release.result,   'Succeeded', 'SucceededWithIssues', 'Skipped'),
+      in(dependencies.Buildx86Release.result,   'Succeeded', 'SucceededWithIssues', 'Skipped'),
+      in(dependencies.Buildarm64Release.result, 'Succeeded', 'SucceededWithIssues', 'Skipped'),
+      in(dependencies.CodeFormatCheck.result,   'Succeeded', 'SucceededWithIssues', 'Skipped')
+    )
+
+  variables:
+    BuildConfiguration: ${{ parameters.configuration }}
+    AppxProjectName: CascadiaPackage
+    AppxBundleName: Microsoft.WindowsTerminal_8wekyb3d8bbwe.msixbundle
+
+  pool:
+    name: Package ES Lab E
+
+  steps:
+  - checkout: self
+    clean: true
+
+  - task: PkgESSetupBuild@10
+    displayName: 'Package ES - Setup Build'
+    inputs:
+      useDfs: false
+      productName: WindowsTerminal
+      disableOutputRedirect: true
+
+  - task: ms.vss-governance-buildtask.governance-build-task-component-detection.ComponentGovernanceComponentDetection@0
+    displayName: 'Component Detection'
+
+  - task: DownloadBuildArtifacts@0
+    displayName: Download AppX artifacts
+    inputs:
+      artifactName: 'appx-$(BuildConfiguration)'
+      itemPattern: |
+        **/*.appx
+        **/*.msix
+      downloadPath: '$(Build.ArtifactStagingDirectory)\appx'
+
+  - task: PowerShell@2
+    displayName: 'Create $(AppxBundleName)'
+    inputs:
+      targetType: filePath
+      filePath: '.\build\scripts\Create-AppxBundle.ps1'
+      arguments: |
+        -InputPath "$(Build.ArtifactStagingDirectory)\appx" -ProjectName $(AppxProjectName) -BundleVersion 0.0.0.0 -OutputPath "$(Build.ArtifactStagingDirectory)\$(AppxBundleName)"
+
+  - task: PkgESCodeSign@10
+    displayName: 'Package ES - SignConfig.WindowsTerminal.xml'
+    inputs:
+      signConfigXml: 'build\config\SignConfig.WindowsTerminal.xml'
+      inPathRoot: '$(Build.ArtifactStagingDirectory)'
+      outPathRoot: '$(Build.ArtifactStagingDirectory)\signed'
+
+  - task: PublishBuildArtifacts@1
+    displayName: 'Publish Signed AppX'
+    inputs:
+      PathtoPublish: '$(Build.ArtifactStagingDirectory)\signed'
+      ArtifactName: 'appxbundle-signed-$(BuildConfiguration)'

build/scripts/Create-AppxBundle.ps1

@@ -0,0 +1,57 @@
+Param(
+    [Parameter(Mandatory,
+      HelpMessage="Base name for input .appx files")]
+    [string]
+    $ProjectName,
+
+    [Parameter(Mandatory,
+      HelpMessage="Appx Bundle Version")]
+    [version]
+    $BundleVersion,
+
+    [Parameter(Mandatory,
+      HelpMessage="Path under which to locate appx/msix files")]
+    [string]
+    $InputPath,
+
+    [Parameter(Mandatory,
+      HelpMessage="Output Path")]
+    [string]
+    $OutputPath,
+
+    [Parameter(HelpMessage="Path to makeappx.exe")]
+    [ValidateScript({Test-Path $_ -Type Leaf})]
+    [string]
+    $MakeAppxPath = "C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\MakeAppx.exe"
+)
+
+If ($null -Eq (Get-Item $MakeAppxPath -EA:SilentlyContinue)) {
+    Write-Error "Could not find MakeAppx.exe at `"$MakeAppxPath`".`nMake sure that -MakeAppxPath points to a valid SDK."
+    Exit 1
+}
+
+# Enumerates a set of appx files beginning with a project name
+# and generates a temporary file containing a bundle content map.
+Function Create-AppxBundleMapping {
+    Param(
+        [Parameter(Mandatory)]
+        [string]
+        $InputPath,
+
+        [Parameter(Mandatory)]
+        [string]
+        $ProjectName
+    )
+
+    $lines = @("[Files]")
+    Get-ChildItem -Path:$InputPath -Recurse -Filter:*$ProjectName* -Include *.appx, *.msix | % {
+        $lines += ("`"{0}`" `"{1}`"" -f ($_.FullName, $_.Name))
+    }
+    $outputFile = New-TemporaryFile
+    $lines | Out-File -Encoding:ASCII $outputFile
+    $outputFile
+}
+
+$NewMapping = Create-AppxBundleMapping -InputPath:$InputPath -ProjectName:$ProjectName
+
+& $MakeAppxPath bundle /v /bv $BundleVersion.ToString() /f $NewMapping.FullName /p $OutputPath

build/scripts/Invoke-FormattingCheck.ps1

@@ -0,0 +1,14 @@
+
+#.SYNOPSIS
+# Checks for code formatting errors. Will throw exception if any are found.
+function Invoke-CheckBadCodeFormatting() {
+    Import-Module ./tools/OpenConsole.psm1
+    Invoke-CodeFormat
+    # returns a non-zero exit code if there are any diffs in the tracked files in the repo
+    git diff-index --quiet HEAD --
+    if ($lastExitCode -eq 1) {
+        throw "code formatting bad, run Invoke-CodeFormat on branch"
+    }
+}
+
+Invoke-CheckBadCodeFormatting

common.openconsole.props

@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="utf-8"?>
+<Project DefaultTargets="Build" ToolsVersion="14.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+
+  <!--
+  This props file is a workaround for the fact that for wapproj projects,
+  the $(SolutionDir) is never evaluated correctly. So, instead we're using this
+  file to define $(OpenConsoleDir), which should be used in place of $(SolutionDir)
+   -->
+  <PropertyGroup Condition="'$(OpenConsoleDir)'==''">
+    <OpenConsoleDir>$(MSBuildThisFileDirectory)</OpenConsoleDir>
+  </PropertyGroup>
+
+</Project>

consolegit2gitfilters.json

@@ -0,0 +1,36 @@
+{
+  "PrefixFilters": [
+    "."
+  ],
+  "ContainsFilters": [
+    "/.",
+    "/.git/",
+    "/obj/",
+    "/bin/",
+    "/TestResults/",
+    "/packages/",
+    "/ipch/",
+    "/dep/",
+    "/.vs/",
+    "/build/",
+    "/src/cascadia/",
+    "/.nuget/",
+    "/.github/",
+    "/samples/"
+  ],
+  "SuffixFilters": [
+    ".dbb",
+    ".evt",
+    ".log",
+    ".metadata",
+    ".prf",
+    ".trc",
+    ".user",
+    ".tmp",
+    ".TMP",
+    ".db",
+    ".wrn",
+    ".rec",
+    ".err"
+  ]    
+}

dep/Console/conapi.h

@@ -0,0 +1,24 @@
+/*++
+Copyright (c) Microsoft Corporation
+
+Module Name:
+- conapi.h
+
+Abstract:
+- This module contains the internal structures and definitions used by the console server.
+
+Author:
+- Therese Stowell (ThereseS) 12-Nov-1990
+
+Revision History:
+--*/
+
+#pragma once
+// these should be in precomp but aren't being picked up...
+#include <unordered_map>
+#define STATUS_SHARING_VIOLATION         ((NTSTATUS)0xC0000043L)
+
+#include "conmsgl1.h"
+#include "conmsgl2.h"
+#include "conmsgl3.h"
+

dep/Console/condrv.h

@@ -0,0 +1,214 @@
+/*++
+
+Copyright (c) Microsoft Corporation. All rights reserved.
+
+Module Name:
+
+    condrv.h
+
+Abstract:
+
+    This module contains the declarations shared by the console driver and the
+    user-mode components that use it.
+
+Author:
+
+    Wedson Almeida Filho (wedsonaf) 24-Sep-2009
+
+Environment:
+
+    Kernel and user modes.
+
+--*/
+
+#pragma once
+
+#include "..\NT\ntioapi_x.h"
+
+//
+// Messages that can be received by servers, used in CD_IO_DESCRIPTOR::Function.
+//
+
+#define CONSOLE_IO_CONNECT        0x01
+#define CONSOLE_IO_DISCONNECT     0x02
+#define CONSOLE_IO_CREATE_OBJECT  0x03
+#define CONSOLE_IO_CLOSE_OBJECT   0x04
+#define CONSOLE_IO_RAW_WRITE      0x05
+#define CONSOLE_IO_RAW_READ       0x06
+#define CONSOLE_IO_USER_DEFINED   0x07
+#define CONSOLE_IO_RAW_FLUSH      0x08
+
+//
+// Header of all IOs submitted to a server.
+//
+
+typedef struct _CD_IO_DESCRIPTOR {
+    LUID Identifier;
+    ULONG_PTR Process;
+    ULONG_PTR Object;
+    ULONG Function;
+    ULONG InputSize;
+    ULONG OutputSize;
+    ULONG Reserved;
+} CD_IO_DESCRIPTOR, *PCD_IO_DESCRIPTOR;
+
+//
+// Types of objects, used in CREATE_OBJECT_INFORMATION::ObjectType.
+//
+
+#define CD_IO_OBJECT_TYPE_CURRENT_INPUT   0x01
+#define CD_IO_OBJECT_TYPE_CURRENT_OUTPUT  0x02
+#define CD_IO_OBJECT_TYPE_NEW_OUTPUT      0x03
+#define CD_IO_OBJECT_TYPE_GENERIC         0x04
+
+//
+// Payload of the CONSOLE_IO_CREATE_OBJECT io.
+//
+
+typedef struct _CD_CREATE_OBJECT_INFORMATION {
+    ULONG ObjectType;
+    ULONG ShareMode;
+    ACCESS_MASK DesiredAccess;
+} CD_CREATE_OBJECT_INFORMATION, *PCD_CREATE_OBJECT_INFORMATION;
+
+//
+// Create EA buffers.
+//
+
+#define CD_BROKER_EA_NAME "broker"
+#define CD_SERVER_EA_NAME "server"
+#define CD_ATTACH_EA_NAME "attach"
+
+typedef struct _CD_CREATE_SERVER {
+    HANDLE BrokerHandle;
+    LUID BrokerRequest;
+} CD_CREATE_SERVER, *PCD_CREATE_SERVER;
+
+typedef struct _CD_ATTACH_INFORMATION {
+    HANDLE ProcessId;
+} CD_ATTACH_INFORMATION, *PCD_ATTACH_INFORMATION;
+
+typedef struct _CD_ATTACH_INFORMATION64 {
+    PVOID64 ProcessId;
+} CD_ATTACH_INFORMATION64, *PCD_ATTACH_INFORMATION64;
+
+//
+// Information passed to the driver by a server when a connection is accepted.
+//
+
+typedef struct _CD_CONNECTION_INFORMATION {
+    ULONG_PTR Process;
+    ULONG_PTR Input;
+    ULONG_PTR Output;
+} CD_CONNECTION_INFORMATION, *PCD_CONNECTION_INFORMATION;
+
+//
+// Ioctls.
+//
+
+typedef struct _CD_IO_BUFFER {
+    ULONG Size;
+    PVOID Buffer;
+} CD_IO_BUFFER, *PCD_IO_BUFFER;
+
+typedef struct _CD_IO_BUFFER64 {
+    ULONG Size;
+    PVOID64 Buffer;
+} CD_IO_BUFFER64, *PCD_IO_BUFFER64;
+
+typedef struct _CD_USER_DEFINED_IO {
+    HANDLE Client;
+    ULONG InputCount;
+    ULONG OutputCount;
+    CD_IO_BUFFER Buffers[ANYSIZE_ARRAY];
+} CD_USER_DEFINED_IO, *PCD_USER_DEFINED_IO;
+
+typedef struct _CD_USER_DEFINED_IO64 {
+    PVOID64 Client;
+    ULONG InputCount;
+    ULONG OutputCount;
+    CD_IO_BUFFER64 Buffers[ANYSIZE_ARRAY];
+} CD_USER_DEFINED_IO64, *PCD_USER_DEFINED_IO64;
+
+typedef struct _CD_IO_BUFFER_DESCRIPTOR {
+    PVOID Data;
+    ULONG Size;
+    ULONG Offset;
+} CD_IO_BUFFER_DESCRIPTOR, *PCD_IO_BUFFER_DESCRIPTOR;
+
+typedef struct _CD_IO_COMPLETE {
+    LUID Identifier;
+    IO_STATUS_BLOCK IoStatus;
+    CD_IO_BUFFER_DESCRIPTOR Write;
+} CD_IO_COMPLETE, *PCD_IO_COMPLETE;
+
+typedef struct _CD_IO_OPERATION {
+    LUID Identifier;
+    CD_IO_BUFFER_DESCRIPTOR Buffer;
+} CD_IO_OPERATION, *PCD_IO_OPERATION;
+
+typedef struct _CD_IO_SERVER_INFORMATION {
+    HANDLE InputAvailableEvent;
+} CD_IO_SERVER_INFORMATION, *PCD_IO_SERVER_INFORMATION;
+
+typedef struct _CD_IO_DISPLAY_SIZE {
+    ULONG Width;
+    ULONG Height;
+} CD_IO_DISPLAY_SIZE, *PCD_IO_DISPLAY_SIZE;
+
+typedef struct _CD_IO_CHARACTER {
+    WCHAR Character; 
+    USHORT Atribute;
+} CD_IO_CHARACTER, *PCD_IO_CHARACTER;
+
+typedef struct _CD_IO_ROW_INFORMATION {
+    SHORT Index;
+    PCD_IO_CHARACTER Old;
+    PCD_IO_CHARACTER New;
+} CD_IO_ROW_INFORMATION, *PCD_IO_ROW_INFORMATION;
+
+typedef struct _CD_IO_CURSOR_INFORMATION {
+    USHORT Column;
+    USHORT Row;
+    ULONG Height;
+    BOOLEAN IsVisible;
+} CD_IO_CURSOR_INFORMATION, *PCD_IO_CURSOR_INFORMATION;
+
+#define IOCTL_CONDRV_READ_IO \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 1, METHOD_OUT_DIRECT, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_COMPLETE_IO \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 2, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_READ_INPUT \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 3, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_WRITE_OUTPUT \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 4, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_ISSUE_USER_IO \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 5, METHOD_OUT_DIRECT, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_DISCONNECT_PIPE \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 6, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_SET_SERVER_INFORMATION \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 7, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_GET_SERVER_PID \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 8, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_GET_DISPLAY_SIZE \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 9, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_UPDATE_DISPLAY \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 10, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_SET_CURSOR \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 11, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_ALLOW_VIA_UIACCESS \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 12, METHOD_NEITHER, FILE_ANY_ACCESS)
+
+#define IOCTL_CONDRV_LAUNCH_SERVER \
+    CTL_CODE(FILE_DEVICE_CONSOLE, 13, METHOD_NEITHER, FILE_ANY_ACCESS)

dep/Console/conmsgl1.h

@@ -0,0 +1,156 @@
+/*++
+
+Copyright (c) Microsoft Corporation. All rights reserved.
+
+Module Name:
+
+    conmsgl1.h
+
+Abstract:
+
+    This include file defines the layer 1 message formats used to communicate
+    between the client and server portions of the CONSOLE portion of the
+    Windows subsystem.
+
+Author:
+
+    Therese Stowell (thereses) 10-Nov-1990
+
+Revision History:
+
+    Wedson Almeida Filho (wedsonaf) 23-May-2010
+        Modified the messages for use with the console driver.
+
+--*/
+
+#pragma once
+
+#define CONSOLE_FIRST_API_NUMBER(Layer) \
+    (Layer << 24) \
+
+typedef struct _CONSOLE_SERVER_MSG {
+    ULONG IconId;
+    ULONG HotKey;
+    ULONG StartupFlags;
+    USHORT FillAttribute;
+    USHORT ShowWindow;
+    COORD ScreenBufferSize;
+    COORD WindowSize;
+    COORD WindowOrigin;
+    ULONG ProcessGroupId;
+    BOOLEAN ConsoleApp;
+    BOOLEAN WindowVisible;
+    USHORT TitleLength;
+    WCHAR Title[MAX_PATH + 1];
+    USHORT ApplicationNameLength;
+    WCHAR ApplicationName[128];
+    USHORT CurrentDirectoryLength;
+    WCHAR CurrentDirectory[MAX_PATH + 1];
+} CONSOLE_SERVER_MSG, *PCONSOLE_SERVER_MSG;
+
+typedef struct _CONSOLE_BROKER_DATA {
+    WCHAR DesktopName[MAX_PATH];
+} CONSOLE_BROKER_MSG, *PCONSOLE_BROKER_MSG;
+
+typedef struct _CONSOLE_GETCP_MSG {
+    OUT ULONG CodePage;
+    IN BOOLEAN Output;
+} CONSOLE_GETCP_MSG, *PCONSOLE_GETCP_MSG;
+
+typedef struct _CONSOLE_MODE_MSG {
+    IN OUT ULONG Mode;
+} CONSOLE_MODE_MSG, *PCONSOLE_MODE_MSG;
+
+typedef struct _CONSOLE_GETNUMBEROFINPUTEVENTS_MSG {
+    OUT ULONG ReadyEvents;
+} CONSOLE_GETNUMBEROFINPUTEVENTS_MSG, *PCONSOLE_GETNUMBEROFINPUTEVENTS_MSG;
+
+typedef struct _CONSOLE_GETCONSOLEINPUT_MSG {
+    OUT ULONG NumRecords;
+    IN USHORT Flags;
+    IN BOOLEAN Unicode;
+} CONSOLE_GETCONSOLEINPUT_MSG, *PCONSOLE_GETCONSOLEINPUT_MSG;
+
+typedef struct _CONSOLE_READCONSOLE_MSG {
+    IN BOOLEAN Unicode;
+    IN BOOLEAN ProcessControlZ;
+    IN USHORT ExeNameLength;
+    IN ULONG InitialNumBytes;
+    IN ULONG CtrlWakeupMask;
+    OUT ULONG ControlKeyState;
+    OUT ULONG NumBytes;
+} CONSOLE_READCONSOLE_MSG, *PCONSOLE_READCONSOLE_MSG;
+
+typedef struct _CONSOLE_WRITECONSOLE_MSG {
+    OUT ULONG NumBytes;
+    IN BOOLEAN Unicode;
+} CONSOLE_WRITECONSOLE_MSG, *PCONSOLE_WRITECONSOLE_MSG;
+
+typedef struct _CONSOLE_LANGID_MSG {
+    OUT LANGID LangId;
+} CONSOLE_LANGID_MSG, *PCONSOLE_LANGID_MSG;
+
+typedef struct _CONSOLE_MAPBITMAP_MSG {
+    OUT HANDLE Mutex;
+    OUT PVOID Bitmap;
+} CONSOLE_MAPBITMAP_MSG, *PCONSOLE_MAPBITMAP_MSG;
+
+typedef struct _CONSOLE_MAPBITMAP_MSG64 {
+    OUT PVOID64 Mutex;
+    OUT PVOID64 Bitmap;
+} CONSOLE_MAPBITMAP_MSG64, *PCONSOLE_MAPBITMAP_MSG64;
+
+typedef enum _CONSOLE_API_NUMBER_L1 {
+    ConsolepGetCP = CONSOLE_FIRST_API_NUMBER(1),
+    ConsolepGetMode,
+    ConsolepSetMode,
+    ConsolepGetNumberOfInputEvents,
+    ConsolepGetConsoleInput,
+    ConsolepReadConsole,
+    ConsolepWriteConsole,
+    ConsolepNotifyLastClose,
+    ConsolepGetLangId,
+    ConsolepMapBitmap,
+} CONSOLE_API_NUMBER_L1, *PCONSOLE_API_NUMBER_L1;
+
+typedef struct _CONSOLE_MSG_HEADER {
+    ULONG ApiNumber;
+    ULONG ApiDescriptorSize;
+} CONSOLE_MSG_HEADER, *PCONSOLE_MSG_HEADER;
+
+typedef union _CONSOLE_MSG_BODY_L1 {
+    CONSOLE_GETCP_MSG GetConsoleCP;
+    CONSOLE_MODE_MSG GetConsoleMode;
+    CONSOLE_MODE_MSG SetConsoleMode;
+    CONSOLE_GETNUMBEROFINPUTEVENTS_MSG GetNumberOfConsoleInputEvents;
+    CONSOLE_GETCONSOLEINPUT_MSG GetConsoleInput;
+    CONSOLE_READCONSOLE_MSG ReadConsole;
+    CONSOLE_WRITECONSOLE_MSG WriteConsole;
+    CONSOLE_LANGID_MSG GetConsoleLangId;
+
+#if defined(BUILD_WOW6432) && !defined(BUILD_WOW3232)
+
+    CONSOLE_MAPBITMAP_MSG64 MapBitmap;
+
+#else 
+
+    CONSOLE_MAPBITMAP_MSG MapBitmap;
+
+#endif
+
+} CONSOLE_MSG_BODY_L1, *PCONSOLE_MSG_BODY_L1;
+
+#ifndef __cplusplus
+typedef struct _CONSOLE_MSG_L1 {
+    CONSOLE_MSG_HEADER Header;
+    union {
+        CONSOLE_MSG_BODY_L1;
+    } u;
+} CONSOLE_MSG_L1, *PCONSOLE_MSG_L1;
+#else
+typedef struct _CONSOLE_MSG_L1 :
+    public CONSOLE_MSG_HEADER
+{
+    CONSOLE_MSG_BODY_L1 u;
+} CONSOLE_MSG_L1, *PCONSOLE_MSG_L1;
+#endif // __cplusplus

dep/Console/conmsgl2.h

@@ -0,0 +1,207 @@
+/*++
+
+Copyright (c) Microsoft Corporation. All rights reserved.
+
+Module Name:
+
+    conmsgl2.h
+
+Abstract:
+
+    This include file defines the layer 2 message formats used to communicate
+    between the client and server portions of the CONSOLE portion of the
+    Windows subsystem.
+
+Author:
+
+    Therese Stowell (thereses) 10-Nov-1990
+
+Revision History:
+
+    Wedson Almeida Filho (wedsonaf) 23-May-2010
+        Modified the messages for use with the console driver.
+
+--*/
+
+#pragma once
+
+typedef struct _CONSOLE_CREATESCREENBUFFER_MSG {
+    IN ULONG Flags;
+    IN ULONG BitmapInfoLength;
+    IN ULONG Usage;
+} CONSOLE_CREATESCREENBUFFER_MSG, *PCONSOLE_CREATESCREENBUFFER_MSG;
+
+#define CONSOLE_ASCII             0x1
+#define CONSOLE_REAL_UNICODE      0x2
+#define CONSOLE_ATTRIBUTE         0x3
+#define CONSOLE_FALSE_UNICODE     0x4
+
+typedef struct _CONSOLE_FILLCONSOLEOUTPUT_MSG {
+    IN COORD WriteCoord;
+    IN ULONG ElementType;
+    IN USHORT Element;
+    IN OUT ULONG Length;
+} CONSOLE_FILLCONSOLEOUTPUT_MSG, *PCONSOLE_FILLCONSOLEOUTPUT_MSG;
+
+typedef struct _CONSOLE_CTRLEVENT_MSG {
+    IN ULONG CtrlEvent;
+    IN ULONG ProcessGroupId;
+} CONSOLE_CTRLEVENT_MSG, *PCONSOLE_CTRLEVENT_MSG;
+
+typedef struct _CONSOLE_SETCP_MSG {
+    IN ULONG CodePage;
+    IN BOOLEAN Output;
+} CONSOLE_SETCP_MSG, *PCONSOLE_SETCP_MSG;
+
+typedef struct _CONSOLE_GETCURSORINFO_MSG {
+    OUT ULONG CursorSize;
+    OUT BOOLEAN Visible;
+} CONSOLE_GETCURSORINFO_MSG, *PCONSOLE_GETCURSORINFO_MSG;
+
+typedef struct _CONSOLE_SETCURSORINFO_MSG {
+    IN ULONG CursorSize;
+    IN BOOLEAN Visible;
+} CONSOLE_SETCURSORINFO_MSG, *PCONSOLE_SETCURSORINFO_MSG;
+
+typedef struct _CONSOLE_SCREENBUFFERINFO_MSG {
+    IN OUT COORD Size;
+    IN OUT COORD CursorPosition;
+    IN OUT COORD ScrollPosition;
+    IN OUT USHORT Attributes;
+    IN OUT COORD CurrentWindowSize;
+    IN OUT COORD MaximumWindowSize;
+    IN OUT USHORT PopupAttributes;
+    IN OUT BOOLEAN FullscreenSupported;
+    IN OUT COLORREF ColorTable[16];
+} CONSOLE_SCREENBUFFERINFO_MSG, *PCONSOLE_SCREENBUFFERINFO_MSG;
+
+typedef struct _CONSOLE_SETSCREENBUFFERSIZE_MSG {
+    IN COORD Size;
+} CONSOLE_SETSCREENBUFFERSIZE_MSG, *PCONSOLE_SETSCREENBUFFERSIZE_MSG;
+
+typedef struct _CONSOLE_SETCURSORPOSITION_MSG {
+    IN COORD CursorPosition;
+} CONSOLE_SETCURSORPOSITION_MSG, *PCONSOLE_SETCURSORPOSITION_MSG;
+
+typedef struct _CONSOLE_GETLARGESTWINDOWSIZE_MSG {
+    OUT COORD Size;
+} CONSOLE_GETLARGESTWINDOWSIZE_MSG, *PCONSOLE_GETLARGESTWINDOWSIZE_MSG;
+
+typedef struct _CONSOLE_SCROLLSCREENBUFFER_MSG {
+    IN SMALL_RECT ScrollRectangle;
+    IN SMALL_RECT ClipRectangle;
+    IN BOOLEAN Clip;
+    IN BOOLEAN Unicode;
+    IN COORD DestinationOrigin;
+    IN CHAR_INFO Fill;
+} CONSOLE_SCROLLSCREENBUFFER_MSG, *PCONSOLE_SCROLLSCREENBUFFER_MSG;
+
+typedef struct _CONSOLE_SETTEXTATTRIBUTE_MSG {
+    IN USHORT Attributes;
+} CONSOLE_SETTEXTATTRIBUTE_MSG, *PCONSOLE_SETTEXTATTRIBUTE_MSG;
+
+typedef struct _CONSOLE_SETWINDOWINFO_MSG {
+    IN BOOLEAN Absolute;
+    IN SMALL_RECT Window;
+} CONSOLE_SETWINDOWINFO_MSG, *PCONSOLE_SETWINDOWINFO_MSG;
+
+typedef struct _CONSOLE_READCONSOLEOUTPUTSTRING_MSG {
+    IN COORD ReadCoord;
+    IN ULONG StringType;
+    OUT ULONG NumRecords;
+} CONSOLE_READCONSOLEOUTPUTSTRING_MSG, *PCONSOLE_READCONSOLEOUTPUTSTRING_MSG;
+
+typedef struct _CONSOLE_WRITECONSOLEINPUT_MSG {
+    OUT ULONG NumRecords;
+    IN BOOLEAN Unicode;
+    IN BOOLEAN Append;
+} CONSOLE_WRITECONSOLEINPUT_MSG, *PCONSOLE_WRITECONSOLEINPUT_MSG;
+
+typedef struct _CONSOLE_WRITECONSOLEOUTPUTSTRING_MSG {
+    IN COORD WriteCoord;
+    IN ULONG StringType;
+    OUT ULONG NumRecords;
+} CONSOLE_WRITECONSOLEOUTPUTSTRING_MSG, *PCONSOLE_WRITECONSOLEOUTPUTSTRING_MSG;
+
+typedef struct _CONSOLE_WRITECONSOLEOUTPUT_MSG {
+    IN OUT SMALL_RECT CharRegion;
+    IN BOOLEAN Unicode;
+} CONSOLE_WRITECONSOLEOUTPUT_MSG, *PCONSOLE_WRITECONSOLEOUTPUT_MSG;
+
+typedef struct _CONSOLE_READCONSOLEOUTPUT_MSG {
+    IN OUT SMALL_RECT CharRegion;
+    IN BOOLEAN Unicode;
+} CONSOLE_READCONSOLEOUTPUT_MSG, *PCONSOLE_READCONSOLEOUTPUT_MSG;
+
+typedef struct _CONSOLE_GETTITLE_MSG {
+    OUT ULONG TitleLength;
+    IN BOOLEAN Unicode;
+    IN BOOLEAN Original;
+} CONSOLE_GETTITLE_MSG, *PCONSOLE_GETTITLE_MSG;
+
+typedef struct _CONSOLE_SETTITLE_MSG {
+    IN BOOLEAN Unicode;
+} CONSOLE_SETTITLE_MSG, *PCONSOLE_SETTITLE_MSG;
+
+typedef enum _CONSOLE_API_NUMBER_L2 {
+    ConsolepFillConsoleOutput = CONSOLE_FIRST_API_NUMBER(2),
+    ConsolepGenerateCtrlEvent,
+    ConsolepSetActiveScreenBuffer,
+    ConsolepFlushInputBuffer,
+    ConsolepSetCP,
+    ConsolepGetCursorInfo,
+    ConsolepSetCursorInfo,
+    ConsolepGetScreenBufferInfo,
+    ConsolepSetScreenBufferInfo,
+    ConsolepSetScreenBufferSize,
+    ConsolepSetCursorPosition,
+    ConsolepGetLargestWindowSize,
+    ConsolepScrollScreenBuffer,
+    ConsolepSetTextAttribute,
+    ConsolepSetWindowInfo,
+    ConsolepReadConsoleOutputString,
+    ConsolepWriteConsoleInput,
+    ConsolepWriteConsoleOutput,
+    ConsolepWriteConsoleOutputString,
+    ConsolepReadConsoleOutput,
+    ConsolepGetTitle,
+    ConsolepSetTitle,
+} CONSOLE_API_NUMBER_L2, *PCONSOLE_API_NUMBER_L2;
+
+typedef union _CONSOLE_MSG_BODY_L2 {
+    CONSOLE_CTRLEVENT_MSG GenerateConsoleCtrlEvent;
+    CONSOLE_FILLCONSOLEOUTPUT_MSG FillConsoleOutput;
+    CONSOLE_SETCP_MSG SetConsoleCP;
+    CONSOLE_GETCURSORINFO_MSG GetConsoleCursorInfo;
+    CONSOLE_SETCURSORINFO_MSG SetConsoleCursorInfo;
+    CONSOLE_SCREENBUFFERINFO_MSG GetConsoleScreenBufferInfo;
+    CONSOLE_SCREENBUFFERINFO_MSG SetConsoleScreenBufferInfo;
+    CONSOLE_SETSCREENBUFFERSIZE_MSG SetConsoleScreenBufferSize;
+    CONSOLE_SETCURSORPOSITION_MSG SetConsoleCursorPosition;
+    CONSOLE_GETLARGESTWINDOWSIZE_MSG GetLargestConsoleWindowSize;
+    CONSOLE_SCROLLSCREENBUFFER_MSG ScrollConsoleScreenBuffer;
+    CONSOLE_SETTEXTATTRIBUTE_MSG SetConsoleTextAttribute;
+    CONSOLE_SETWINDOWINFO_MSG SetConsoleWindowInfo;
+    CONSOLE_READCONSOLEOUTPUTSTRING_MSG ReadConsoleOutputString;
+    CONSOLE_WRITECONSOLEINPUT_MSG WriteConsoleInput;
+    CONSOLE_WRITECONSOLEOUTPUTSTRING_MSG WriteConsoleOutputString;
+    CONSOLE_WRITECONSOLEOUTPUT_MSG WriteConsoleOutput;
+    CONSOLE_READCONSOLEOUTPUT_MSG ReadConsoleOutput;
+    CONSOLE_SETTITLE_MSG SetConsoleTitle;
+    CONSOLE_GETTITLE_MSG GetConsoleTitle;
+} CONSOLE_MSG_BODY_L2, *PCONSOLE_MSG_BODY_L2;
+
+#ifndef __cplusplus
+typedef struct _CONSOLE_MSG_L2 {
+    CONSOLE_MSG_HEADER Header;
+    union {
+        CONSOLE_MSG_BODY_L2;
+    } u;
+} CONSOLE_MSG_L2, *PCONSOLE_MSG_L2;
+#else
+typedef struct _CONSOLE_MSG_L2 :
+    public CONSOLE_MSG_HEADER
+{
+    CONSOLE_MSG_BODY_L2 u;
+} CONSOLE_MSG_L2, *PCONSOLE_MSG_L2;
+#endif // __cplusplus

dep/Console/conmsgl3.h

@@ -0,0 +1,392 @@
+/*++
+
+Copyright (c) 1985 - 1999, Microsoft Corporation
+
+Module Name:
+
+    conmsgl3.h
+
+Abstract:
+
+    This include file defines the message formats used to communicate
+    between the client and server portions of the CONSOLE portion of the
+    Windows subsystem.
+
+Author:
+
+    Therese Stowell (thereses) 10-Nov-1990
+
+Revision History:
+
+    Wedson Almeida Filho (wedsonaf) 23-May-2010
+        Modified the messages for use with the console driver.
+
+--*/
+
+#pragma once
+
+#include <winconp.h>  // need FONT_SELECT
+
+typedef struct _CONSOLE_GETNUMBEROFFONTS_MSG {
+    OUT ULONG NumberOfFonts;
+} CONSOLE_GETNUMBEROFFONTS_MSG, *PCONSOLE_GETNUMBEROFFONTS_MSG;
+
+typedef struct _CONSOLE_GETSELECTIONINFO_MSG {
+    OUT CONSOLE_SELECTION_INFO SelectionInfo;
+} CONSOLE_GETSELECTIONINFO_MSG, *PCONSOLE_GETSELECTIONINFO_MSG;
+
+typedef struct _CONSOLE_GETMOUSEINFO_MSG {
+    OUT ULONG NumButtons;
+} CONSOLE_GETMOUSEINFO_MSG, *PCONSOLE_GETMOUSEINFO_MSG;
+
+typedef struct _CONSOLE_GETFONTINFO_MSG {
+    IN BOOLEAN MaximumWindow;
+    OUT ULONG NumFonts;  // this value is valid even for error cases
+} CONSOLE_GETFONTINFO_MSG, *PCONSOLE_GETFONTINFO_MSG;
+
+typedef struct _CONSOLE_GETFONTSIZE_MSG {
+    IN ULONG  FontIndex;
+    OUT COORD FontSize;
+} CONSOLE_GETFONTSIZE_MSG, *PCONSOLE_GETFONTSIZE_MSG;
+
+typedef struct _CONSOLE_CURRENTFONT_MSG {
+    IN BOOLEAN MaximumWindow;
+    IN OUT ULONG FontIndex;
+    IN OUT COORD FontSize;
+    IN OUT ULONG FontFamily;
+    IN OUT ULONG FontWeight;
+    IN OUT WCHAR FaceName[LF_FACESIZE];
+} CONSOLE_CURRENTFONT_MSG, *PCONSOLE_CURRENTFONT_MSG;
+
+typedef struct _CONSOLE_SETFONT_MSG {
+    IN ULONG  FontIndex;
+} CONSOLE_SETFONT_MSG, *PCONSOLE_SETFONT_MSG;
+
+typedef struct _CONSOLE_SETICON_MSG {
+    IN HICON hIcon;
+} CONSOLE_SETICON_MSG, *PCONSOLE_SETICON_MSG;
+
+typedef struct _CONSOLE_SETICON_MSG64 {
+    IN PVOID64 hIcon;
+} CONSOLE_SETICON_MSG64, *PCONSOLE_SETICON_MSG64;
+
+typedef struct _CONSOLE_ADDALIAS_MSG {
+    IN USHORT SourceLength;
+    IN USHORT TargetLength;
+    IN USHORT ExeLength;
+    IN BOOLEAN Unicode;
+} CONSOLE_ADDALIAS_MSG, *PCONSOLE_ADDALIAS_MSG;
+
+typedef struct _CONSOLE_GETALIAS_MSG {
+    IN USHORT SourceLength;
+    OUT USHORT TargetLength;
+    IN USHORT ExeLength;
+    IN BOOLEAN Unicode;
+} CONSOLE_GETALIAS_MSG, *PCONSOLE_GETALIAS_MSG;
+
+typedef struct _CONSOLE_GETALIASESLENGTH_MSG {
+    OUT ULONG AliasesLength;
+    IN BOOLEAN Unicode;
+} CONSOLE_GETALIASESLENGTH_MSG, *PCONSOLE_GETALIASESLENGTH_MSG;
+
+typedef struct _CONSOLE_GETALIASEXESLENGTH_MSG {
+    OUT ULONG AliasExesLength;
+    IN BOOLEAN Unicode;
+} CONSOLE_GETALIASEXESLENGTH_MSG, *PCONSOLE_GETALIASEXESLENGTH_MSG;
+
+typedef struct _CONSOLE_GETALIASES_MSG {
+    IN BOOLEAN Unicode;
+    OUT ULONG AliasesBufferLength;
+} CONSOLE_GETALIASES_MSG, *PCONSOLE_GETALIASES_MSG;
+
+typedef struct _CONSOLE_GETALIASEXES_MSG {
+    OUT ULONG AliasExesBufferLength;
+    IN BOOLEAN Unicode;
+} CONSOLE_GETALIASEXES_MSG, *PCONSOLE_GETALIASEXES_MSG;
+
+typedef struct _CONSOLE_EXPUNGECOMMANDHISTORY_MSG {
+    IN BOOLEAN Unicode;
+} CONSOLE_EXPUNGECOMMANDHISTORY_MSG, *PCONSOLE_EXPUNGECOMMANDHISTORY_MSG;
+
+typedef struct _CONSOLE_SETNUMBEROFCOMMANDS_MSG {
+    IN ULONG NumCommands;
+    IN BOOLEAN Unicode;
+} CONSOLE_SETNUMBEROFCOMMANDS_MSG, *PCONSOLE_SETNUMBEROFCOMMANDS_MSG;
+
+typedef struct _CONSOLE_GETCOMMANDHISTORYLENGTH_MSG {
+    OUT ULONG CommandHistoryLength;
+    IN BOOLEAN Unicode;
+} CONSOLE_GETCOMMANDHISTORYLENGTH_MSG, *PCONSOLE_GETCOMMANDHISTORYLENGTH_MSG;
+
+typedef struct _CONSOLE_GETCOMMANDHISTORY_MSG {
+    OUT ULONG CommandBufferLength;
+    IN BOOLEAN Unicode;
+} CONSOLE_GETCOMMANDHISTORY_MSG, *PCONSOLE_GETCOMMANDHISTORY_MSG;
+
+typedef struct _CONSOLE_INVALIDATERECT_MSG {
+    IN SMALL_RECT Rect;
+} CONSOLE_INVALIDATERECT_MSG, *PCONSOLE_INVALIDATERECT_MSG;
+
+typedef struct _CONSOLE_VDM_MSG {
+    IN ULONG iFunction;
+    OUT BOOLEAN Bool;
+    IN OUT POINT Point;
+    OUT RECT Rect;
+} CONSOLE_VDM_MSG, *PCONSOLE_VDM_MSG;
+
+typedef struct _CONSOLE_SETCURSOR_MSG {
+    IN HCURSOR CursorHandle;
+} CONSOLE_SETCURSOR_MSG, *PCONSOLE_SETCURSOR_MSG;
+
+typedef struct _CONSOLE_SETCURSOR_MSG64 {
+    IN PVOID64 CursorHandle;
+} CONSOLE_SETCURSOR_MSG64, *PCONSOLE_SETCURSOR_MSG64;
+
+typedef struct _CONSOLE_SHOWCURSOR_MSG {
+    IN BOOLEAN bShow;
+    OUT ULONG DisplayCount;
+} CONSOLE_SHOWCURSOR_MSG, *PCONSOLE_SHOWCURSOR_MSG;
+
+typedef struct _CONSOLE_MENUCONTROL_MSG {
+    IN ULONG CommandIdLow;
+    IN ULONG CommandIdHigh;
+    OUT HMENU hMenu;
+} CONSOLE_MENUCONTROL_MSG, *PCONSOLE_MENUCONTROL_MSG;
+
+typedef struct _CONSOLE_MENUCONTROL_MSG64 {
+    IN ULONG CommandIdLow;
+    IN ULONG CommandIdHigh;
+    OUT PVOID64 hMenu;
+} CONSOLE_MENUCONTROL_MSG64, *PCONSOLE_MENUCONTROL_MSG64;
+
+typedef struct _CONSOLE_SETPALETTE_MSG {
+    IN HPALETTE hPalette;
+    IN ULONG dwUsage;
+} CONSOLE_SETPALETTE_MSG, *PCONSOLE_SETPALETTE_MSG;
+
+typedef struct _CONSOLE_SETPALETTE_MSG64 {
+    IN PVOID64 hPalette;
+    IN ULONG dwUsage;
+} CONSOLE_SETPALETTE_MSG64, *PCONSOLE_SETPALETTE_MSG64;
+
+typedef struct _CONSOLE_SETDISPLAYMODE_MSG {
+    IN ULONG dwFlags;
+    OUT COORD ScreenBufferDimensions;
+} CONSOLE_SETDISPLAYMODE_MSG, *PCONSOLE_SETDISPLAYMODE_MSG;
+
+typedef struct _CONSOLE_REGISTERVDM_MSG {
+    IN ULONG RegisterFlags;
+    IN HANDLE StartEvent;
+    IN HANDLE EndEvent;
+    IN HANDLE ErrorEvent;
+    OUT ULONG StateLength;
+    OUT PVOID StateBuffer;
+    OUT PVOID VDMBuffer;
+} CONSOLE_REGISTERVDM_MSG, *PCONSOLE_REGISTERVDM_MSG;
+
+typedef struct _CONSOLE_REGISTERVDM_MSG64 {
+    IN ULONG RegisterFlags;
+    IN PVOID64 StartEvent;
+    IN PVOID64 EndEvent;
+    IN PVOID64 ErrorEvent;
+    OUT ULONG StateLength;
+    OUT PVOID64 StateBuffer;
+    OUT PVOID64 VDMBuffer;
+} CONSOLE_REGISTERVDM_MSG64, *PCONSOLE_REGISTERVDM_MSG64;
+
+typedef struct _CONSOLE_GETHARDWARESTATE_MSG {
+    OUT COORD Resolution;
+    OUT COORD FontSize;
+} CONSOLE_GETHARDWARESTATE_MSG, *PCONSOLE_GETHARDWARESTATE_MSG;
+
+typedef struct _CONSOLE_SETHARDWARESTATE_MSG {
+    IN COORD Resolution;
+    IN COORD FontSize;
+} CONSOLE_SETHARDWARESTATE_MSG, *PCONSOLE_SETHARDWARESTATE_MSG;
+
+typedef struct _CONSOLE_GETDISPLAYMODE_MSG {
+    OUT ULONG ModeFlags;
+} CONSOLE_GETDISPLAYMODE_MSG, *PCONSOLE_GETDISPLAYMODE_MSG;
+
+typedef struct _CONSOLE_GETKEYBOARDLAYOUTNAME_MSG {
+    union {
+        WCHAR awchLayout[9];
+        char achLayout[9];
+    };
+    BOOLEAN bAnsi;
+} CONSOLE_GETKEYBOARDLAYOUTNAME_MSG, *PCONSOLE_GETKEYBOARDLAYOUTNAME_MSG;
+
+typedef struct _CONSOLE_SETKEYSHORTCUTS_MSG {
+    IN BOOLEAN Set;
+    IN BYTE ReserveKeys;
+} CONSOLE_SETKEYSHORTCUTS_MSG, *PCONSOLE_SETKEYSHORTCUTS_MSG;
+
+typedef struct _CONSOLE_SETMENUCLOSE_MSG {
+    IN BOOLEAN Enable;
+} CONSOLE_SETMENUCLOSE_MSG, *PCONSOLE_SETMENUCLOSE_MSG;
+
+typedef struct _CONSOLE_CHAR_TYPE_MSG {
+    IN COORD coordCheck;
+    OUT ULONG dwType;
+} CONSOLE_CHAR_TYPE_MSG, *PCONSOLE_CHAR_TYPE_MSG;
+
+typedef struct _CONSOLE_LOCAL_EUDC_MSG {
+    IN USHORT CodePoint;
+    IN COORD FontSize;
+} CONSOLE_LOCAL_EUDC_MSG, *PCONSOLE_LOCAL_EUDC_MSG;
+
+typedef struct _CONSOLE_CURSOR_MODE_MSG {
+    IN OUT BOOLEAN Blink;
+    IN OUT BOOLEAN DBEnable;
+} CONSOLE_CURSOR_MODE_MSG, *PCONSOLE_CURSOR_MODE_MSG;
+
+typedef struct _CONSOLE_REGISTEROS2_MSG {
+    IN BOOLEAN fOs2Register;
+} CONSOLE_REGISTEROS2_MSG, *PCONSOLE_REGISTEROS2_MSG;
+
+typedef struct _CONSOLE_SETOS2OEMFORMAT_MSG {
+    IN BOOLEAN fOs2OemFormat;
+} CONSOLE_SETOS2OEMFORMAT_MSG, *PCONSOLE_SETOS2OEMFORMAT_MSG;
+
+typedef struct _CONSOLE_NLS_MODE_MSG {
+    IN OUT BOOLEAN Ready;
+    IN ULONG NlsMode;
+} CONSOLE_NLS_MODE_MSG, *PCONSOLE_NLS_MODE_MSG;
+
+typedef struct _CONSOLE_GETCONSOLEWINDOW_MSG {
+    OUT HWND hwnd;
+} CONSOLE_GETCONSOLEWINDOW_MSG, *PCONSOLE_GETCONSOLEWINDOW_MSG;
+
+typedef struct _CONSOLE_GETCONSOLEWINDOW_MSG64 {
+    OUT PVOID64 hwnd;
+} CONSOLE_GETCONSOLEWINDOW_MSG64, *PCONSOLE_GETCONSOLEWINDOW_MSG64;
+
+typedef struct _CONSOLE_GETPROCESSLIST_MSG {
+    OUT ULONG dwProcessCount;
+} CONSOLE_GETCONSOLEPROCESSLIST_MSG, *PCONSOLE_GETCONSOLEPROCESSLIST_MSG;
+
+typedef struct _CONSOLE_GETHISTORY_MSG {
+    OUT ULONG HistoryBufferSize;
+    OUT ULONG NumberOfHistoryBuffers;
+    OUT ULONG dwFlags;
+} CONSOLE_HISTORY_MSG, *PCONSOLE_HISTORY_MSG;
+
+typedef enum _CONSOLE_API_NUMBER_L3 {
+    ConsolepGetNumberOfFonts = CONSOLE_FIRST_API_NUMBER(3),
+    ConsolepGetMouseInfo,
+    ConsolepGetFontInfo,
+    ConsolepGetFontSize,
+    ConsolepGetCurrentFont,
+    ConsolepSetFont,
+    ConsolepSetIcon,
+    ConsolepInvalidateBitmapRect,
+    ConsolepVDMOperation,
+    ConsolepSetCursor,
+    ConsolepShowCursor,
+    ConsolepMenuControl,
+    ConsolepSetPalette,
+    ConsolepSetDisplayMode,
+    ConsolepRegisterVDM,
+    ConsolepGetHardwareState,
+    ConsolepSetHardwareState,
+    ConsolepGetDisplayMode,
+    ConsolepAddAlias,
+    ConsolepGetAlias,
+    ConsolepGetAliasesLength,
+    ConsolepGetAliasExesLength,
+    ConsolepGetAliases,
+    ConsolepGetAliasExes,
+    ConsolepExpungeCommandHistory,
+    ConsolepSetNumberOfCommands,
+    ConsolepGetCommandHistoryLength,
+    ConsolepGetCommandHistory,
+    ConsolepSetKeyShortcuts,
+    ConsolepSetMenuClose,
+    ConsolepGetKeyboardLayoutName,
+    ConsolepGetConsoleWindow,
+    ConsolepCharType,
+    ConsolepSetLocalEUDC,
+    ConsolepSetCursorMode,
+    ConsolepGetCursorMode,
+    ConsolepRegisterOS2,
+    ConsolepSetOS2OemFormat,
+    ConsolepGetNlsMode,
+    ConsolepSetNlsMode,
+    ConsolepGetSelectionInfo,
+    ConsolepGetConsoleProcessList,
+    ConsolepGetHistory,
+    ConsolepSetHistory,
+    ConsolepSetCurrentFont,
+} CONSOLE_API_NUMBER_L3, *PCONSOLE_API_NUMBER_L3;
+
+typedef union _CONSOLE_MSG_BODY_L3 {
+    CONSOLE_GETNUMBEROFFONTS_MSG GetNumberOfConsoleFonts;
+    CONSOLE_GETMOUSEINFO_MSG GetConsoleMouseInfo;
+    CONSOLE_GETFONTINFO_MSG GetConsoleFontInfo;
+    CONSOLE_GETFONTSIZE_MSG GetConsoleFontSize;
+    CONSOLE_CURRENTFONT_MSG GetCurrentConsoleFont;
+    CONSOLE_SETFONT_MSG SetConsoleFont;
+    CONSOLE_INVALIDATERECT_MSG InvalidateConsoleBitmapRect;
+    CONSOLE_VDM_MSG VDMConsoleOperation;
+    CONSOLE_SHOWCURSOR_MSG ShowConsoleCursor;
+    CONSOLE_SETDISPLAYMODE_MSG SetConsoleDisplayMode;
+#ifdef BUILD_WOW6432
+    CONSOLE_REGISTERVDM_MSG64 RegisterConsoleVDM;
+    CONSOLE_SETCURSOR_MSG64 SetConsoleCursor;
+    CONSOLE_SETICON_MSG64 SetConsoleIcon;
+    CONSOLE_MENUCONTROL_MSG64 ConsoleMenuControl;
+    CONSOLE_SETPALETTE_MSG64 SetConsolePalette;
+    CONSOLE_GETCONSOLEWINDOW_MSG64 GetConsoleWindow;
+#else
+    CONSOLE_REGISTERVDM_MSG RegisterConsoleVDM;
+    CONSOLE_SETCURSOR_MSG SetConsoleCursor;
+    CONSOLE_SETICON_MSG SetConsoleIcon;
+    CONSOLE_MENUCONTROL_MSG ConsoleMenuControl;
+    CONSOLE_SETPALETTE_MSG SetConsolePalette;
+    CONSOLE_GETCONSOLEWINDOW_MSG GetConsoleWindow;
+#endif
+    CONSOLE_GETHARDWARESTATE_MSG GetConsoleHardwareState;
+    CONSOLE_SETHARDWARESTATE_MSG SetConsoleHardwareState;
+    CONSOLE_GETDISPLAYMODE_MSG GetConsoleDisplayMode;
+    CONSOLE_ADDALIAS_MSG AddConsoleAliasW;
+    CONSOLE_GETALIAS_MSG GetConsoleAliasW;
+    CONSOLE_GETALIASESLENGTH_MSG GetConsoleAliasesLengthW;
+    CONSOLE_GETALIASEXESLENGTH_MSG GetConsoleAliasExesLengthW;
+    CONSOLE_GETALIASES_MSG GetConsoleAliasesW;
+    CONSOLE_GETALIASEXES_MSG GetConsoleAliasExesW;
+    CONSOLE_EXPUNGECOMMANDHISTORY_MSG ExpungeConsoleCommandHistoryW;
+    CONSOLE_SETNUMBEROFCOMMANDS_MSG SetConsoleNumberOfCommandsW;
+    CONSOLE_GETCOMMANDHISTORYLENGTH_MSG GetConsoleCommandHistoryLengthW;
+    CONSOLE_GETCOMMANDHISTORY_MSG GetConsoleCommandHistoryW;
+    CONSOLE_SETKEYSHORTCUTS_MSG SetConsoleKeyShortcuts;
+    CONSOLE_SETMENUCLOSE_MSG SetConsoleMenuClose;
+    CONSOLE_GETKEYBOARDLAYOUTNAME_MSG GetKeyboardLayoutName;
+    CONSOLE_CHAR_TYPE_MSG GetConsoleCharType;
+    CONSOLE_LOCAL_EUDC_MSG SetConsoleLocalEUDC;
+    CONSOLE_CURSOR_MODE_MSG SetConsoleCursorMode;
+    CONSOLE_CURSOR_MODE_MSG GetConsoleCursorMode;
+    CONSOLE_REGISTEROS2_MSG RegisterConsoleOS2;
+    CONSOLE_SETOS2OEMFORMAT_MSG SetConsoleOS2OemFormat;
+    CONSOLE_NLS_MODE_MSG GetConsoleNlsMode;
+    CONSOLE_NLS_MODE_MSG SetConsoleNlsMode;
+    CONSOLE_GETSELECTIONINFO_MSG GetConsoleSelectionInfo;
+    CONSOLE_GETCONSOLEPROCESSLIST_MSG GetConsoleProcessList;
+    CONSOLE_CURRENTFONT_MSG SetCurrentConsoleFont;
+    CONSOLE_HISTORY_MSG SetConsoleHistory;
+    CONSOLE_HISTORY_MSG GetConsoleHistory;
+} CONSOLE_MSG_BODY_L3, *PCONSOLE_MSG_BODY_L3;
+
+#ifndef __cplusplus
+typedef struct _CONSOLE_MSG_L3 {
+    CONSOLE_MSG_HEADER Header;
+    union {
+        CONSOLE_MSG_BODY_L3;
+    } u;
+} CONSOLE_MSG_L3, *PCONSOLE_MSG_L3;
+#else
+typedef struct _CONSOLE_MSG_L3 :
+    public CONSOLE_MSG_HEADER
+{
+    CONSOLE_MSG_BODY_L3 u;
+} CONSOLE_MSG_L3, *PCONSOLE_MSG_L3;
+#endif  // __cplusplus

dep/Console/ntcon.h

@@ -0,0 +1,29 @@
+//
+//    Copyright (C) Microsoft.  All rights reserved.
+//
+#ifndef _NTCON_
+#define _NTCON_
+
+//
+// originally in winconp.h
+//
+#define CONSOLE_DETACHED_PROCESS ((HANDLE)-1)
+#define CONSOLE_NEW_CONSOLE ((HANDLE)-2)
+#define CONSOLE_CREATE_NO_WINDOW ((HANDLE)-3)
+
+#define SYSTEM_ROOT_CONSOLE_EVENT 3
+
+#define CONSOLE_READ_NOREMOVE   0x0001
+#define CONSOLE_READ_NOWAIT     0x0002
+
+#define CONSOLE_READ_VALID      (CONSOLE_READ_NOREMOVE | CONSOLE_READ_NOWAIT)
+
+#define CONSOLE_GRAPHICS_BUFFER  2
+
+//
+// These are flags stored in PEB::ProcessParameters::ConsoleFlags.
+//
+#define CONSOLE_IGNORE_CTRL_C 0x1
+
+
+#endif //_NTCON_

dep/Console/winconp.h

@@ -0,0 +1,669 @@
+
+#ifndef _WINCONP_
+#define _WINCONP_
+
+#pragma once
+
+#ifdef __cplusplus
+extern "C" {
+#endif
+
+#if _MSC_VER >= 1200
+#pragma warning(push)
+#pragma warning(disable:4820) // padding added after data member
+#endif
+
+#include <wincontypes.h>
+
+//
+// History flags (internal)
+//
+
+#define CHI_VALID_FLAGS (HISTORY_NO_DUP_FLAG)
+
+//
+// Selection flags (internal)
+//
+
+#define CONSOLE_SELECTION_INVERTED      0x0010   // selection is inverted (turned off)
+#define CONSOLE_SELECTION_VALID         (CONSOLE_SELECTION_IN_PROGRESS | \
+                                         CONSOLE_SELECTION_NOT_EMPTY | \
+                                         CONSOLE_MOUSE_SELECTION | \
+                                         CONSOLE_MOUSE_DOWN)
+
+
+WINBASEAPI
+BOOL
+WINAPI
+GetConsoleKeyboardLayoutNameA(
+    _Out_writes_(KL_NAMELENGTH) LPSTR pszLayout);
+WINBASEAPI
+BOOL
+WINAPI
+GetConsoleKeyboardLayoutNameW(
+    _Out_writes_(KL_NAMELENGTH) LPWSTR pszLayout);
+#ifdef UNICODE
+#define GetConsoleKeyboardLayoutName  GetConsoleKeyboardLayoutNameW
+#else
+#define GetConsoleKeyboardLayoutName  GetConsoleKeyboardLayoutNameA
+#endif // !UNICODE
+
+//
+// Registry strings
+//
+
+#define CONSOLE_REGISTRY_STRING                         L"Console"
+#define CONSOLE_REGISTRY_FONTSIZE                       L"FontSize"
+#define CONSOLE_REGISTRY_FONTFAMILY                     L"FontFamily"
+#define CONSOLE_REGISTRY_BUFFERSIZE                     L"ScreenBufferSize"
+#define CONSOLE_REGISTRY_CURSORSIZE                     L"CursorSize"
+#define CONSOLE_REGISTRY_WINDOWMAXIMIZED                L"WindowMaximized"
+#define CONSOLE_REGISTRY_WINDOWSIZE                     L"WindowSize"
+#define CONSOLE_REGISTRY_WINDOWPOS                      L"WindowPosition"
+#define CONSOLE_REGISTRY_WINDOWALPHA                    L"WindowAlpha"
+#define CONSOLE_REGISTRY_FILLATTR                       L"ScreenColors"
+#define CONSOLE_REGISTRY_POPUPATTR                      L"PopupColors"
+#define CONSOLE_REGISTRY_FULLSCR                        L"FullScreen"
+#define CONSOLE_REGISTRY_QUICKEDIT                      L"QuickEdit"
+#define CONSOLE_REGISTRY_FACENAME                       L"FaceName"
+#define CONSOLE_REGISTRY_FONTWEIGHT                     L"FontWeight"
+#define CONSOLE_REGISTRY_INSERTMODE                     L"InsertMode"
+#define CONSOLE_REGISTRY_HISTORYSIZE                    L"HistoryBufferSize"
+#define CONSOLE_REGISTRY_HISTORYBUFS                    L"NumberOfHistoryBuffers"
+#define CONSOLE_REGISTRY_HISTORYNODUP                   L"HistoryNoDup"
+#define CONSOLE_REGISTRY_COLORTABLE                     L"ColorTable%02u"
+#define CONSOLE_REGISTRY_EXTENDEDEDITKEY                L"ExtendedEditKey"
+#define CONSOLE_REGISTRY_EXTENDEDEDITKEY_CUSTOM         L"ExtendedEditkeyCustom"
+#define CONSOLE_REGISTRY_WORD_DELIM                     L"WordDelimiters"
+#define CONSOLE_REGISTRY_TRIMZEROHEADINGS               L"TrimLeadingZeros"
+#define CONSOLE_REGISTRY_LOAD_CONIME                    L"LoadConIme"
+#define CONSOLE_REGISTRY_ENABLE_COLOR_SELECTION         L"EnableColorSelection"
+#define CONSOLE_REGISTRY_SCROLLSCALE                    L"ScrollScale"
+
+// V2 console settings
+#define CONSOLE_REGISTRY_FORCEV2                        L"ForceV2"
+#define CONSOLE_REGISTRY_LINESELECTION                  L"LineSelection"
+#define CONSOLE_REGISTRY_FILTERONPASTE                  L"FilterOnPaste"
+#define CONSOLE_REGISTRY_LINEWRAP                       L"LineWrap"
+#define CONSOLE_REGISTRY_CTRLKEYSHORTCUTS_DISABLED      L"CtrlKeyShortcutsDisabled"
+#define CONSOLE_REGISTRY_ALLOW_ALTF4_CLOSE              L"AllowAltF4Close"
+#define CONSOLE_REGISTRY_VIRTTERM_LEVEL                 L"VirtualTerminalLevel"
+
+#define CONSOLE_REGISTRY_CURSORTYPE                     L"CursorType"
+#define CONSOLE_REGISTRY_CURSORCOLOR                    L"CursorColor"
+
+#define CONSOLE_REGISTRY_INTERCEPTCOPYPASTE             L"InterceptCopyPaste"
+
+#define CONSOLE_REGISTRY_COPYCOLOR                      L"CopyColor"
+#define CONSOLE_REGISTRY_USEDX                          L"UseDx"
+
+#define CONSOLE_REGISTRY_DEFAULTFOREGROUND             L"DefaultForeground"
+#define CONSOLE_REGISTRY_DEFAULTBACKGROUND             L"DefaultBackground"
+#define CONSOLE_REGISTRY_TERMINALSCROLLING             L"TerminalScrolling"
+// end V2 console settings
+
+    /*
+     * Starting code page
+     */
+#define CONSOLE_REGISTRY_CODEPAGE    (L"CodePage")
+
+//
+// registry strings on HKEY_LOCAL_MACHINE
+//
+#define MACHINE_REGISTRY_CONSOLE        (L"\\Registry\\Machine\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Console")
+#define MACHINE_REGISTRY_CONSOLEIME     (L"ConsoleIME")
+#define MACHINE_REGISTRY_ENABLE_CONIME_ON_SYSTEM_PROCESS     (L"EnableConImeOnSystemProcess")
+
+
+#define MACHINE_REGISTRY_CONSOLE_TTFONT (L"\\Registry\\Machine\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Console\\TrueTypeFont")
+#define MACHINE_REGISTRY_CONSOLE_TTFONT_WIN32_PATH (L"Software\\Microsoft\\Windows NT\\CurrentVersion\\Console\\TrueTypeFont")
+
+
+#define MACHINE_REGISTRY_CONSOLE_NLS    (L"\\Registry\\Machine\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Console\\Nls")
+
+
+#define MACHINE_REGISTRY_CONSOLE_FULLSCREEN (L"\\Registry\\Machine\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Console\\FullScreen")
+#define MACHINE_REGISTRY_INITIAL_PALETTE           (L"InitialPalette")
+#define MACHINE_REGISTRY_COLOR_BUFFER              (L"ColorBuffer")
+#define MACHINE_REGISTRY_COLOR_BUFFER_NO_TRANSLATE (L"ColorBufferNoTranslate")
+#define MACHINE_REGISTRY_MODE_FONT_PAIRS           (L"ModeFontPairs")
+#define MACHINE_REGISTRY_FS_CODEPAGE               (L"CodePage")
+
+
+#define MACHINE_REGISTRY_EUDC    (L"\\Registry\\Machine\\System\\CurrentControlSet\\Control\\Nls\\CodePage\\EUDCCodeRange")
+
+
+//
+// TrueType font list
+//
+
+// doesn't available bold when add BOLD_MARK on first of face name.
+#define BOLD_MARK    (L'*')
+
+typedef struct _TT_FONT_LIST {
+    SINGLE_LIST_ENTRY List;
+    UINT  CodePage;
+    BOOL  fDisableBold;
+    TCHAR FaceName1[LF_FACESIZE];
+    TCHAR FaceName2[LF_FACESIZE];
+} TTFONTLIST, *LPTTFONTLIST;
+
+//
+// registry strings on HKEY_CURRENT_USER
+//
+#define PRELOAD_REGISTRY_STRING      (L"Keyboard Layout\\Preload")
+
+
+//
+// Special key for previous word erase
+//
+#define EXTKEY_ERASE_PREV_WORD  (0x7f)
+
+#ifndef NOGDI
+
+typedef struct _CONSOLE_GRAPHICS_BUFFER_INFO {
+    DWORD dwBitMapInfoLength;
+    LPBITMAPINFO lpBitMapInfo;
+    DWORD dwUsage;
+    HANDLE hMutex;
+    PVOID lpBitMap;
+} CONSOLE_GRAPHICS_BUFFER_INFO, *PCONSOLE_GRAPHICS_BUFFER_INFO;
+
+#endif
+
+BOOL
+WINAPI
+InvalidateConsoleDIBits(
+    _In_ HANDLE hConsoleOutput,
+    _In_ PSMALL_RECT lpRect);
+
+VOID
+WINAPI
+SetLastConsoleEventActive(
+    VOID);
+
+#define VDM_HIDE_WINDOW         1
+#define VDM_IS_ICONIC           2
+#define VDM_CLIENT_RECT         3
+#define VDM_CLIENT_TO_SCREEN    4
+#define VDM_SCREEN_TO_CLIENT    5
+#define VDM_IS_HIDDEN           6
+#define VDM_FULLSCREEN_NOPAINT  7
+#define VDM_SET_VIDEO_MODE      8
+
+BOOL
+WINAPI
+VDMConsoleOperation(
+    _In_ DWORD iFunction,
+    _Inout_opt_ LPVOID lpData);
+
+
+BOOL
+WINAPI
+SetConsoleIcon(
+    _In_ HICON hIcon);
+
+//
+// These console font APIs don't appear to be used anywhere. Maybe they
+// should be removed.
+//
+
+BOOL
+WINAPI
+SetConsoleFont(
+    _In_ HANDLE hConsoleOutput,
+    _In_ DWORD nFont);
+
+DWORD
+WINAPI
+GetConsoleFontInfo(
+    _In_ HANDLE hConsoleOutput,
+    _In_ BOOL bMaximumWindow,
+    _In_ DWORD nLength,
+    _Out_ PCONSOLE_FONT_INFO lpConsoleFontInfo);
+
+DWORD
+WINAPI
+GetNumberOfConsoleFonts(
+    VOID);
+
+BOOL
+WINAPI
+SetConsoleCursor(
+    _In_ HANDLE hConsoleOutput,
+    _In_ HCURSOR hCursor);
+
+int
+WINAPI
+ShowConsoleCursor(
+    _In_ HANDLE hConsoleOutput,
+    _In_ BOOL bShow);
+
+HMENU
+APIENTRY
+ConsoleMenuControl(
+    _In_ HANDLE hConsoleOutput,
+    _In_ UINT dwCommandIdLow,
+    _In_ UINT dwCommandIdHigh);
+
+BOOL
+SetConsolePalette(
+    _In_ HANDLE hConsoleOutput,
+    _In_ HPALETTE hPalette,
+    _In_ UINT dwUsage);
+
+#define CONSOLE_UNREGISTER_VDM 0
+#define CONSOLE_REGISTER_VDM   1
+#define CONSOLE_REGISTER_WOW   2
+
+BOOL
+APIENTRY
+RegisterConsoleVDM(
+    _In_ DWORD dwRegisterFlags,
+    _In_ HANDLE hStartHardwareEvent,
+    _In_ HANDLE hEndHardwareEvent,
+    _In_ HANDLE hErrorhardwareEvent,
+    _Reserved_ DWORD Reserved,
+    _Out_ LPDWORD lpStateLength,
+    _Outptr_ PVOID *lpState,
+    _In_opt_ COORD VDMBufferSize,
+    _Outptr_ PVOID *lpVDMBuffer);
+
+BOOL
+APIENTRY
+GetConsoleHardwareState(
+    _In_ HANDLE hConsoleOutput,
+    _Out_ PCOORD lpResolution,
+    _Out_ PCOORD lpFontSize);
+
+BOOL
+APIENTRY
+SetConsoleHardwareState(
+    _In_ HANDLE hConsoleOutput,
+    _In_ COORD dwResolution,
+    _In_ COORD dwFontSize);
+
+#define CONSOLE_NOSHORTCUTKEY   0x00000000        /* no shortcut key  */
+#define CONSOLE_ALTTAB          0x00000001        /* Alt + Tab        */
+#define CONSOLE_ALTESC          0x00000002        /* Alt + Escape     */
+#define CONSOLE_ALTSPACE        0x00000004        /* Alt + Space      */
+#define CONSOLE_ALTENTER        0x00000008        /* Alt + Enter      */
+#define CONSOLE_ALTPRTSC        0x00000010        /* Alt Print screen */
+#define CONSOLE_PRTSC           0x00000020        /* Print screen     */
+#define CONSOLE_CTRLESC         0x00000040        /* Ctrl + Escape    */
+
+typedef struct _APPKEY {
+    WORD Modifier;
+    WORD ScanCode;
+} APPKEY, *LPAPPKEY;
+
+#define CONSOLE_MODIFIER_SHIFT      0x0003   // Left shift key
+#define CONSOLE_MODIFIER_CONTROL    0x0004   // Either Control shift key
+#define CONSOLE_MODIFIER_ALT        0x0008   // Either Alt shift key
+
+BOOL
+APIENTRY
+SetConsoleKeyShortcuts(
+    _In_ BOOL bSet,
+    _In_ BYTE bReserveKeys,
+    _In_reads_(dwNumAppKeys) LPAPPKEY lpAppKeys,
+    _In_ DWORD dwNumAppKeys);
+
+BOOL
+APIENTRY
+SetConsoleMenuClose(
+    _In_ BOOL bEnable);
+
+DWORD
+GetConsoleInputExeNameA(
+    _In_ DWORD nBufferLength,
+    _Out_writes_(nBufferLength) LPSTR lpBuffer);
+DWORD
+GetConsoleInputExeNameW(
+    _In_ DWORD nBufferLength,
+    _Out_writes_(nBufferLength) LPWSTR lpBuffer);
+#ifdef UNICODE
+#define GetConsoleInputExeName  GetConsoleInputExeNameW
+#else
+#define GetConsoleInputExeName  GetConsoleInputExeNameA
+#endif // !UNICODE
+
+BOOL
+SetConsoleInputExeNameA(
+    _In_ LPSTR lpExeName);
+BOOL
+SetConsoleInputExeNameW(
+    _In_ LPWSTR lpExeName);
+#ifdef UNICODE
+#define SetConsoleInputExeName  SetConsoleInputExeNameW
+#else
+#define SetConsoleInputExeName  SetConsoleInputExeNameA
+#endif // !UNICODE
+
+BOOL
+WINAPI
+ReadConsoleInputExA(
+    _In_ HANDLE hConsoleInput,
+    _Out_writes_(nLength) PINPUT_RECORD lpBuffer,
+    _In_ DWORD nLength,
+    _Out_ LPDWORD lpNumberOfEventsRead,
+    _In_ USHORT wFlags);
+BOOL
+WINAPI
+ReadConsoleInputExW(
+    _In_ HANDLE hConsoleInput,
+    _Out_writes_(nLength) PINPUT_RECORD lpBuffer,
+    _In_ DWORD nLength,
+    _Out_ LPDWORD lpNumberOfEventsRead,
+    _In_ USHORT wFlags);
+#ifdef UNICODE
+#define ReadConsoleInputEx  ReadConsoleInputExW
+#else
+#define ReadConsoleInputEx  ReadConsoleInputExA
+#endif // !UNICODE
+
+BOOL
+WINAPI
+WriteConsoleInputVDMA(
+    _In_ HANDLE hConsoleInput,
+    _In_reads_(nLength) PINPUT_RECORD lpBuffer,
+    _In_ DWORD nLength,
+    _Out_ LPDWORD lpNumberOfEventsWritten);
+BOOL
+WINAPI
+WriteConsoleInputVDMW(
+    _In_ HANDLE hConsoleInput,
+    _In_reads_(nLength) PINPUT_RECORD lpBuffer,
+    _In_ DWORD nLength,
+    _Out_ LPDWORD lpNumberOfEventsWritten);
+#ifdef UNICODE
+#define WriteConsoleInputVDM  WriteConsoleInputVDMW
+#else
+#define WriteConsoleInputVDM  WriteConsoleInputVDMA
+#endif // !UNICODE
+
+
+BOOL
+APIENTRY
+GetConsoleNlsMode(
+    _In_ HANDLE hConsole,
+    _Out_ PDWORD lpdwNlsMode);
+
+BOOL
+APIENTRY
+SetConsoleNlsMode(
+    _In_ HANDLE hConsole,
+    _In_ DWORD fdwNlsMode);
+
+BOOL
+APIENTRY
+GetConsoleCharType(
+    _In_ HANDLE hConsole,
+    _In_ COORD coordCheck,
+    _Out_ PDWORD pdwType);
+
+#define CHAR_TYPE_SBCS     0   // Displayed SBCS character
+#define CHAR_TYPE_LEADING  2   // Displayed leading byte of DBCS
+#define CHAR_TYPE_TRAILING 3   // Displayed trailing byte of DBCS
+
+BOOL
+APIENTRY
+SetConsoleLocalEUDC(
+    _In_ HANDLE hConsoleHandle,
+    _In_ WORD   wCodePoint,
+    _In_ COORD  cFontSize,
+    _In_ PCHAR  lpSB);
+
+BOOL
+APIENTRY
+SetConsoleCursorMode(
+    _In_ HANDLE hConsoleHandle,
+    _In_ BOOL   Blink,
+    _In_ BOOL   DBEnable);
+
+BOOL
+APIENTRY
+GetConsoleCursorMode(
+    _In_ HANDLE hConsoleHandle,
+    _Out_ PBOOL  pbBlink,
+    _Out_ PBOOL  pbDBEnable);
+
+BOOL
+APIENTRY
+RegisterConsoleOS2(
+    _In_ BOOL fOs2Register);
+
+BOOL
+APIENTRY
+SetConsoleOS2OemFormat(
+    _In_ BOOL fOs2OemFormat);
+
+BOOL
+IsConsoleFullWidth(
+    _In_ HDC hDC,
+    _In_ DWORD CodePage,
+    _In_ WCHAR wch);
+
+#if defined(FE_IME)
+BOOL
+APIENTRY
+RegisterConsoleIME(
+    _In_ HWND  hWndConsoleIME,
+    _Out_opt_ DWORD *lpdwConsoleThreadId);
+
+BOOL
+APIENTRY
+UnregisterConsoleIME(
+    VOID);
+#endif // FE_IME
+
+//
+// These bits are always on for console handles and are used for routing
+// by windows.
+//
+
+#define CONSOLE_HANDLE_SIGNATURE 0x00000003
+#define CONSOLE_HANDLE_NEVERSET  0x10000000
+#define CONSOLE_HANDLE_MASK      (CONSOLE_HANDLE_SIGNATURE | CONSOLE_HANDLE_NEVERSET)
+
+#define CONSOLE_HANDLE(HANDLE) (((ULONG_PTR)(HANDLE) & CONSOLE_HANDLE_MASK) == CONSOLE_HANDLE_SIGNATURE)
+
+//
+// These strings are used to open console input or output.
+//
+
+#define CONSOLE_INPUT_STRING  L"CONIN$"
+#define CONSOLE_OUTPUT_STRING L"CONOUT$"
+#define CONSOLE_GENERIC       L"CON"
+
+//
+// this string is used to call RegisterWindowMessage to get
+// progman's handle.
+//
+
+#define CONSOLE_PROGMAN_HANDLE_MESSAGE "ConsoleProgmanHandle"
+
+
+//
+// stream API definitions.  these API are only supposed to be used by
+// subsystems (i.e. OpenFile routes to OpenConsoleW).
+//
+
+HANDLE
+APIENTRY
+OpenConsoleW(
+    _In_ LPWSTR lpConsoleDevice,
+    _In_ DWORD dwDesiredAccess,
+    _In_ BOOL bInheritHandle,
+    _In_ DWORD dwShareMode);
+
+HANDLE
+APIENTRY
+DuplicateConsoleHandle(
+    _In_ HANDLE hSourceHandle,
+    _In_ DWORD dwDesiredAccess,
+    _In_ BOOL bInheritHandle,
+    _In_ DWORD dwOptions);
+
+BOOL
+APIENTRY
+GetConsoleHandleInformation(
+    _In_ HANDLE hObject,
+    _Out_ LPDWORD lpdwFlags);
+
+BOOL
+APIENTRY
+SetConsoleHandleInformation(
+    _In_ HANDLE hObject,
+    _In_ DWORD dwMask,
+    _In_ DWORD dwFlags);
+
+BOOL
+APIENTRY
+CloseConsoleHandle(
+    _In_ HANDLE hConsole);
+
+BOOL
+APIENTRY
+VerifyConsoleIoHandle(
+    _In_ HANDLE hIoHandle);
+
+HANDLE
+APIENTRY
+GetConsoleInputWaitHandle(
+    VOID);
+
+typedef struct _CONSOLE_STATE_INFO {
+    /* BEGIN V1 CONSOLE_STATE_INFO */
+    COORD ScreenBufferSize;
+    COORD WindowSize;
+    INT WindowPosX;
+    INT WindowPosY;
+    COORD FontSize;
+    UINT FontFamily;
+    UINT FontWeight;
+    WCHAR FaceName[LF_FACESIZE];
+    UINT CursorSize;
+    UINT FullScreen : 1;
+    UINT QuickEdit : 1;
+    UINT AutoPosition : 1;
+    UINT InsertMode : 1;
+    UINT HistoryNoDup : 1;
+    UINT FullScreenSupported : 1;
+    UINT UpdateValues : 1;
+    UINT Defaults : 1;
+    WORD ScreenAttributes;
+    WORD PopupAttributes;
+    UINT HistoryBufferSize;
+    UINT NumberOfHistoryBuffers;
+    COLORREF ColorTable[16];
+    HWND hWnd;
+    HICON hIcon;
+    LPWSTR OriginalTitle;
+    LPWSTR LinkTitle;
+
+    /*
+     * Starting code page
+     */
+    UINT CodePage;
+
+    /* END V1 CONSOLE_STATE_INFO */
+
+    /* BEGIN V2 CONSOLE_STATE_INFO */
+    BOOL fIsV2Console;
+    BOOL fWrapText;
+    BOOL fFilterOnPaste;
+    BOOL fCtrlKeyShortcutsDisabled;
+    BOOL fLineSelection;
+    BYTE bWindowTransparency;
+    BOOL fWindowMaximized;
+
+    unsigned int CursorType;
+    COLORREF CursorColor;
+
+    BOOL InterceptCopyPaste;
+
+    COLORREF DefaultForeground;
+    COLORREF DefaultBackground;
+    BOOL TerminalScrolling;
+    /* END V2 CONSOLE_STATE_INFO */
+
+} CONSOLE_STATE_INFO, *PCONSOLE_STATE_INFO;
+
+
+#ifdef DEFINE_CONSOLEV2_PROPERTIES
+#define PID_CONSOLE_FORCEV2                 1
+#define PID_CONSOLE_WRAPTEXT                2
+#define PID_CONSOLE_FILTERONPASTE           3
+#define PID_CONSOLE_CTRLKEYSDISABLED        4
+#define PID_CONSOLE_LINESELECTION           5
+#define PID_CONSOLE_WINDOWTRANSPARENCY      6
+#define PID_CONSOLE_WINDOWMAXIMIZED         7
+#define PID_CONSOLE_CURSOR_TYPE             8
+#define PID_CONSOLE_CURSOR_COLOR            9
+#define PID_CONSOLE_INTERCEPT_COPY_PASTE    10
+#define PID_CONSOLE_DEFAULTFOREGROUND       11
+#define PID_CONSOLE_DEFAULTBACKGROUND       12
+#define PID_CONSOLE_TERMINALSCROLLING       13
+
+#define CONSOLE_PROPKEY(name, id) \
+DEFINE_PROPERTYKEY(name, 0x0C570607, 0x0396, 0x43DE, 0x9D, 0x61, 0xE3, 0x21, 0xD7, 0xDF, 0x50, 0x26, id);
+
+CONSOLE_PROPKEY(PKEY_Console_ForceV2,                   PID_CONSOLE_FORCEV2);
+CONSOLE_PROPKEY(PKEY_Console_WrapText,                  PID_CONSOLE_WRAPTEXT);
+CONSOLE_PROPKEY(PKEY_Console_FilterOnPaste,             PID_CONSOLE_FILTERONPASTE);
+CONSOLE_PROPKEY(PKEY_Console_CtrlKeyShortcutsDisabled,  PID_CONSOLE_CTRLKEYSDISABLED);
+CONSOLE_PROPKEY(PKEY_Console_LineSelection,             PID_CONSOLE_LINESELECTION);
+CONSOLE_PROPKEY(PKEY_Console_WindowTransparency,        PID_CONSOLE_WINDOWTRANSPARENCY);
+CONSOLE_PROPKEY(PKEY_Console_WindowMaximized,           PID_CONSOLE_WINDOWMAXIMIZED);
+CONSOLE_PROPKEY(PKEY_Console_CursorType,                PID_CONSOLE_CURSOR_TYPE);
+CONSOLE_PROPKEY(PKEY_Console_CursorColor,               PID_CONSOLE_CURSOR_COLOR);
+CONSOLE_PROPKEY(PKEY_Console_InterceptCopyPaste,        PID_CONSOLE_INTERCEPT_COPY_PASTE);
+CONSOLE_PROPKEY(PKEY_Console_DefaultForeground,         PID_CONSOLE_DEFAULTFOREGROUND);
+CONSOLE_PROPKEY(PKEY_Console_DefaultBackground,         PID_CONSOLE_DEFAULTBACKGROUND);
+CONSOLE_PROPKEY(PKEY_Console_TerminalScrolling,         PID_CONSOLE_TERMINALSCROLLING);
+#endif
+
+
+//
+// Ensure the alignment is WORD boundary
+//
+
+#include <pshpack2.h>
+
+typedef struct {
+    WORD wMod;
+    WORD wVirKey;
+    WCHAR wUnicodeChar;
+} ExtKeySubst;
+
+typedef struct {
+    ExtKeySubst keys[3];    // 0: Ctrl
+                            // 1: Alt
+                            // 2: Ctrl+Alt
+} ExtKeyDef;
+
+typedef ExtKeyDef ExtKeyDefTable['Z' - 'A' + 1];
+
+typedef struct {
+    DWORD dwVersion;
+    DWORD dwCheckSum;
+    ExtKeyDefTable table;
+} ExtKeyDefBuf;
+
+//
+// Restore the previous alignment
+//
+
+#include <poppack.h>
+
+
+#if _MSC_VER >= 1200
+#pragma warning(pop)
+#endif
+
+#ifdef __cplusplus
+}
+#endif
+
+#endif // _WINCONP_

dep/NT/ntioapi_x.h

@@ -0,0 +1,3 @@
+#pragma once
+
+#define FILE_SYNCHRONOUS_IO_NONALERT            0x00000020

dep/Win32K/winuserp.h

@@ -0,0 +1,12 @@
+/*
+ * Reserved console space.
+ *
+ * This was moved from the console code so that we can localize it
+ * in one place.  This was necessary for dealing with the background
+ * color, which we need to have for the hungapp drawing.  These are
+ * stored in the extra-window-bytes of each console.
+ */
+#define GWL_CONSOLE_WNDALLOC  (3 * sizeof(DWORD))
+#define GWL_CONSOLE_PID       0
+#define GWL_CONSOLE_TID       4
+#define GWL_CONSOLE_BKCOLOR   8

dep/WinAppDriver/EULA.rtf

@@ -0,0 +1,96 @@
+{\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Tahoma;}{\f1\fswiss\fprq2\fcharset0 Arial;}{\f2\fnil\fcharset0 Calibri;}}
+{\colortbl ;\red0\green0\blue255;}
+{\stylesheet{ Normal;}{\s1 heading 1;}{\s2 heading 2;}}
+{\*\generator Riched20 10.0.10586}\viewkind4\uc1 
+\pard\widctlpar\sb120\sa120\b\f0\fs28 MICROSOFT SOFTWARE LICENSE TERMS\par
+
+\pard\brdrb\brdrs\brdrw10\brsp20 \widctlpar\sb120\sa120 Pre-Release and Evaluation EULA \endash  Windows Application Driver\par
+
+\pard\widctlpar\sb120\sa120\b0\fs20 IF YOU LIVE IN (OR ARE A BUSINESS WITH YOUR PRINCIPAL PLACE OF BUSINESS IN) THE UNITED STATES, PLEASE READ THE \ldblquote BINDING ARBITRATION AND CLASS ACTION WAIVER\rdblquote  SECTION BELOW. IT AFFECTS HOW DISPUTES ARE RESOLVED.\lang9\par
+
+\pard\brdrt\brdrs\brdrw10\brsp20 \widctlpar\sb120\sa120 These license terms are an agreement between you and Microsoft Corporation (or one of its affiliates). They apply to the software named above and any Microsoft services or software updates (except to the extent such services or updates are accompanied by new or \lang1033 additional terms, in which case those different terms apply prospectively and do not alter your or Microsoft\rquote s rights relating to pre-updated software or services\lang9 ). IF YOU COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE RIGHTS BELOW.\par
+
+\pard 
+{\pntext\f0 1.\tab}{\*\pn\pnlvlbody\pnf0\pnindent360\pnstart1\pndec{\pntxta.}}
+\widctlpar\s1\fi-357\li357\sb120\sa120\b\lang1033 INSTALLATION AND USE RIGHTS.\par
+
+\pard 
+{\pntext\f0 a)\tab}{\*\pn\pnlvlbody\pnf0\pnindent0\pnstart1\pnlcltr{\pntxta)}}
+\widctlpar\s2\fi-360\li717\sb120\sa120 General. \b0 You may install and use any number of copies of the software on your devices, solely to i) evaluate for internal business purposes; and ii) design, develop and test your applications. \par
+{\pntext\f0 b)\tab}\b Included Microsoft Applications. \b0 The software may include other Microsoft applications. These license terms apply to those included applications, if any, unless other license terms are provided with the other Microsoft applications.\par
+{\pntext\f0 c)\tab}\b Third Party Applications. \b0 The software may include third party applications that Microsoft, not the third party, licenses to you under this agreement. Any included notices for third party applications are for your information only and are listed in Exhibit A to these license terms.\par
+{\pntext\f0 d)\tab}\b No Distribution Rights.  \b0 This agreement does not grant you a license to distribute nor sublicense all or part of the software to any third party.\par
+{\pntext\f0 e)\tab}\b\lang9 Package Managers. \b0\lang1033 The software may include package managers, like NuGet, that give you the option to download other Microsoft and third party software packages to use with your application. Those packages are under their own licenses, and not this agreement. Microsoft does not distribute, license or provide any warranties for any of the third party packages\lang9 .\lang1033\par
+
+\pard\widctlpar\s1\fi-357\li357\sb120\sa120\b 2.\tab TIME-SENSITIVE SOFTWARE.\par
+
+\pard 
+{\pntext\f0 a)\tab}{\*\pn\pnlvlbody\pnf0\pnindent0\pnstart1\pnlcltr{\pntxta)}}
+\widctlpar\s2\fi-360\li717\sb120\sa120 Period. \b0 The software is time-sensitive and may stop running on a date that is defined in the software.\par
+{\pntext\f0 b)\tab}\b Notice. \b0 You may receive periodic reminder notices of this date through the software.\par
+{\pntext\f0 c)\tab}\b Access to data. \b0 You may not be able to access data used in the software when it stops running.\par
+
+\pard\widctlpar\s1\fi-357\li357\sb120\sa120\b 3.\tab PRE-RELEASE SOFTWARE.\b0  The software is a pre-release version. It may not operate correctly. It may be different from the commercially released version.\par
+\b 4.\tab FEEDBACK.\b0  If you give feedback about the software to Microsoft, you give to Microsoft, without charge, the right to use, share and commercialize your feedback in any way and for any purpose. You will not give feedback that is subject to a license that requires Microsoft to license its software or documentation to third parties because Microsoft includes your feedback in them. These rights survive this agreement.\par
+\b 5.\tab DATA.\b0  The software may collect information about you and your use of the software and send that to Microsoft. Microsoft may use this information to provide services and improve Microsoft\rquote s products and services. Your opt-out rights, if any, are described in\b  \b0 the product documentation. Some features in the software may enable collection of data from users of your applications that access or use the software. If you use these features to enable data collection in your applications, you must comply with applicable law, including getting any required user consent, and maintain a prominent privacy policy that accurately informs users about how you use, collect, and share their data. You can learn more about Microsoft\rquote s data collection and use in the product documentation and the Microsoft Privacy Statement at {{\field{\*\fldinst{HYPERLINK http://go.microsoft.com/fwlink/?LinkID=521839 }}{\fldrslt{http://go.microsoft.com/fwlink/?LinkID=521839\ul0\cf0}}}}\f0\fs20 . You agree to comply with all applicable provisions of the Microsoft Privacy Statement.\par
+\b 6.\tab SCOPE OF LICENSE.\b0  The software is licensed, not sold. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you will not (and have no right to):\par
+
+\pard 
+{\pntext\f0 a)\tab}{\*\pn\pnlvlbody\pnf0\pnindent0\pnstart1\pnlcltr{\pntxta)}}
+\widctlpar\s2\fi-360\li717\sb120\sa120 work around any technical limitations in the software that only allow you to use it in certain ways;\par
+{\pntext\f0 b)\tab}reverse engineer, decompile or disassemble the software;\par
+{\pntext\f0 c)\tab}remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software;\par
+{\pntext\f0 d)\tab}use the software in any way that is against the law or to create or propagate malware; or\par
+{\pntext\f0 e)\tab}share, publish, or lend the software (except for any distributable code, and then subject to the applicable terms above), provide the software as a stand-alone hosted solution for others to use, or transfer the software or this agreement to any third party.\par
+
+\pard\widctlpar\s1\fi-357\li357\sb120\sa120\b 7.\tab EXPORT RESTRICTIONS.\b0  You must comply with all domestic and international export laws and regulations that apply to the software, which include restrictions on destinations, end users, and end use. For further information on export restrictions, visit (aka.ms/exporting).\par
+\b 8.\tab SUPPORT SERVICES.\b0  Microsoft is not obligated under this agreement to provide any support services for the software. Any support provided is \ldblquote as is\rdblquote , \ldblquote with all faults\rdblquote , and without warranty of any kind.\par
+\b 9.\tab UPDATES.\b0  The software may periodically check for updates, and download and install them for you. You may obtain updates only from Microsoft or authorized sources. Microsoft may need to update your system to provide you with updates. You agree to receive these automatic updates without any additional notice. Updates may not include or support all existing software features, services, or peripheral devices.\par
+\b 10.\tab BINDING ARBITRATION AND CLASS ACTION WAIVER.\b0  This Section applies if you live in (or, if a business, your principal place of business is in) the United States.  If you and Microsoft have a dispute, you and Microsoft agree to try for 60 days to resolve it informally. If you and Microsoft can\rquote t, you and Microsoft agree to binding individual arbitration before the American Arbitration Association under the Federal Arbitration Act (\ldblquote FAA\rdblquote ), and not to sue in court in front of a judge or jury. Instead, a neutral arbitrator will decide. Class action lawsuits, class-wide arbitrations, private attorney-general actions, and any other proceeding where someone acts in a representative capacity are not allowed; nor is combining individual proceedings without the consent of all parties. The complete Arbitration Agreement contains more terms and is at aka.ms/arb-agreement-1. You and Microsoft agree to these terms.\par
+\b 11.\tab ENTIRE AGREEMENT.\b0  This agreement, and any other terms Microsoft may provide for supplements, updates, or third-party applications, is the entire agreement for the software.\par
+\b 12.\tab APPLICABLE LAW AND PLACE TO RESOLVE DISPUTES.\b0  If you acquired the software in the United States or Canada, the laws of the state or province where you live (or, if a business, where your principal place of business is located) govern the interpretation of this agreement, claims for its breach, and all other claims (including consumer protection, unfair competition, and tort claims), regardless of conflict of laws principles, except that the FAA governs everything related to arbitration. If you acquired the software in any other country, its laws apply, except that the FAA governs everything related to arbitration. If U.S. federal jurisdiction exists, you and Microsoft consent to exclusive jurisdiction and venue in the federal court in King County, Washington for all disputes heard in court (excluding arbitration). If not, you and Microsoft consent to exclusive jurisdiction and venue in the Superior Court of King County, Washington for all disputes heard in court (excluding arbitration).\par
+\b 13.\tab CONSUMER RIGHTS; REGIONAL VARIATIONS\b0 . This agreement describes certain legal rights. You may have other rights, including consumer rights, under the laws of your state, province, or country. Separate and apart from your relationship with Microsoft, you may also have rights with respect to the party from which you acquired the software. This agreement does not change those other rights if the laws of your state, province, or country do not permit it to do so. For example, if you acquired the software in one of the below regions, or mandatory country law applies, then the following provisions apply to you:\par
+
+\pard 
+{\pntext\f0 a)\tab}{\*\pn\pnlvlbody\pnf0\pnindent0\pnstart1\pnlcltr{\pntxta)}}
+\widctlpar\s2\fi-360\li717\sb120\sa120\b Australia.\b0  You have statutory guarantees under the Australian Consumer Law and nothing in this agreement is intended to affect those rights.\par
+{\pntext\f0 b)\tab}\b Canada.\b0  If you acquired this software in Canada, you may stop receiving updates by turning off the automatic update feature, disconnecting your device from the Internet (if and when you re-connect to the Internet, however, the software will resume checking for and installing updates), or uninstalling the software. The product documentation, if any, may also specify how to turn off updates for your specific device or software.\par
+{\pntext\f0 c)\tab}\b Germany and Austria\b0 .\par
+
+\pard\widctlpar\li717\sb120\sa120\b (i)\b0\tab\b Warranty.\b0  The properly licensed software will perform substantially as described in any Microsoft materials that accompany the software. However, Microsoft gives no contractual guarantee in relation to the licensed software.\par
+\b (ii)\b0\tab\b Limitation of Liability\b0 . In case of intentional conduct, gross negligence, claims based on the Product Liability Act, as well as, in case of death or personal or physical injury, Microsoft is liable according to the statutory law.\par
+
+\pard\widctlpar\s1\li717\sb120\sa120 Subject to the foregoing clause (ii), Microsoft will only be liable for slight negligence if Microsoft is in breach of such material contractual obligations, the fulfillment of which facilitate the due performance of this agreement, the breach of which would endanger the purpose of this agreement and the compliance with which a party may constantly trust in (so-called "cardinal obligations"). In other cases of slight negligence, Microsoft will not be liable for slight negligence.\par
+
+\pard\widctlpar\s1\fi-357\li357\sb120\sa120\b 14.\tab DISCLAIMER OF WARRANTY.\b0  \b THE SOFTWARE IS LICENSED \ldblquote AS IS.\rdblquote  YOU BEAR THE RISK OF USING IT. MICROSOFT GIVES NO EXPRESS WARRANTIES, GUARANTEES, OR CONDITIONS. TO THE EXTENT PERMITTED UNDER APPLICABLE LAWS, MICROSOFT EXCLUDES ALL IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.\b0\par
+\b 15.\tab LIMITATION ON AND EXCLUSION OF DAMAGES. IF YOU HAVE ANY BASIS FOR RECOVERING DAMAGES DESPITE THE PRECEDING DISCLAIMER OF WARRANTY, YOU CAN RECOVER FROM MICROSOFT AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP TO U.S. $5.00. YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL, LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.\par
+
+\pard\widctlpar\li357\sb120\sa120\b0 This limitation applies to (a) anything related to the software, services, content (including code) on third party Internet sites, or third party applications; and (b) claims for breach of contract, warranty, guarantee, or condition; strict liability, negligence, or other tort; or any other claim; in each case to the extent permitted by applicable law.\par
+It also applies even if Microsoft knew or should have known about the possibility of the damages. The above limitation or exclusion may not apply to you because your state, province, or country may not allow the exclusion or limitation of incidental, consequential, or other damages.\par
+
+\pard\widctlpar\sb120\sa120\page\par
+
+\pard\widctlpar\sb120\sa120\qc EXHIBIT A\par
+THIRD PARTY NOTICES AND INFORMATION\par
+FOR\par
+MICROSOFT WINDOWS APPLICATION DRIVER\par
+
+\pard\widctlpar\sb120\sa120\par
+THIRD-PARTY SOFTWARE NOTICES AND INFORMATION\line\line Note:  While Microsoft is not the author of the files below, Microsoft is offering you a license subject to the terms of the Microsoft Software License Terms for Microsoft Windows Application Driver (the \ldblquote Microsoft Program\rdblquote ). Microsoft reserves all other rights. The notices below are provided for informational purposes only and are not the license terms under which Microsoft distributes these files.\par
+The Microsoft Program includes the following third-party software:\par
+1.\tab Newtonsoft.json version 7.0. ({\b{\field{\*\fldinst{HYPERLINK http://www.newtonsoft.com/json }}{\fldrslt{http://www.newtonsoft.com/json\ul0\cf0}}}}\f0\fs20 )\par
+2.\tab Casablanca ({{\field{\*\fldinst{HYPERLINK http://casablanca.codeplex.com/ }}{\fldrslt{http://casablanca.codeplex.com/\ul0\cf0}}}}\f0\fs20 )\par
+As the recipient of the above third-party software, Microsoft sets forth a copy of the notices and other information below.\par
+1. Newtonsoft.json version 7.0.1 ({{\field{\*\fldinst{HYPERLINK http://www.newtonsoft.com/json }}{\fldrslt{http://www.newtonsoft.com/json\ul0\cf0}}}}\f0\fs20 )\par
+NEWTONSOFT.JSON NOTICES AND INFORMATION BEGIN HERE\line =========================================\par
+The MIT License (MIT)\line\line Copyright (c) 2007 James Newton-King\line\line Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:\line\line The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.\line\line THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\par
+NEWTONSOFT.JSON NOTICES AND INFORMATION END HERE\line =========================================\par
+2. Casablanca ({{\field{\*\fldinst{HYPERLINK http://casablanca.codeplex.com/ }}{\fldrslt{http://casablanca.codeplex.com/\ul0\cf0}}}}\f0\fs20 )\par
+CASABLANCA NOTICES AND INFORMATION BEGIN HERE\line =========================================\par
+Copyright (c) Microsoft Corporation. All rights reserved. \line Licensed under the Apache License, Version 2.0 (the "License");\line you may not use this file except in compliance with the License.\line You may obtain a copy of the License at\line {{\field{\*\fldinst{HYPERLINK http://www.apache.org/licenses/LICENSE-2.0 }}{\fldrslt{http://www.apache.org/licenses/LICENSE-2.0\ul0\cf0}}}}\f0\fs20\line\line Unless required by applicable law or agreed to in writing, software\line\f1\fs19 distributed under the License is distributed on an "AS IS" BASIS,\line WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\line See the License for the specific language governing permissions and\line limitations under the License.\fs20\par
+\f0 CASABLANCA NOTICES AND INFORMATION END HERE\line =========================================\par
+\par
+
+\pard\sa200\sl276\slmult1\f2\fs22\lang9\par
+}
+

dep/WinAppDriver/Readme.txt

@@ -0,0 +1,7 @@
+Windows Application Driver (Beta)
+
+For documentation, sample code, and logging issues: 
+https://github.com/Microsoft/WinAppDriver
+
+To request new features and upvote requests filed by others: 
+https://wpdev.uservoice.com

dep/jsoncpp/README.md

@@ -0,0 +1,7 @@
+# jsoncpp
+
+[Amalgamated](https://github.com/open-source-parsers/jsoncpp/wiki/Amalgamated)
+from source commit
+[ddabf50](https://github.com/open-source-parsers/jsoncpp/commit/ddabf50f72cf369bf652a95c4d9fe31a1865a781),
+release 1.8.4.
+

dep/jsoncpp/json/json-forwards.h

@@ -0,0 +1,333 @@
+/// Json-cpp amalgamated forward header (http://jsoncpp.sourceforge.net/).
+/// It is intended to be used with #include "json/json-forwards.h"
+/// This header provides forward declaration for all JsonCpp types.
+
+// //////////////////////////////////////////////////////////////////////
+// Beginning of content of file: LICENSE
+// //////////////////////////////////////////////////////////////////////
+
+/*
+The JsonCpp library's source code, including accompanying documentation, 
+tests and demonstration applications, are licensed under the following
+conditions...
+
+Baptiste Lepilleur and The JsonCpp Authors explicitly disclaim copyright in all 
+jurisdictions which recognize such a disclaimer. In such jurisdictions, 
+this software is released into the Public Domain.
+
+In jurisdictions which do not recognize Public Domain property (e.g. Germany as of
+2010), this software is Copyright (c) 2007-2010 by Baptiste Lepilleur and
+The JsonCpp Authors, and is released under the terms of the MIT License (see below).
+
+In jurisdictions which recognize Public Domain property, the user of this 
+software may choose to accept it either as 1) Public Domain, 2) under the 
+conditions of the MIT License (see below), or 3) under the terms of dual 
+Public Domain/MIT License conditions described here, as they choose.
+
+The MIT License is about as close to Public Domain as a license can get, and is
+described in clear, concise terms at:
+
+   http://en.wikipedia.org/wiki/MIT_License
+   
+The full text of the MIT License follows:
+
+========================================================================
+Copyright (c) 2007-2010 Baptiste Lepilleur and The JsonCpp Authors
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use, copy,
+modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
+BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
+ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+========================================================================
+(END LICENSE TEXT)
+
+The MIT license is compatible with both the GPL and commercial
+software, affording one all of the rights of Public Domain with the
+minor nuisance of being required to keep the above copyright notice
+and license text in the source code. Note also that by accepting the
+Public Domain "license" you can re-license your copy using whatever
+license you like.
+
+*/
+
+// //////////////////////////////////////////////////////////////////////
+// End of content of file: LICENSE
+// //////////////////////////////////////////////////////////////////////
+
+
+
+
+
+#ifndef JSON_FORWARD_AMALGAMATED_H_INCLUDED
+# define JSON_FORWARD_AMALGAMATED_H_INCLUDED
+/// If defined, indicates that the source file is amalgamated
+/// to prevent private header inclusion.
+#define JSON_IS_AMALGAMATION
+
+// //////////////////////////////////////////////////////////////////////
+// Beginning of content of file: include/json/config.h
+// //////////////////////////////////////////////////////////////////////
+
+// Copyright 2007-2010 Baptiste Lepilleur and The JsonCpp Authors
+// Distributed under MIT license, or public domain if desired and
+// recognized in your jurisdiction.
+// See file LICENSE for detail or copy at http://jsoncpp.sourceforge.net/LICENSE
+
+#ifndef JSON_CONFIG_H_INCLUDED
+#define JSON_CONFIG_H_INCLUDED
+#include <stddef.h>
+#include <string> //typedef String
+#include <stdint.h> //typedef int64_t, uint64_t
+
+/// If defined, indicates that json library is embedded in CppTL library.
+//# define JSON_IN_CPPTL 1
+
+/// If defined, indicates that json may leverage CppTL library
+//#  define JSON_USE_CPPTL 1
+/// If defined, indicates that cpptl vector based map should be used instead of
+/// std::map
+/// as Value container.
+//#  define JSON_USE_CPPTL_SMALLMAP 1
+
+// If non-zero, the library uses exceptions to report bad input instead of C
+// assertion macros. The default is to use exceptions.
+#ifndef JSON_USE_EXCEPTION
+#define JSON_USE_EXCEPTION 1
+#endif
+
+/// If defined, indicates that the source file is amalgamated
+/// to prevent private header inclusion.
+/// Remarks: it is automatically defined in the generated amalgamated header.
+// #define JSON_IS_AMALGAMATION
+
+#ifdef JSON_IN_CPPTL
+#include <cpptl/config.h>
+#ifndef JSON_USE_CPPTL
+#define JSON_USE_CPPTL 1
+#endif
+#endif
+
+#ifdef JSON_IN_CPPTL
+#define JSON_API CPPTL_API
+#elif defined(JSON_DLL_BUILD)
+#if defined(_MSC_VER) || defined(__MINGW32__)
+#define JSON_API __declspec(dllexport)
+#define JSONCPP_DISABLE_DLL_INTERFACE_WARNING
+#endif // if defined(_MSC_VER)
+#elif defined(JSON_DLL)
+#if defined(_MSC_VER) || defined(__MINGW32__)
+#define JSON_API __declspec(dllimport)
+#define JSONCPP_DISABLE_DLL_INTERFACE_WARNING
+#endif // if defined(_MSC_VER)
+#endif // ifdef JSON_IN_CPPTL
+#if !defined(JSON_API)
+#define JSON_API
+#endif
+
+// If JSON_NO_INT64 is defined, then Json only support C++ "int" type for
+// integer
+// Storages, and 64 bits integer support is disabled.
+// #define JSON_NO_INT64 1
+
+#if defined(_MSC_VER) // MSVC
+#  if _MSC_VER <= 1200 // MSVC 6
+    // Microsoft Visual Studio 6 only support conversion from __int64 to double
+    // (no conversion from unsigned __int64).
+#    define JSON_USE_INT64_DOUBLE_CONVERSION 1
+    // Disable warning 4786 for VS6 caused by STL (identifier was truncated to '255'
+    // characters in the debug information)
+    // All projects I've ever seen with VS6 were using this globally (not bothering
+    // with pragma push/pop).
+#    pragma warning(disable : 4786)
+#  endif // MSVC 6
+
+#  if _MSC_VER >= 1500 // MSVC 2008
+    /// Indicates that the following function is deprecated.
+#    define JSONCPP_DEPRECATED(message) __declspec(deprecated(message))
+#  endif
+
+#endif // defined(_MSC_VER)
+
+// In c++11 the override keyword allows you to explicitly define that a function
+// is intended to override the base-class version.  This makes the code more
+// managable and fixes a set of common hard-to-find bugs.
+#if __cplusplus >= 201103L
+# define JSONCPP_OVERRIDE override
+# define JSONCPP_NOEXCEPT noexcept
+#elif defined(_MSC_VER) && _MSC_VER > 1600 && _MSC_VER < 1900
+# define JSONCPP_OVERRIDE override
+# define JSONCPP_NOEXCEPT throw()
+#elif defined(_MSC_VER) && _MSC_VER >= 1900
+# define JSONCPP_OVERRIDE override
+# define JSONCPP_NOEXCEPT noexcept
+#else
+# define JSONCPP_OVERRIDE
+# define JSONCPP_NOEXCEPT throw()
+#endif
+
+#ifndef JSON_HAS_RVALUE_REFERENCES
+
+#if defined(_MSC_VER) && _MSC_VER >= 1600 // MSVC >= 2010
+#define JSON_HAS_RVALUE_REFERENCES 1
+#endif // MSVC >= 2010
+
+#ifdef __clang__
+#if __has_feature(cxx_rvalue_references)
+#define JSON_HAS_RVALUE_REFERENCES 1
+#endif  // has_feature
+
+#elif defined __GNUC__ // not clang (gcc comes later since clang emulates gcc)
+#if defined(__GXX_EXPERIMENTAL_CXX0X__) || (__cplusplus >= 201103L)
+#define JSON_HAS_RVALUE_REFERENCES 1
+#endif  // GXX_EXPERIMENTAL
+
+#endif // __clang__ || __GNUC__
+
+#endif // not defined JSON_HAS_RVALUE_REFERENCES
+
+#ifndef JSON_HAS_RVALUE_REFERENCES
+#define JSON_HAS_RVALUE_REFERENCES 0
+#endif
+
+#ifdef __clang__
+#  if __has_extension(attribute_deprecated_with_message)
+#    define JSONCPP_DEPRECATED(message)  __attribute__ ((deprecated(message)))
+#  endif
+#elif defined __GNUC__ // not clang (gcc comes later since clang emulates gcc)
+#  if (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 5))
+#    define JSONCPP_DEPRECATED(message)  __attribute__ ((deprecated(message)))
+#  elif (__GNUC__ > 3 || (__GNUC__ == 3 && __GNUC_MINOR__ >= 1))
+#    define JSONCPP_DEPRECATED(message)  __attribute__((__deprecated__))
+#  endif  // GNUC version
+#endif // __clang__ || __GNUC__
+
+#if !defined(JSONCPP_DEPRECATED)
+#define JSONCPP_DEPRECATED(message)
+#endif // if !defined(JSONCPP_DEPRECATED)
+
+#if __GNUC__ >= 6
+#  define JSON_USE_INT64_DOUBLE_CONVERSION 1
+#endif
+
+#if !defined(JSON_IS_AMALGAMATION)
+
+# include "version.h"
+
+# if JSONCPP_USING_SECURE_MEMORY
+#  include "allocator.h" //typedef Allocator
+# endif
+
+#endif // if !defined(JSON_IS_AMALGAMATION)
+
+namespace Json {
+typedef int Int;
+typedef unsigned int UInt;
+#if defined(JSON_NO_INT64)
+typedef int LargestInt;
+typedef unsigned int LargestUInt;
+#undef JSON_HAS_INT64
+#else                 // if defined(JSON_NO_INT64)
+// For Microsoft Visual use specific types as long long is not supported
+#if defined(_MSC_VER) // Microsoft Visual Studio
+typedef __int64 Int64;
+typedef unsigned __int64 UInt64;
+#else                 // if defined(_MSC_VER) // Other platforms, use long long
+typedef int64_t Int64;
+typedef uint64_t UInt64;
+#endif // if defined(_MSC_VER)
+typedef Int64 LargestInt;
+typedef UInt64 LargestUInt;
+#define JSON_HAS_INT64
+#endif // if defined(JSON_NO_INT64)
+#if JSONCPP_USING_SECURE_MEMORY
+#define JSONCPP_STRING        std::basic_string<char, std::char_traits<char>, Json::SecureAllocator<char> >
+#define JSONCPP_OSTRINGSTREAM std::basic_ostringstream<char, std::char_traits<char>, Json::SecureAllocator<char> >
+#define JSONCPP_OSTREAM       std::basic_ostream<char, std::char_traits<char>>
+#define JSONCPP_ISTRINGSTREAM std::basic_istringstream<char, std::char_traits<char>, Json::SecureAllocator<char> >
+#define JSONCPP_ISTREAM       std::istream
+#else
+#define JSONCPP_STRING        std::string
+#define JSONCPP_OSTRINGSTREAM std::ostringstream
+#define JSONCPP_OSTREAM       std::ostream
+#define JSONCPP_ISTRINGSTREAM std::istringstream
+#define JSONCPP_ISTREAM       std::istream
+#endif // if JSONCPP_USING_SECURE_MEMORY
+} // end namespace Json
+
+#endif // JSON_CONFIG_H_INCLUDED
+
+// //////////////////////////////////////////////////////////////////////
+// End of content of file: include/json/config.h
+// //////////////////////////////////////////////////////////////////////
+
+
+
+
+
+
+// //////////////////////////////////////////////////////////////////////
+// Beginning of content of file: include/json/forwards.h
+// //////////////////////////////////////////////////////////////////////
+
+// Copyright 2007-2010 Baptiste Lepilleur and The JsonCpp Authors
+// Distributed under MIT license, or public domain if desired and
+// recognized in your jurisdiction.
+// See file LICENSE for detail or copy at http://jsoncpp.sourceforge.net/LICENSE
+
+#ifndef JSON_FORWARDS_H_INCLUDED
+#define JSON_FORWARDS_H_INCLUDED
+
+#if !defined(JSON_IS_AMALGAMATION)
+#include "config.h"
+#endif // if !defined(JSON_IS_AMALGAMATION)
+
+namespace Json {
+
+// writer.h
+class FastWriter;
+class StyledWriter;
+
+// reader.h
+class Reader;
+
+// features.h
+class Features;
+
+// value.h
+typedef unsigned int ArrayIndex;
+class StaticString;
+class Path;
+class PathArgument;
+class Value;
+class ValueIteratorBase;
+class ValueIterator;
+class ValueConstIterator;
+
+} // namespace Json
+
+#endif // JSON_FORWARDS_H_INCLUDED
+
+// //////////////////////////////////////////////////////////////////////
+// End of content of file: include/json/forwards.h
+// //////////////////////////////////////////////////////////////////////
+
+
+
+
+
+#endif //ifndef JSON_FORWARD_AMALGAMATED_H_INCLUDED

dep/telemetry/ProjectTelemetry.h

@@ -0,0 +1,17 @@
+/*++
+Copyright (c) Microsoft Corporation
+Licensed under the MIT license.
+
+Module Name:
+- ProjectTelemetry.h
+
+Abstract:
+- This module is used for basic definitions for telemetry for the entire project
+--*/
+
+#define TraceLoggingOptionMicrosoftTelemetry() TraceLoggingOptionGroup(0x9aa7a361, 0x583f, 0x4c09, 0xb1, 0xf1, 0xce, 0xa1, 0xef, 0x58, 0x63, 0xb0)
+#define TelemetryPrivacyDataTag(tag) TraceLoggingUInt64((tag), "PartA_PrivTags")
+#define PDT_ProductAndServicePerformance       0x0u
+#define PDT_ProductAndServiceUsage             0x0u
+#define MICROSOFT_KEYWORD_TELEMETRY     0x0
+#define MICROSOFT_KEYWORD_MEASURES      0x0

dirs

@@ -0,0 +1,3 @@
+DIRS=\
+     src 
+

doc/AddASetting.md

@@ -0,0 +1,40 @@
+# Adding a Settings Property
+
+1. Add to wincon.w
+    * THIS IS NOT IN OPENCONSOLE. Make sure you update
+      `.../console/published/wincon.w` in the OS repo when you submit the PR.
+      The branch won't build without it.
+    * For now, you can update winconp.h with your consumable changes.
+    * define registry name (ex `CONSOLE_REGISTRY_CURSORCOLOR`)
+    * add the setting to `CONSOLE_STATE_INFO`
+    * define the property key ID and the property key itself
+        - Yes, the large majority of the `DEFINE_PROPERTYKEY` defs are the same, it's only the last byte of the guid that changes
+
+2. Add matching fields to Settings.hpp
+    - add getters, setters, the whole drill.
+
+3. Add to the propsheet
+    - We need to add it to *reading and writing* the registry from the propsheet, and *reading* the link from the propsheet. Yes, that's weird, but the propsheet is smart enough to re-use ShortcutSerialization::s_SetLinkValues, but not smart enough to do the same with RegistrySerialization.
+    - `src/propsheet/registry.cpp`
+        -  `propsheet/registry.cpp@InitRegistryValues` should initialize the default value for the property.
+        -  `propsheet/registry.cpp@GetRegistryValues` should make sure to read the property from the registry
+
+4. Add the field to the propslib registry map
+
+5. Add the value to `ShortcutSerialization.cpp`
+    - Read the value in `ShortcutSerialization::s_PopulateV2Properties`
+    - Write the value in `ShortcutSerialization::s_SetLinkValues`
+
+6. Add the setting to `Menu::s_GetConsoleState`, and `Menu::s_PropertiesUpdate`
+Now, your new setting should be stored just like all the other properties.
+
+7. Update the feature test properties to get add the setting as well
+    - `ft_uia/Common/NativeMethods.cs@WinConP`:
+        - `Wtypes.PROPERTYKEY PKEY_Console_`
+        - `NT_CONSOLE_PROPS`
+
+8. Add the default value for the setting to `win32k-settings.man`
+    - If the setting shouldn't default to 0 or `nullptr`, then you'll need to set the default value of the setting in `win32k-settings.man`.
+
+9. Update `Settings::InitFromStateInfo` and `Settings::CreateConsoleStateInfo` to get/set the value in a CONSOLE_STATE_INFO appropriately
+

doc/ConsoleCtrlEvent.md

@@ -0,0 +1,22 @@
+# Console Control Events
+
+## Generation
+
+conhost requests that user32 injects a thread into the attached console application.
+See ntuser's exitwin.c for `CreateCtrlThread`.
+
+## Timeouts
+
+_Sourced from ntuser's **exitwin.c**, **user.h**_
+
+| Event                  | Circumstances                   | Timeout                                                     |
+|------------------------|---------------------------------|-------------------------------------------------------------|
+| `CTRL_CLOSE_EVENT`     | _any_                           | system parameter `SPI_GETHUNGAPPTIMEOUT`, 5000ms            |
+| `CTRL_LOGOFF_EVENT`    | `CONSOLE_QUICK_RESOLVE_FLAG`[1] | registry key `CriticalAppShutdownTimeout` or 500ms          |
+| `CTRL_LOGOFF_EVENT`    | _none of the above_             | system parameter `SPI_GETWAITTOKILLTIMEOUT`, 5000ms         |
+| `CTRL_SHUTDOWN_EVENT`  | **service process**             | system parameter `SPI_GETWAITTOKILLSERVICETIMEOUT`, 20000ms |
+| `CTRL_SHUTDOWN_EVENT`  | `CONSOLE_QUICK_RESOLVE_FLAG`[1] | registry key `CriticalAppShutdownTimeout` or 500ms          |
+| `CTRL_SHUTDOWN_EVENT`  | _none of the above_             | system parameter `SPI_GETWAITTOKILLTIMEOUT`, 5000ms         |
+| `CTRL_C`, `CTRL_BREAK` | _any_                           | **no timeout**                                              |
+
+_[1]: nobody sets `CONSOLE_QUICK_RESOLVE_FLAG`._

doc/ConsoleHostSettings.md

@@ -0,0 +1,70 @@
+# Understanding Console Host Settings
+
+Settings in the Windows Console Host can be a bit tricky to understand. This is mostly because the settings system evolved over the course of decades. Before we dig into the details of how settings are persisted, it's probably worth taking a quick look at what these settings are.
+
+## Settings Description
+
+|Name                       |Type                   |Description                           |
+|---------------------------|-----------------------|--------------------------------------|
+|`FontSize`                 |Coordinate (REG_DWORD) |Size of font in pixels                |
+|`FontFamily`               |REG_DWORD              |GDI Font family                       |
+|`ScreenBufferSize`         |Coordinate (REG_DWORD) |Size of the screen buffer in WxH characters |
+|`CursorSize`               |REG_DWORD              |Cursor height as percentage of a single character |
+|`WindowSize`               |Coordinate (REG_DWORD) |Initial size of the window in WxH characters |
+|`WindowPosition`           |Coordinate (REG_DWORD) |Initial position of the window in WxH pixels (if not set, use auto-positioning) |
+|`WindowAlpha`              |REG_DWORD              |Opacity of the window (valid range: 0x4D-0xFF) |
+|`ScreenColors`             |REG_DWORD              |Default foreground and background colors |
+|`PopupColors`              |REG_DWORD              |FG and BG colors used when displaying a popup window (e.g. when F2 is pressed in CMD.exe) |
+|`QuickEdit`                |REG_DWORD              |Whether QuickEdit is on by default or not |
+|`FaceName`                 |REG_SZ                 |Name of font to use (or "__DefaultTTFont__", which defaults to whichever font is deemed most appropriate for your codepage) |
+|`FontWeight`               |REG_DWORD              |GDI font weight                       |
+|`InsertMode`               |REG_DWORD              |Whether Insert mode is on by default or not |
+|`HistoryBufferSize`        |REG_DWORD              |Number of history entries to retain   |
+|`NumberOfHistoryBuffers`   |REG_DWORD              |Number of history buffers to retain   |
+|`HistoryNoDup`             |REG_DWORD              |Whether to retain duplicate history entries or not |
+|`ColorTable%%`             |REG_DWORD              |For each of the 16 colors in the palette, the RGB value of the color to use |
+|`ExtendedEditKey`          |REG_DWORD              |Whether to allow the use of extended edit keys or not |
+|`WordDelimiters`           |REG_SZ                 |A list of characters that are considered as delimiting words (e.g. `' .-/\=|,()[]{}'`) |
+|`TrimLeadingZeros`         |REG_DWORD              |Whether to remove zeroes from the beginning of a selected string on copy (e.g. `00000001` becomes `1`) |
+|`EnableColorSelection`     |REG_DWORD              |Whether to allow selection colorization or not |
+|`ScrollScale`              |REG_DWORD              |How many lines to scroll when using `SHIFT|Scroll Wheel` |
+|`CodePage`                 |REG_DWORD              |The default codepage to use           |
+|`ForceV2`                  |REG_DWORD              |Whether to use the improved version of the Windows Console Host |
+|`LineSelection`*           |REG_DWORD              |Whether to use wrapped text selection |
+|`FilterOnPaste`*           |REG_DWORD              |Whether to replace characters on paste (e.g. Word "smart quotes" are replaced with regular quotes) |
+|`LineWrap`*                |REG_DWORD              |Whether to have the Windows Console Host break long lines into multiple rows |
+|`CtrlKeyShortcutsDisabled`*|REG_DWORD              |Disables new control key shortcuts    |
+|`AllowAltF4Close`*         |REG_DWORD              |Allows the user to disable the Alt-F4 hotkey |
+|`VirtualTerminalLevel`*    |REG_DWORD              |The level of VT support provided by the Windows Console Host |
+
+*: Only applies to the improved version of the Windows Console Host
+
+## The Settings Hierarchy
+
+Settings are persisted to a variety of locations depending on how they are modified and how the Windows Console Host was invoked:
+* Hardcoded settings in conhostv2.dll
+* User's configured defaults (stored as values in `HKCU\Console`)
+* Per-console-application storage (stored as subkeys of `HKCU\Console`). Subkey names:
+  * Console application path (with `\` replaced with `_`)
+  * Console title
+* Windows shortcut (.lnk) files
+
+To modify the defaults, invoke the `Defaults` titlebar menu option on a Windows Console Host window. Any changes made in the resulting dialog will be persisted to the registry location mentioned above.
+
+To modify settings specific to the current application, invoke the `Properties` titlebar menu option on a Windows Console Host window. If the application was launched directly (e.g. via the Windows run dialog), changes made in the dialog will be persisted in the per-application storage location mentioned above. If the application was launched via a Windows shortcut file, changes made in the settings dialog will be persisted directly into the .lnk file. For console applications with a shortcut, you can also right-click on the shortcut file and choose `Properties` to access the settings dialog.
+
+When console applications are launched, the Windows Console Host determines which settings to use by overlaying settings from the above locations.
+
+1. Initialize settings based on hardcoded defaults
+2. Overlay settings specified by the user's configured defaults
+3. Overlay application-specific settings from either the registry or the shortcut file, depending on how the application was launched
+
+Note that the registry settings are "sparse" settings repositories, meaning that if a setting isn't present, then whatever value that is already in use remains unchanged. This allows users to have some settings shared amongst all console applications and other settings be specific. Shortcut files, however, store each setting regardless of whether it was a default setting or not.
+
+## Known Issues
+
+* Modifications to system-created Start Menu and Win-X menu console applications are not kept during upgrade.
+
+## Adding settings
+
+Adding a setting involves a bunch of steps - see [AddASetting.md](AddASetting.md).

doc/Debugging.md

@@ -0,0 +1,10 @@
+# Debugging Miscellanea
+
+This file contains notes about debugging various items in the repository.
+
+## Setting breakpoints in Visual Studio for Cascadia (packaged) application
+
+If you want to debug code in the Cascadia package via Visual Studio, your breakpoints will not be hit by default. A tweak is required to the *CascadiaPackage* project in order to enable this.
+
+1. Right-click on *CascadiaPackage* in Solution Explorer and select Properties.
+2. Change the *Application process* type from *Mixed (Managed and Native)* to *Native Only*.

doc/EXCEPTIONS.md

@@ -0,0 +1,36 @@
+# Using Exceptions
+
+## Philosophy
+Introducing exceptions to an existing non-exception-based codebase can be perilous. The console was originally written
+in C at a time when C++ was relatively unused in the Windows operating system. As part of our project to modernize the
+Windows console, we converted to use C++, but still had an aversion to using exception-based error handling in
+our code for fear that it introduce unexpected failures. However, the STL and other libraries like it are so useful that
+sometimes it's significantly simpler to use them. Given that, we have a set of rules that we follow when considering
+exception use.
+
+## Rules
+1. **DO NOT** allow exceptions to leak out of new code into old code
+1. **DO** use `NTSTATUS` or `HRESULT` as return values as appropriate (`HRESULT` is preferred)
+1. **DO** encapsulate all exception behaviors within implementing classes
+1. **DO NOT** introduce modern exception throwing code into old code. Instead, refactor as needed to allow encapsulation or
+   use non-exception based code
+1. **DO** use WIL as an alternative for non-throwing modern facilities (e.g. `wil::unique_ptr<>`)
+
+## Examples
+
+### Encapsulating exception behaviors in a class
+
+    class ExceptionsDoNotLeak
+    {
+        public:
+        HRESULT SomePublicFunction();
+        int iPublic;
+
+        private:
+        void _SomePrivateFunction();
+        int _iPrivate;
+    };
+
+### Using WIL for non-throwing modern facilities
+
+TODO

doc/ORGANIZATION.md

@@ -0,0 +1,123 @@
+# Code Organization
+
+## Rules
+
+- **Follow the pattern of what you already see in the code**
+- Try to package new ideas/components into libraries that have nicely defined interfaces
+- Package new ideas into classes or refactor existing ideas into a class as you extend
+- Each project should have a Unit test in a ut_ folder in its subdirectory (like `ut_host`)
+- Functional tests should be in ft_ subdirectories (like `ft_api`)
+- Build scripts are generally in subdirectories with their type of output (like `/dll` or `/exe`)
+- Try to place interfaces in an `inc` folder in an appropriate location
+- Structure related libraries together (`/terminal/parser` and `/terminal/adapter`)
+
+## Code Overview
+* `/` - root is where solution files, root MD documentation, SD replication artifacts go.
+* `/bin` – not checked in is where binaries will be generated by the MSBuild system
+* `/dep` – dependencies that aren’t a part of the SDK
+	* `/dep/console` – files that are currently in the internal-only private SDK for the console but we’re working on opening
+	* `/dep/DDK` – files lifted wholesale from the public Microsoft DDK so you don’t have to install that. We’re reducing dependencies on these but we still use TAEF (included in here) as our test runner engine
+	* `/dep/NT` – some more structures from the DDK, sometimes internal-only/non-public we’re trying to remove.
+	* `/dep/telemetry` – Private Microsoft telemetry headers
+	* `/dep/wil` – Windows Internal Library – extremely useful for interfacing with Win32/NT/COM APIs. Contains tons of “unique pointer” like syntax for various Win32 APIs and a handful of useful macros to enable cleaner code writing (RETURN_HR_IF, LOG_IF_WIN32_ERROR, etc.)
+	* `/dep/win32k` – private headers from the Windows windowing system that we’re trying to migrate off of
+* `/ipch` – not checked in is where intellisense data will be generated if you use Visual Studio 2015
+* `/obj` – not checked in is where objects will be generated by the MSBuild system
+* `/src` – This is the fun one. In the root is common build system data.
+	* `/src/host` – The meat of the windows console host. This includes buffer, input, output, windowing, server management, clipboard, and most interactions with the console host window that aren’t stated anywhere else. We’re trying to pull things out that are reusable into other libraries, but it’s a work in progress
+		* `/src/host/lib` – Builds the reusable LIB copy of the host
+		* `/src/host/dll` – Packages LIB into conhostv2.dll to be put into the OS C:\windows\system32\
+		* `/src/host/exe` – Packages LIB into OpenConsole.exe currently used for testing without replacing your system32 copy
+		* `/src/host/tools` – Random odds and ends that make testing/debugging/development a bit easier
+			* ...to be doc’d, each of what these are
+		* `/src/host/ut_host` – Contains complete unit test library for everything we’ve managed to get unit tests on. We’d like all new code to contribute appropriate unit tests in here
+		* `/src/host/ft_api` – Feature level tests for anything that changes the way we interact with the outside world via the API. Building these up as we work as well
+		* `/src/host/ft_cjk` – Double-wide/double-byte specific Chinese/Japanese/Korean language tests that previously had to be run in a different environment. To be merged into ft_api one day
+		* `/src/host/ft_resize` – Special test for resizing/reflowing the buffer window
+		* `/src/host/ft_uia` – Currently disabled (for not being very reliable) UI Automation tests that we are looking to re-enable and expand to do UI Automation coverage of various human interactions
+		* `/src/host/...` - The files I’ll list out below
+	* `/src/inc` – Include files that are shared between the host and some of the other libraries. This is only some of them. The include story is kind of a mess right now, but we’d like to clean it up at some point
+	* `/src/propslib` – Library shared between console host and the OS shell “right click a shortcut file and modify console properties” page to read/write user settings to and from the registry and embedded within shortcut LNK data
+	* `/src/renderer` – Refactored extraction of all activities related to rendering the text in the buffers onto the screen
+		* `/src/renderer/base` – Base interface layer providing non-engine-specific rendering things like choosing the data from the console buffer, deciding how to lay out or transform that data, then dispatching commands to a specific final display engine
+		* `/src/renderer/gdi` – The GDI implementation of rendering to the screen. Takes commands to “draw a line” or “fill the background” or “select a region” from the base and turns them into GDI calls to the screen. Extracted from original console host code.
+		* `/src/renderer/inc` – Interface definitions for all renderer communication
+	* `/src/terminal` – Virtual terminal support for the console. This is the sequences that are found in-band with other text on STDIN/STDOUT that command the display to do things. This is the *nix way of controlling a console.
+		* `/src/terminal/parser` – This contains a state machine and sorting engine for feeding in individual characters from STDOUT or STDIN and decoding them into the appropriate verbs that should be performed
+		* `/src/terminal/adapter` – This converts the verbs from the interface into calls on the console API. It doesn’t actually call through the API (for performance reasons since it lives inside the same binary), but it tries to remain as close to an API call as possible. There are some private extensions to the API for behaviors that didn’t exist before this was written that we’ve not made public. We don’t know if we will yet or force people to use VT to get at them.
+	* `/src/tsf` – Text Services Foundation. This provides IME input services to the console. This was historically used for only Chinese, Japanese, and Korean IMEs specifically on OS installations with those as the primary language. It was in the summer of 2016 unrestricted to be able to be used on any OS installation with any IME (whether or not it will display correctly is a different story). It also was unrestricted to allow things like Pen and Touch input (which are routed via IME messages) to display properly inside the console from the TabTip window (the little popup that helps you insert pen/touch writing/keyboard candidates into an application)
+
+## Host File Overview
+
+* Generally related to handling input/output data and sometimes intertwined with the actual service calls
+	* `_output.cpp`
+	* `_stream.cpp`
+* Handles copy/paste/etc.
+	* `clipboard.cpp`
+* Handles the command prompt line as you see in CMD.exe (known as the processed input line… most other shells handle this themselves with raw input and don’t use ours. This is a legacy of bad architectural design, putting stuff in conhost not in CMD)
+	* `cmdline.cpp`
+* Handles shunting IME data back and forth to the TSF library and to and from the various buffers
+	* `Conimeinfo.cpp`
+	* `Convarea.cpp`
+* Contains the global state for the entire console application
+	* `consoleInformation.cpp`
+* Stuff related to the low-level server communication over our protocol with the driver
+	* `Csrutil.cpp`
+	* `Srvinit.cpp`
+	* `Handle.cpp`
+* Routines related to startup of the application
+	* `Srvinit.cpp`
+* Routines related to the API calls (and the servicing thereof, muxes a bit with the server protocol)
+	* `Directio.cpp`
+	* `Getset.cpp`
+	* `Srvinit.cpp`
+* Extra stuff strapped onto the buffer to enable CJK languages
+	* `Dbcs.cpp`
+* Attempted class-ification of existing Cursor structures to take them out of Screen Info/Text Info
+	* `Cursor.cpp`
+* Related to searching through the back buffer of the console (the output scroll buffer as defined in screeninfo/textinfo)
+	* `Find.cpp`
+* Contains global state data
+	* `Globals.cpp`
+* Attempted class-ification of existing Icon manipulation to take them out of ConsoleInformation/Settings
+	* `Icon.cpp`
+* Contains all keyboard/mouse input handling, capture of keys, conversion of keys, and some manipulation of the input buffer
+	* `Input.cpp`
+	* `Inputkeyinfo.cpp`
+	* `Inputreadhandledata.cpp`
+* Main entry point used ONLY by the OS to send a pre-configured driver handle to conhostv2.dll
+	* `Main.cpp`
+* Assorted utilities and stuff
+	* `Misc.cpp` (left for us by previous eras of random console devs)
+	* `Util.cpp` (created in our era)
+* Custom zeroing and non-throwing allocator 
+	* `Newdelete.cpp`
+* Related to inserting text into the TextInfo buffer
+	* `Output.cpp`
+	* `Stream.cpp`
+* Connects to interfaces in the PropsLib to manipulate persistent settings state
+	* `Registry.cpp`
+* Connects to our relatively recently extracted renderer LIB to give it data about console state and user prefs
+	* `renderData.cpp`
+	* `renderFontDefaults.cpp`
+* Maintains most of the information about what we should present inside the window on the screen (sizes, dimensions, also holds a text buffer instance and a cursor instance and a selection instance)
+	* `screenInfo.cpp`
+* Handles some aspects of scrolling with the mouse and keyboard
+	* `Scrolling.cpp`
+* Handles the click-and-drag highlighting of text on the screen to select (or the keyboard-based Mark mode selection where you can enter the mode and select around). Often calls clipboard when done
+	* `Selection.cpp`
+	* `selectionInput.cpp`
+	* `selectionState.cpp`
+* Handles all user preferences and state. Was extracted from consoleInformation and CI subclasses it still (because it was hard to break the association out)
+	* `Settings.cpp`
+* Good ol’ Windows 10 telemetry pipeline & ETW events as debugging aids (they use the same channel with a different flag)
+	* `Telemetry.cpp`
+	* `Tracing.cpp`
+* Private calls into the Windows Window Manager to perform privileged actions related to the console process (working to eliminate) or for High DPI stuff (also working to eliminate)
+	* `Userprivapi.cpp`
+	* `Windowdpiapi.cpp`
+* New UTF8 state machine in progress to improve Bash (and other apps) support for UTF-8 in console
+	* `Utf8ToWideCharParser.cpp`
+* Window resizing/layout/management/window messaging loops and all that other stuff that has us interact with Windows to create a visual display surface and control the user interaction entry point
+	* `Window.cpp`
+	* `Windowproc.cpp`

doc/STYLE.md

@@ -0,0 +1,7 @@
+# Coding Style
+
+## Philosophy
+1. If it's inserting something into the existing classes/functions, try to follow the existing style as closely as possible.
+1. If it's brand new code or refactoring a complete class or area of the code, please follow as Modern C++ of a style as you can and reference the [C++ Core Guidelines](https://github.com/isocpp/CppCoreGuidelines) as much as you possibly can.
+1. When working with any Win32 or NT API, please try to use the [Windows Implementation Library](./WIL.md) smart pointers and result handlers.
+1. The use of NTSTATUS as a result code is discouraged, HRESULT or exceptions are preferred. Functions should not return a status code if they would always return a successful status code. Any function that returns a status code should be marked `noexcept` and have the `nodiscard` attribute.

doc/TAEF.md

@@ -0,0 +1,20 @@
+### TAEF ###
+TAEF, the Test Authoring and Execution Framework, is used extensively within the Windows organization to test the operating system code in a unified manner for system, driver, and application code. As the console is a Windows OS Component, we strive to continue using the same system such that tests can be ran in a unified manner both externally to Microsoft as well as inside the official OS Build/Test system.
+
+The [official documentation](https://msdn.microsoft.com/en-us/library/windows/hardware/hh439725\(v=vs.85\).aspx) for TAEF describes the basic architecture, usage, and functionality of the test system. It is similar to Visual Studio test, but a bit more comprehensive and flexible.
+
+For the purposes of the console project, you can run the tests using the *TE.exe* that matches the architecture for which the test was build (x86/x64) in the pattern
+
+	te.exe Console.Unit.Tests.dll
+
+Replacing the binary name with any other test binary name that might need running. Wildcard patterns or multiple binaries can be specified and all found tests will be executed.
+
+Limiting the tests to be run is also useful with:
+
+	te.exe Console.Unit.Tests.dll /name:*BufferTests*
+
+Any pattern of class/method names can be specified after the */name:* flag with wildcard patterns.
+
+For any further details on the functionality of the TAEF test runner, *TE.exe*, please see the documentation above or run the embedded help with
+
+	te.exe /!

doc/UniversalTest.md

@@ -0,0 +1,117 @@
+# Universal Testing for Console
+
+## Overview
+
+Universal Testing is the Microsoft framework for creating and deploying test packages onto just about any device through just about any process. We use it for packaging up all sorts of test resources and sending it into our automated test labs no matter what the source of the content or the engineering system involved.
+
+It involves several parts:
+- TESTMD
+  - These define a package unit for deployment to the test device. This usually includes the test binaries and any dependent data that it will need to execute.
+  - There can also be a hierarchy where one package can depend on another such that packages can be re-used.
+
+- TESTLIST
+  - This defines a batch of TESTMD packages that should be executed together.
+
+- TESTPASSES
+  - This defines a list of tests via a TESTLIST and a lab environment configuration on which the tests should be run.
+
+  These files can either include their child element as they're supposed to (TESTMDs included in TESTLISTs) or they can often include themselves to provide chain structuring (one TESTLIST can reference another TESTLIST).
+
+- TREX
+    - This is the legacy configuration system that performed the same job as TESTPASSES, but not in source files.
+
+## Configuration
+
+  This is a record of the current setup (as of Mar-1-2019) of the console's universal tests. This series of steps was created in conjunction with converting the console's testing from the legacy TREX dispatching mode to the new TESTPASSES dispatching mode for the Source Is Truth initiative (define all testing metadata in source next to the code being tested, instead of in a separate database somewhere else).
+
+1.	Have some TestMDs.
+    -	\onecore\windows\core\console\open\src\host\ut_host\testmd.definition + SOURCES file
+        - 	Generates “Microsoft-Console-Host-UnitTests” TESTMD and package
+        -	Binplaces to prebuilt\test\<arch>\<fre/chk>\
+            1.	Microsoft.Console.Host.UnitTests.testmd
+            1.	Microsoft-Console-Host-UnitTests.cab
+            1.	Microsoft-Console-Host-UnitTests.man.dsm.xml
+    - 	\onecore\windows\core\console\open\src\host\ft_host\testmd.definition + SOURCES file
+        -	Generates “Microsoft-Console-Host-FeatureTests” TESTMD and package
+        -	Binplaces to prebuilt\test\<arch>\<fre/chk>\
+            1.	Microsoft.Console.Host.FeatureTests.testmd
+            1.	Microsoft-Console-Host-FeatureTests.cab
+            1.	Microsoft-Console-Host-FeatureTests.man.dsm.xml
+    -	\onecore\windows\core\console\open\src\buffer\out\ut_textbuffer\testmd.definition + SOURCES file
+        -	Generates “Microsoft-Console-TextBuffer-UnitTests” TESTMD and package
+        -	Binplaces to prebuilt\test\<arch>\<fre/chk>\
+            1.	Microsoft.Console.TextBuffer.UnitTests.testmd
+            1.	Microsoft-Console-TextBuffer-UnitTests.cab
+            1.	Microsoft-Console-TextBuffer-UnitTests.man.dsm.xml
+    -	\minkernel\console\client\ut_conpty\testmd.definition + SOURCES file
+        - 	Generates “Microsoft-Console-ConPty-UnitTests” TESTMD and package
+        - 	Binplaces to prebuilt\test\<arch>\<fre/chk>\
+            1.	Microsoft.Console.ConPty.UnitTests.testmd
+            1.	Microsoft-Console-ConPty-UnitTests.cab
+            1.	Microsoft-Console-ConPty-UnitTests.man.dsm.xml
+    - 	\onecore\windows\core\console\open\src\terminal\parser\ut_parser\testmd.definition + SOURCES file
+        - 	Generates “Microsoft-Console-VirtualTerminal-Parser-UnitTests” TESTMD and package
+        - 	Binplaces to prebuilt\test\<arch>\<fre/chk>\
+            1.	Microsoft.Console.VirtualTerminal.Parser.UnitTests.testmd
+            1.	Microsoft-Console-VirtualTerminal-Parser-UnitTests.cab
+            1.	Microsoft-Console-VirtualTerminal-Parser-UnitTests.man.dsm.xml
+    - \onecore\windows\core\console\open\src\terminal\adapter\ut_adapter\testmd.definition + SOURCES file
+        -	Generates “Microsoft-Console-VirtualTerminal-Adapter-UnitTests” TESTMD and package
+        -	Binplaces to prebuilt\test\<arch>\<fre/chk>\
+            1.	Microsoft.Console.VirtualTerminal.Adapter.UnitTests.testmd
+            1.	Microsoft-Console-VirtualTerminal-Adapter-UnitTests.cab
+            1.	Microsoft-Console-VirtualTerminal-Adapter-UnitTests.man.dsm.xml
+1.	Have some TESTLISTs that refer to the TESTMDs
+    - 	\onecore\windows\core\console\open\src\testlist\Microsoft.Console.Tests.testlist + SOURCES file
+        - 	Includes 
+            1.	Microsoft.Console.Host.UnitTests.testmd
+            1.	Microsoft.Console.Host.FeatureTests.testmd
+            1.	Microsoft.Console.TextBuffer.UnitTests.testmd
+            1.	Microsoft.Console.Conpty.UnitTests.testmd
+            1.	Microsoft.Console.VirtualTerminal.Parser.UnitTests.testmd
+            1.	Microsoft.Console.VirtualTerminal.Adapter.UnitTests.testmd
+        - 	Binplaces to prebuilt\test\<arch>\<fre/chk>\
+            - 	Microsoft.Console.Tests.testlist
+    - 	\onecore\windows\core\console\open\src\testlist\Microsoft.Console.TestLab.Desktop.testlist + SOURCES file
+        - Includes
+            1.	Microsoft.Console.Tests.testlist
+        - 	Binplaces to prebuilt\test\<arch>\<fre/chk>\
+            - 	Microsoft.Console.TestLab.Desktop.testlist
+        - 	Is currently the subject of TREX IDs
+            1.	153251 – TESTLIST based AMD64 Desktop VM testpass (to be offboarded when done)
+            1.	153252 – TESTLIST based X86 Desktop VM testpass (to be offboarded when done)
+    -	\onecore\windows\core\console\open\src\testlist\Microsoft.Console.TestLab.OneCoreUap.testlist + SOURCES file
+        -	Includes
+            1.	Microsoft.Console.Tests.testlist
+        - 	Binplaces to prebuilt\test\<arch>\<fre/chk>\
+            -	Microsoft.Console.TestLab.OneCoreUAP.testlist
+        -	Is currently the subject of TREX IDs
+            1.	153253 – TESTLIST based AMD64 OneCoreUAP VM testpass (to be offboarded when done)
+            1.	153254 – TESTLIST based X86 OneCoreUAP VM testpass (to be offboarded when done)
+1.	Create some TESTPASSES
+    - 	For the existing OneCoreUAP ones…
+        - 	Create directory \onecoreuap\testpasses\local\console\
+        - 	Create file console_onecoreuap.testpasses
+            1.	Create AMD64 pass
+                -	Name it similarly to the existing name
+                -	Use the environment $(TESTPASSES_ONECOREUAP)/standard_testenvs/OneCoreUAP-amd64-VM.testenv
+                -	Connect to the testlist $(TESTLIST_SEARCH_PATHS)/Microsoft.Console.TestLab.OneCoreUAP.testlist
+            1.	Create X86 pass
+                -	Name it similarly to the existing name
+                -	Use the environment $(TESTPASSES_ONECOREUAP)/standard_testenvs/OneCoreUAP-x86-VM.testenv
+                -	Connect to the testlist $(TESTLIST_SEARCH_PATHS)/Microsoft.Console.TestLab.OneCoreUAP.testlist
+    - 	For the Desktop ones…
+        -	Create directory \pcshell\testpasses\local\console\
+        - 	Create file console_desktop.testpasses
+            1.	Create AMD64 pass
+                - 	Name it similarly to the existing name
+                - 	Use the environment $(TESTPASSES_PCSHELL)/standard_testenvs/Enterprise-amd64-VM.testenv
+                - 	Connect to the testlist $(TESTLIST_SEARCH_PATHS)/Microsoft.Console.TestLab.Desktop.testlist
+            1.	Create X86 pass
+                - 	Name it similarly to the existing name
+                - 	Use the environment $(TESTPASSES_PCSHELL)/standard_testenvs/Enterprise-x86-VM.testenv
+                - 	Connect to the testlist $(TESTLIST_SEARCH_PATHS)/Microsoft.Console.TestLab.Desktop.testlist
+1.	Hook up the TESTPASSES into the official branch TESTPASSES file
+    - 	Open up \.branchconfig\official\rs_onecore_dep_acidev\official_build.testpasses
+        1.	Add TestpassReferences item targeting $(TESTPASSES_ONECOREUAP)/local/console/console_onecoreuap.testpasses
+        1.	Add TestpassReferences item targeting $(TESTPASSES_PCSHELL)/local/console/console_desktop.testpasses

doc/WIL.md

@@ -0,0 +1,27 @@
+# Windows Implementation Library
+
+## Overview
+[Windows Implementation Library](https://github.com/Microsoft/wil), or WIL, is a header-only library created to help make working with the Windows API more predictable and (hopefully) bug free.
+
+A majority of functions are in either the `wil::` or `wistd::` namespace. `wistd::` is used for things that have an equivalent in STL's `std::` namespace but have some special functionality like being exception-free. Everything else is in `wil::` namespace.
+
+The primary usages of WIL in our code so far are...
+
+### Smart Pointers ###
+
+Inside [wil\resource.h](https://github.com/microsoft/wil/blob/master/include/wil/resource.h) are smart pointer like classes for many Windows OS resources like file handles, socket handles, process handles, and so on. They're of the form `wil::unique_handle` and call the appropriate/matching OS function (like `CloseHandle()` in this case) when they go out of scope.
+
+Another useful item is `wil::make_unique_nothrow()` which is analogous to `std::make_unique` (except without the exception which might help you integrate with existing exception-free code in the console.) This will return a `wistd::unique_ptr` (vs. a `std::unique_ptr`) which can be used in a similar manner.
+
+### Result Handling ###
+
+To manage the various types of result codes that come back from Windows APIs, the file [wil\result.h](https://github.com/microsoft/wil/blob/master/include/wil/result.h) provides a wealth of macros that can help. 
+
+As an example, the method `DuplicateHandle()` returns a `BOOL` value that is `FALSE` under failure and would like you to `GetLastError()` from the operating system to find out what the actual result code is. In this circumstance, you could use the macro `RETURN_IF_WIN32_BOOL_FALSE` to wrap the call to `DuplicateHandle()` which would automatically handle this pattern for you and return the `HRESULT` equivalent on failure.
+
+This leads to nice patterns where you can set up all resources in a function as protected by `std::unique_ptr` or the various `wil::` smart pointers and smart handles then `RETURN_IF_*` on every call to a Windows API and be guaranteed that your resources will be cleaned up appropriately under any failure case. Do note that this generally requires you to return an `HRESULT` as your return code and use out pointer parameters for return data. There are exceptions to this... read the header for more details. 
+
+The additional advantage to using this pattern is that failures at any point are logged to our global tracing/debugging channels to be viewed under the debugger output with the exact line number and function details for the error.
+
+Additionally, if you just want to make sure that a failure case is logged for debugging purposes, all of these macros have a `LOG_IF_*` equivalent that will simply log a failure and keep rolling.
+

doc/WindowsTestPasses.md

@@ -0,0 +1,42 @@
+# Windows Test Passes for Console
+
+## Overview
+
+Every night, we run a set of automated test passes in the Windows engineering system for the console host code. This process is orchestrated on our working branch, which at the time of this writing is `RS_ONECORE_DEP_ACIDEV` (and will soon switch back to `RS_ONECORE_DEP_ACIOSS` or something of that ilk).
+
+You can find the information about our nightly build, including these test passes, at the website [https://es.microsoft.com], choosing our branch, and then navigating to the `Execution Status` page.
+
+At the bottom of the page will be the test pass runs for our tests that night. You can find out more about how these are set up in the [UniversalTest.md] file.
+
+When a failure occurs in one of these passes, a bug will automatically be generated in the Azure DevOps project for the OS and assigned to our path.
+
+The next step would be investigating one of these failures...
+
+## Investigation
+
+A quick overview of investigation... normally you can just attempt to build and reproduce the failure locally with the `OpenConsole` project and it will happen the same way as it did on the nightly build in the lab. However, sometimes the failure will be exclusive to the lab or won't happen in the same way as it does on your local dev machine. At that point, you need to move into setting up the environment as it was during the testpass and figuring out what went wrong.
+
+You can try to do this all manually by pulling down a VM image from the release share for the nightly build, making a VM, deploying the test binaries and TAEF test runner executables to the machine, installing the VS Remote Debugging or WinDBG tools on the VM, and then running the test and figuring out what's going wrong with the debuggers.
+
+Or you can use some of the Engineering Systems tools to make this easier. I'll detail how to do that below.
+
+Prerequisites:
+- Visual Studio 2017
+- Install the TDP (Test Development Platform) plug-in (see: [https://osgwiki.com/wiki/Test_Development_Platform_(TDP)]).
+
+1. Open Visual Studio 2017 and use the TDP drop-down menu to open the `Device Manager`.
+1. In the pane that opens to the left, choose `Add` and then `Nebula VM Device`. Nebula is a cloud provider for VMs (like Azure but a more private instance for corporate work usage).
+1. Name the machine and choose the build/branch/flavor/SKU from the drop downs at the bottom. It will find the VHD for you from the build shares. Hit `Add Device` to deploy to Nebula.
+1. Wait a few minutes. It took 5-10 for it to be deployed.
+1. Right click the machine name in the `Device Manager` list and choose `Launch T-Shell`. You can also use `Connect via Console` to get a "remote desktop"-like session to the KVM port on the VM.
+1. In T-shell, use `testd Microsoft.Console.TestLab.Desktop.testlist` or a command of that format with a different TESTLIST or TESTMD name from our project (see the [UniversalTest.md] documentation). The `testd` utility will automatically resolve the build/branch/flavor information, dig through the build shares for the matching TESTLIST/TESTMD metadata, and attempt to deploy all relevant packages and dependencies on the device. When it's successful, it will move onto running all the tests and giving you the results. On conclusion, the test results should pop up in the web browser or the `Hubble - Log Viewer` tool provided by the Engineering Systems team.
+
+If some of the above things do not work, go to [https://osgwiki.com] and type them into the Search bar. For instance, if T-Shell isn't found or working, you can find out where to get it or download it on `OSGWiki`. The same goes for the other commands besides `testd` to use in T-shell and more information on what `Hubble` or `Nebula` are. 
+
+Presumably now you have a failure. Or a success. You can attempt to spelunk the logs in `Hubble` and you might come to a conclusion. Or you can move onto debugging directly.
+
+Now that you've relied on `testd` to get everything deployed and orchestrated and run once on the device, you can use `execd` to run things again or to run a smaller subset of things on the remote device through `T-Shell`. 
+
+By default, in the `Universal Test` world, everything will be deployed onto the remote machine at `C:\data\test\bin`. In T-Shell, use `cdd C:\data\test\bin` to change to that directory and then `execd te.exe Microsoft.Console.Host.FeatureTests.dll /name:*TestReadFileEcho*` to run just one specific test. Of course you should substitute the file name and test name parameters as makes sense. And of course you can find out more about `cdd` and `execd` on the `T-shell` page of `OSGWiki`.
+
+Fortunately, running things through `T-shell` in this fashion is exactly the same way that the testlab orchestrates the tests. If you still don't get good data this way, you can use the `Connect via Console` mechanism way above to try to run things under `WinDBG` or the `Visual Studio Remote Debugger` manually on the machine to get them to repro or under the debugger more completely.

doc/bot.md

@@ -0,0 +1,102 @@
+# Issue/PR Management Bot Information
+
+## Overview
+
+The goal here is to help us automate, manage, and narrow down what we actually need to focus on in this repository.
+We'll be using tags, primarily, to help us understand what needs attention, what is sitting around and turning stale, etc.
+
+### Quick-Guidance to Core Contributors
+1. Look at `Needs-Attention` as top priority
+1. Look at `Needs-Triage` during triage meetings to get a handle on what's new and sort it out
+1. Look at `Needs-Tag-Fix` when you have a few minutes to fix up things tagged impoperly
+1. Manually add `Needs-Author-Feedback` when there's something we need the author to follow up on and want attention if they return it or an auto-close for inactivity if it goes stale.
+
+### Tagging/Process Details
+1. When new issues arrive, or when issues are not properly tagged... we'll mark them as `Needs-Triage` automatically.
+   - The core contributor team will then come through and mark them up as appropriate. The goal is to have a tag that fits the `Product`, `Area`, and `Issue` category. 
+   - The `Needs-Triage` tag will be removed manually by the core contributor team during a triage meeting. (Exception, triage may also be done offline by senior team members during high-volume times.)
+   - An issue may or may not be assigned to a contributor during triage. It is not necessary to assign someone to complete it.
+   - We're not focusing on Projects yet.
+1. When core contributors need to ask something of the author, they will manually assign the `Needs-Author-Feedback` tag.
+   - This tag will automatically drop off when the author comes back around and applies activity to the thread.
+   - When this tag drops off, the bot will apply the `Needs-Attention` tag to get the core contribution team's attention again. If an author cares enough to be active, we will attempt to prioritize engaging with that author.
+   - If the author doesn't come back around in a while, this will become a `No-Recent-Activity` tag.
+   - If there's activity on an issue, the `No-Recent-Activity` tag will automatically drop.
+   - If the `No-Recent-Activity` stays, the issue will be closed as stale. 
+1. PRs will automatically get a `Needs-Author-Feedback` tag when reviewers wait on the author
+   - This follows a similar decay strategy to issues.
+   - If the author responds, the `Needs-Author-Feedback` tag will drop.
+   - If there is no activity in a while, the `No-Recent-Activity` tag will appear.
+   - If the `No-Recent-Activity` tag exists for a while, the PR will be closed as stale.
+1. Issues manually marked as `Resolution-Duplicate` will be closed shortly after activity stops
+1. Pull requests manually marked as `AutoMerge` will permit the bot to complete the PR and do cleanup when certain conditions are met. See details below.
+
+## Rules
+
+### Issue Management
+
+#### Mark as Triage Needed
+- When an issue doesn't meet triage criteria, applies `Needs-Triage` tag. Right now, this is just when it's opened.
+  
+#### Author Has Responded
+- When an issue with `Needs-Author-Feedback` gets an author response, drops that tag in favor of `Needs-Attention` to flag core contributors to drop by.
+
+#### Remove Activity Tag
+- When an issue with `No-Recent-Activity` has activity, drops this tag
+
+#### Close Stale
+- Every hour, checks if there's an issue with `Needs-Author-Feedback` and `No-Recent-Activity` for 3 days. Closes as stale.
+
+#### Tag as No Activity
+- Every hour, checks if there's been no activity in 4 days on an issue that `Needs-Author-Feedback`. If it's been 4 days, mark `No-Recent-Activity` as well.
+
+#### Close Duplicate Issues
+- Every hour, checks if there's been a day since the last activity on an issue with tag `Resolution-Duplicate` and closes it if inactive.
+
+#### Enforce tag system
+- When an issue is opened or labels are changed in any way, we will check if the tagging matches the system. If not, it will get `Needs-Tag-Fix`. The system is to have an `Area-`, `Issue-`, and `Product-` tag for all open things, and also a `Resolution-` for closed ones.
+- When the tags from appropriate categories are applied, it will auto-remove the `Needs-Tag-Fix` tag.
+- `Resolution-Duplicate` is sufficient to fix all tagging. (`Area-`, `Issue-`, and `Product-` are not needed for a duplicate.)
+
+#### Clean-up low quality issues
+- If an issue is filed with an incomplete title...
+- If an issue is filed with nothing in the body...
+- If an issue is filed matching a pattern that happens all the time (common duplicate phrase, obvious multiple-issues-in-one pattern)...
+- Then close the issue automatically informing the opener that they can resolve the problem and reopen the issue. (See Bug/Feature templates for example situations.)
+
+### PR Management
+
+#### Codeflow Link *(Disabled)*
+- Bumps a PR with a link to the Microsoft CodeFlow tool for reviewing PRs
+
+#### Marks PR as Awaiting Author Feedback
+- When a reviewer marks the PR as changes requested, the `Needs-Author-Feedback` tag will be applied
+
+#### Removes Awaiting Author Feedback
+- When the PR author updates the pull request, comments on it, or responds to a review, the `Needs-Author-Feedback` tag is removed.
+
+#### Removes No Recent Activity
+- When anyone touches the pull request, the `No-Recent-Activity` tag is removed.
+
+#### Markup stale pull requests
+- Every hour, if a pull request `Needs-Author-Feedback` and hasn't been touched in 7 days, it will get the `No-Recent-Activity` tag.
+
+#### Close stale pull requests
+- Every hour, if a pull request has `No-Recent-Activity` and hasn't been touched in a further 7 days, it will be closed.
+
+#### Auto-Merge pull requests
+- When a pull request has the `AutoMerge` label...
+  - If it has been at least 480 minutes and all the statuses pass, merge it in.
+  - Will use Squash merge stratgy
+  - Will attempt to delete branch after merge, if possible
+  - Will automatically remove the `AutoMerge` label if changes are pushed by someone *without* Write Access.
+  - More information on bot-logic that can be controlled with comments is [here](https://github.com/OfficeDev/office-ui-fabric-react/wiki/Advanced-auto-merge)
+  
+#### Mark issues with an active PR
+- If there is an active PR for an issue, label that issue with the `In-PR` label
+
+#### Add committed fix tag for completed PRs
+- When a PR is finished and there's no outstanding work left on a linked issue, add the `Resolution-Fix-Committed` label
+  
+## Admin Panel
+[Here](https://fabric-cp.azurewebsites.net/bot/)

doc/building.md

@@ -0,0 +1,36 @@
+
+# How to build Openconsole
+
+Openconsole can be built with Visual Studio or from the command line. There are build scripts for both cmd and powershell in /tools.
+
+When using Visual Studio, be sure to set up the path for code formatting. This can be done in Visual Studio by going to Tools > Options > Text Editor > C++ > Formatting and checking "Use custom clang-format.exe file" and choosing the clang-format.exe in the repository at /dep/llvm/clang-format.exe by clicking "browse" right under the check box.
+
+## Building with cmd
+
+The cmd scripts are set up to emulate a portion of the OS razzle build environment. razzle.cmd is the first script that should be run. bcz.cmd will build clean and bz.cmd should build incrementally.
+
+There are also scripts for running the tests:
+- `runut.cmd` - run the unit tests
+- `runft.cmd` - run the feature tests
+- `runuia.cmd` - run the UIA tests
+- `runformat` - uses clang-format to format all c++ files to match our coding style.
+
+## Build with Powershell
+
+Openconsole.psm1 should be loaded with `Import-Module`. From there `Set-MsbuildDevEnvironment` will set up environment variables required to build. There are a few exported functions (look at their documentation for further details):
+
+- `Invoke-OpenConsolebuild` - builds the solution. Can be passed msbuild arguments.
+- `Invoke-OpenConsoleTests` - runs the various tests. Will run the unit tests by default.
+- `Start-OpenConsole` - starts Openconsole.exe from the output directory. x64 is run by default.
+- `Debug-OpenConsole` - starts Openconsole.exe and attaches it to the default debugger. x64 is run by default.
+- `Invoke-CodeFormat` - uses clang-format to format all c++ files to match our coding style.
+
+## Configuration Types
+
+Openconsole has three configuration types:
+
+- Debug
+- Release
+- AuditMode
+
+AuditMode is an experimental mode that enables some additional static analyis from CppCoreCheck.

doc/cascadia/Keybindings-spec.md

@@ -0,0 +1,108 @@
+# Keymapping spec
+
+* author: Mike Griese __migrie__
+* created on: 2018-Oct-23
+
+## Abstract
+It should be possible to configure the terminal so that it doesn't send certain keystrokes as input to the terminal, and instead triggers certain actions. Examples of these actions could be copy/pasting text, opening a new tab, or changing the font size.
+
+This spec describes a mechanism by which we could provide a common implementation of handling keyboard shortcuts like these. This common implementation could then be leveraged and extended by the UX implementation as to handle certain callbacks in the UX layer. For example, The TerminalCore doesn't have a concept of what a tab is, but the keymap abstraction could raise an event such that a WPF app could implement creating a new tab in its idomatic way, and UWP could implement them in their own way.
+
+## Terminology
+* **Key Chord**: This is any possible keystroke that a user can input
+  simultaneously, as a combination of a single character and any set of
+  (<kbd>Ctrl</kbd>, <kbd>Alt</kbd> and <kbd>Shift</kbd>).
+  For example, pressing <kbd>Ctrl</kbd> and <kbd>C</kbd> at the same time is the
+  key chord Ctrl+C. Pressing <kbd>Ctrl+B</kbd>, <kbd>C</kbd> are two separate
+  key chords. Trying to press them simultaneously (<kbd>Ctrl+B+C</kbd>) should
+  generate two separate key chords, with the order determined by the OS.
+
+## User Stories
+1. The User should be able to press certain key-chords to trigger certain
+   actions in the frontend of the application, such as copying text, pasting,
+   opening new tabs, or switching focus between panes.
+2. The user should be able to configure which key chords are bound to which actions.
+3. If a key chord is not mapped to an action, it should be sent to the Terminal just as any other keypress.
+
+## Details
+
+When the UX frontend is created, it should instantiate a `IKeyBindings` object with the keybindings mapped as it would like.
+
+When it's creating its platform-dependent terminal component, it can pass the `IKeyBindings` object to that component. The component will then be able to pass that object to the terminal instance.
+
+When the terminal component calls `ITerminalInput.SendKeyEvent(uint vkey, KeyModifiers modifiers)`, the terminal will use `IKeyBindings.TryKeyChord` to see if there are any bound actions to that input. If there are, the `IKeyBindings` implementation will either handle the event by interacting with the `ITerminalInput`, or it'll invoke an event that's been registered by the frontend
+
+```csharp
+struct KeyChord
+{
+    KeyModifiers modifiers;
+    int vkey;
+}
+
+interface IKeyBindings {
+    bool TryKeyChord(KeyChord kc);
+}
+```
+
+Each frontend can implement the `IKeyBindings` interface however it so chooses.
+
+The `ITerminalInput` interface will be extended with the following method:
+```csharp
+public interface ITerminalInput
+{
+    ...
+    void SetKeyBindings(IKeyBindings bindings);
+    ...
+}
+```
+This will set the `IKeyBindings` object that the `ITerminalInput` implementation will use to filter key events.
+
+This method will be implemented by the `Terminal` object:
+```csharp
+partial class Terminal
+{
+    public void ITerminalInput.SetKeyBindings(IKeyBindings bindings);
+}
+```
+### Project Cascadia Sample
+
+Below is an example of how the Project Cascadia application might implement its
+  keybindings.
+
+```csharp
+enum ShortcutAction
+{
+    CopyText,
+    PasteText,
+    NewTab,
+    NewWindow,
+    CloseWindow,
+    CloseTab,
+    SwitchToTab,
+    NextTab,
+    PrevTab,
+    IncreaseFontSize,
+    DecreaseFontSize,
+    ...
+}
+public delegate bool NewTabEvent(object sender);
+public delegate bool CloseTabEvent(object sender);
+public delegate bool NewWindowEvent(object sender);
+public delegate bool CloseWindowEvent(object sender);
+public delegate bool CopyEvent(object sender);
+public delegate bool PasteEvent(object sender);
+
+class KeyBindings : IKeyBindings
+{
+    private Dictionary<ShortcutAction, KeyChord?> keyShortcuts;
+
+    public void SetKeyBinding(ShortcutAction action, KeyChord? chord);
+    public bool TryKeyChord(KeyChord chord);
+}
+```
+
+### Copy/Paste
+How does Copy/paste play into this?
+
+When Input is written to the terminal, and it tries the copy keybinding, what happens?
+The Keybindings are global to the frontend, not local to the terminal. Copy/Paste events should also be delegates that get raised, and the frontend can then determine what to do with them. It'll probably query its active/focused Terminal Component, then Get the `ITerminalInput` from that component, and use that to CopyText / PasteText from the Terminal as needed.

doc/cascadia/Panes.md

@@ -0,0 +1,232 @@
+---
+author: "Mike Griese @zadjii-msft"
+created on: 2019-May-16
+---
+
+# Panes in the Windows Terminal
+
+## Abstract
+
+Panes are an abstraction by which the terminal can display multiple terminal
+instances simultaneously in a single terminal window. While tabs allow for a
+single terminal window to have many terminal sessions running simultaneously
+within a single window, only one tab can be visible at a time. Panes, on the
+other hand, allow a user to have many different terminal sessions visible to the
+user within the context of a single window at the same time. This can enable
+greater productivity from the user, as they can see the output of one terminal
+window while working in another.
+
+This spec will help outline the design of the implementation of panes in the
+Windows Terminal.
+
+## Inspirations
+
+Panes within the context of a single terminal window are not a new idea. The
+design of the panes for the Windows Terminal was heavily inspired by the
+application `tmux`, which is a commandline application which acts as a "terminal
+multiplexer", allowing for the easy managment of many terminal sessions from a
+single application.
+
+Other applications that include pane-like functionality include (but are not
+limited to):
+
+* screen
+* terminator
+* emacs & vim
+* Iterm2
+
+## Design
+
+The architecture of the Windows Terminal can be broken into two main pieces:
+Tabs and Panes. The Windows Terminal supports _top-level_ tabs, with nested
+panes inside the tabs. This means that there's a single strip of tabs along the
+application, and each tab has a set of panes that are visible within the context
+of that tab.
+
+Panes are implemented as a binary tree of panes. A Pane can either be a leaf
+pane, with it's own terminal control that it displays, or it could be a parent
+pane, where it has two children, each with their own terminal control.
+
+When a pane is a parent, its two children are either split vertically or
+horizontally. Parent nodes don't have a terminal of their own, they merely
+display the terminals of their children.
+
+ * If a Pane is split vertically, the two panes are seperated by a vertical
+   split, as to appear side-by-side. Think `[|]`
+ * If a Pane is split horizontally, the two panes are split by a horizontal
+   separator, and appear above/below one another. Think `[-]`.
+
+As additional panes are created, panes will continue to subdivide the space of
+their parent. It's up to the parent pane to control the sizing and display of
+it's children.
+
+### Example
+
+We'll start by taking the terminal and creating a single vertical split. There
+are now two panes in the terminal, side by side. The original terminal is `A`,
+and the newly created one is `B`. The terminal now looks like this:
+
+```
+  +---------------+
+  |       |       |    1: parent [|]
+  |       |       |    ├── 2: A
+  |       |       |    └── 3: B
+  |   A   |   B   |
+  |       |       |
+  |       |       |
+  |       |       |
+  +---------------+
+```
+
+Here, there are actually 3 nodes: 1 is the parent of both 2 and 3. 2 is the node
+containing the `A` terminal, and 3 is the node with the `B` terminal.
+
+
+We could now split `B` in two horizontally, creating a third terminal pane `C`.
+
+```
+  +---------------+
+  |       |       |    1: parent [|]
+  |       |   B   |    ├── 2: A
+  |       |       |    └── 3: parent [-]
+  |   A   +-------+        ├── 4: B
+  |       |       |        └── 5: C
+  |       |   C   |
+  |       |       |
+  +---------------+
+```
+
+Node 3 is now a parent node, and the terminal `B` has moved into a new node as a
+sibling of the new terminal `C`.
+
+We could also split `A` in horizontally, creating a fourth terminal pane `D`.
+
+```
+  +---------------+
+  |       |       |    1: parent [|]
+  |   A   |   B   |    ├── 2: parent [-]
+  |       |       |    |   ├── 4: A
+  +-------+-------+    |   └── 5: D
+  |       |       |    └── 3: parent [-]
+  |   D   |   C   |        ├── 4: B
+  |       |       |        └── 5: C
+  +---------------+
+```
+
+While it may appear that there's a single horizonal separator and a single
+vertical separator here, that's not actually the case. Due to the tree-like
+structure of the pane splitting, the horizontal splits exist only between the
+two panes they're splitting. So, the user could move each of the horizontal
+splits independently, without affecting the other set of panes. As an example:
+
+```
+  +---------------+
+  |       |       |
+  |   A   |       |
+  +-------+   B   |
+  |       |       |
+  |   D   |       |
+  |       +-------+
+  |       |   C   |
+  +---------------+
+```
+
+### Creating a pane
+
+In the basic use case, the user will decide to split the currently focused pane.
+The currently focused pane is always a leaf, because as parent's can't be
+focused (they don't have their own terminal). When a user decides to add a new
+pane, the child will:
+
+ 1. Convert into a parent
+ 2. Move its terminal into its first child
+ 3. Split its UI in half, and display each child in one half.
+
+It's up to the app hosting the panes to tell the pane what kind of terminal in
+wants created in the new pane. By default, the new pane will be created with the
+default settings profile.
+
+### While panes are open
+
+When a tab has multiple panes open, only one is the "active" pane. This is the
+pane that was last focused in the tab. If the tab is the currently open tab,
+then this is the pane with the currently focused terminal control. When the user
+brings the tab into focus, the last focused pane is the pane that should become
+focused again.
+
+The tab's state will be updated to reflect the state of it's focused pane. The
+title text and icon of the tab will reflect that of the focused pane. Should the
+focus switch from one pane to another, the tab's text and icon should update to
+reflect the newly focused control. Any additional state that the tab would
+display for a single pane should also be reflected in the tab for a tab with
+multiple panes.
+
+While panes are open, the user should be able to move any split between panes.
+In moving the split, the sizes of the terminal controls should be resized to
+match.
+
+### Closing a pane
+
+A pane can either be closed by the user manually, or when the terminal it's
+attached to raises its ConnectionClosed event. When this happens, we should
+remove this pane from the tree. The parent of the closing pane will have to
+remove the pane as one of it's children. If the sibling of the closing pane is a
+leaf, then the parent should just take all of the state from the remaining pane.
+This will cause the remaining pane's content to expand to take the entire
+boundaries of the parent's pane. If the remaining child was a parent itself,
+then the parent will take both the children of the remaining pane, and make them
+the parent's children, as if the parent node was taken from the tree and
+replaced by the remaining child.
+
+## Future considerations
+
+The Pane implementation isn't complete in it's current form. There are many
+additional things that could be done to improve the user experience. This is by
+no means a comprehensive list.
+
+* [ ] Panes should be resizable with the mouse. The user should be able to drag
+  the separator for a pair of panes, and have the content between them resize as
+  the separator moves.
+* [ ] There's no keyboard shortcut for "ClosePane"
+* [ ] The user should be able to configure what profile is used for splitting a
+  pane. Currently, the default profile is used, but it's possible a user might
+  want to create a new pane with the parent pane's profile.
+* [ ] There should be some sort of UI to indicate that a particular pane is
+  focused, more than just the blinking cursor. `tmux` accomplishes this by
+  colorizing the separators adjacent to the active pane. Another idea is
+  displaying a small outline around the focused pane (like when tabbing through
+  controls on a webpage).
+* [ ] The user should be able to navigate the focus of panes with the keyboard,
+  instead of requiring the mouse.
+* [ ] The user should be able to zoom a pane, to make the pane take the entire
+  size of the terminal window temporarily.
+* [ ] A pane doesn't necessarily need to host a terminal. It could potentially
+  host another UIElement. One could imagine enabling a user to quickly open up a
+  Browser pane to search for a particular string without needing to leave the
+  terminal.
+
+## Footnotes
+
+### Why not top-level panes, and nested tabs?
+
+If each pane were to have it's own set of tabs, then each pane would need to
+reserve screen real estate for a row of tabs. As a user continued to split the
+window, more and more of the screen would be dedicated to just displaying a row
+of tabs, which isn't really the important part of the application, the terminal
+is.
+
+Additionally, if there were top-level panes, once the root was split, it would
+not be possible to move a single pane to be the full size of the window. The
+user would need to somehow close the other panes, to be able to make the split
+the size of the dull window.
+
+One con of this design is that if a control is hosted in a pane, the current
+design makes it hard to move out of a pane into it's own tab, or into another
+pane. This could be solved a number of ways. There could be keyboard shortcuts
+for swapping the positions of tabs, or a shortcut for both "zooming" a tab
+(temporarily making it the full size) or even popping a pane out to it's own
+tab. Additionally, a right-click menu option could be added to do the
+aformentioned actions. Discoverability of these two actions is not as high as
+just dragging a tab from one pane to another; however, it's believed that panes
+are more of a power-user scenario, and power users will not neccessarily be
+turned off by the feature's discoverability.

doc/cascadia/SettingsSchema.md

@@ -0,0 +1,76 @@
+# Profiles.json Documentation
+
+## Globals
+Properties listed below affect the entire window, regardless of the profile settings.
+
+| Property | Necessity | Type | Default | Description |
+| -------- | --------- | ---- | ------- | ----------- |
+| `alwaysShowTabs` | _Required_ | Boolean | `true` | When set to `true`, tabs are always displayed. When set to `false` and `showTabsInTitlebar` is set to `false`, tabs only appear after typing <kbd>Ctrl</kbd> + <kbd>T</kbd>. |
+| `defaultProfile` | _Required_ | String | PowerShell guid | Sets the default profile. Opens by typing <kbd>Ctrl</kbd> + <kbd>T</kbd> or by clicking the '+' icon. The guid of the desired default profile is used as the value. |
+| `initialCols` | _Required_ | Integer | `120` | The number of columns displayed in the window upon first load. |
+| `initialRows` | _Required_ | Integer | `30` | The number of rows displayed in the window upon first load. |
+| `requestedTheme` | _Required_ | String | `system` | Sets the theme of the application. Possible values: `"light"`, `"dark"`, `"system"` |
+| `showTerminalTitleInTitlebar` | _Required_ | Boolean | `true` | When set to `true`, titlebar displays the title of the selected tab. When set to `false`, titlebar displays "Windows Terminal". |
+| `showTabsInTitlebar` | Optional | Boolean | `true` | When set to `true`, the tabs are moved into the titlebar and the titlebar disappears. When set to `false`, the titlebar sits above the tabs. |
+| `wordDelimiters` | Optional | String | ` ./\\()\"'-:,.;<>~!@#$%^&*|+=[]{}~?\u2502` | Determines the delimiters used in a double click selection. |
+
+## Profiles
+Properties listed below are specific to each unique profile.
+
+| Property | Necessity | Type | Default | Description |
+| -------- | --------- | ---- | ------- | ----------- |
+| `acrylicOpacity` | _Required_ | Number | `0.5` | When `useAcrylic` is set to `true`, it sets the transparency of the window for the profile. Accepts floating point values from 0-1. |
+| `closeOnExit` | _Required_ | Boolean | `true` | When set to `true`, the selected tab closes when `exit` is typed. When set to `false`, the tab will remain open when `exit` is typed. |
+| `colorScheme` | _Required_ | String | `Campbell` | Name of the terminal color scheme to use. Color schemes are defined under `schemes`. |
+| `commandline` | _Required_ | String | `powershell.exe` | Executable used in the profile. |
+| `cursorColor` | _Required_ | String | `#FFFFFF` | Sets the cursor color for the profile. Uses hex color format: `"#rrggbb"`. |
+| `cursorShape` | _Required_ | String | `bar` | Sets the cursor shape for the profile. Possible values: `"vintage"` ( &#x2583; ), `"bar"` ( &#x2503; ), `"underscore"` ( &#x2581; ), `"filledBox"` ( &#x2588; ), `"emptyBox"` ( &#x25AF; ) |
+| `fontFace` | _Required_ | String | `Consolas` | Name of the font face used in the profile. |
+| `fontSize` | _Required_ | Integer | `10` | Sets the font size. |
+| `guid` | _Required_ | String | | Unique identifier of the profile. Written in registry format: `"{00000000-0000-0000-0000-000000000000}"`. |
+| `historySize` | _Required_ | Integer | `9001` | The number of lines above the ones displayed in the window you can scroll back to. |
+| `name` | _Required_ | String | `PowerShell Core` | Name of the profile. Displays in the dropdown menu. |
+| `padding` | _Required_ | String | `0, 0, 0, 0` | Sets the padding around the text within the window. Can have three different formats: `"#"` sets the same padding for all sides, `"#, #"` sets the same padding for left-right and top-bottom, and `"#, #, #, #"` sets the padding individually for left, top, right, and bottom. |
+| `snapOnInput` | _Required_ | Boolean | `true` | When set to `true`, the window will scroll to the command input line when typing. When set to `false`, the window will not scroll when you start typing. |
+| `startingDirectory` | _Required_ | String | `%USERPROFILE%` | The directory the shell starts in when it is loaded. |
+| `useAcrylic` | _Required_ | Boolean | `false` | When set to `true`, the window will have an acrylic background. When set to `false`, the window will have a plain, untextured background. |
+| `background` | Optional | String | | Sets the background color of the profile. Overrides `background` set in color scheme if `colorscheme` is set. Uses hex color format: `"#rrggbb"`. |
+| `colorTable` | Optional | Array[String] | | Array of colors used in the profile if `colorscheme` is not set. Colors use hex color format: `"#rrggbb"`. Ordering is as follows: `[black, red, green, yellow, blue, magenta, cyan, white, bright black, bright red, bright green, bright yellow, bright blue, bright magenta, bright cyan, bright white]` |
+| `cursorHeight` | Optional | Integer | | Sets the percentage height of the cursor starting from the bottom. Only works when `cursorShape` is set to `"vintage"`. Accepts values from 25-100. |
+| `foreground` | Optional | String | | Sets the foreground color of the profile. Overrides `foreground` set in color scheme if `colorscheme` is set. Uses hex color format: `"#rrggbb"`. |
+| `icon` | Optional | String | | Image file location of the icon used in the profile. Displays within the tab and the dropdown menu. |
+| `scrollbarState` | Optional | String | | Defines the visibility of the scrollbar. Possible values: `"visible"`, `"hidden"` |
+| `tabTitle` | Optional | String | | Overrides default title of the tab. |
+
+## Schemes
+Properties listed below are specific to each color scheme. [ColorTool](https://github.com/microsoft/terminal/tree/master/src/tools/ColorTool) is a great tool you can use to create and explore new color schemes. All colors use hex color format.
+
+| Property | Necessity | Type | Description |
+| -------- | ---- | ----------- | ----------- |
+| `name` | _Required_ | String | Name of the color scheme. |
+| `foreground` | _Required_ | String | Sets the foreground color of the color scheme. |
+| `background` | _Required_ | String | Sets the background color of the color scheme. |
+| `black` | _Required_ | String | Sets the color used as ANSI black. |
+| `blue` | _Required_ | String | Sets the color used as ANSI blue. |
+| `brightBlack` | _Required_ | String | Sets the color used as ANSI bright black. |
+| `brightBlue` | _Required_ | String | Sets the color used as ANSI bright blue. |
+| `brightCyan` | _Required_ | String | Sets the color used as ANSI bright cyan. |
+| `brightGreen` | _Required_ | String | Sets the color used as ANSI bright green. |
+| `brightPurple` | _Required_ | String | Sets the color used as ANSI bright purple. |
+| `brightRed` | _Required_ | String | Sets the color used as ANSI bright red. |
+| `brightWhite` | _Required_ | String | Sets the color used as ANSI bright white. |
+| `brightYellow` | _Required_ | String | Sets the color used as ANSI bright yellow. |
+| `cyan` | _Required_ | String | Sets the color used as ANSI cyan. |
+| `green` | _Required_ | String | Sets the color used as ANSI green. |
+| `purple` | _Required_ | String | Sets the color used as ANSI purple. |
+| `red` | _Required_ | String | Sets the color used as ANSI red. |
+| `white` | _Required_ | String | Sets the color used as ANSI white. |
+| `yellow` | _Required_ | String | Sets the color used as ANSI yellow. |
+
+## Keybindings
+Properties listed below are specific to each custom key binding.
+
+| Property | Necessity | Type | Description |
+| -------- | ---- | ----------- | ----------- |
+| `command` | _Required_ | String | The command executed when the associated key bindings are pressed. |
+| `keys` | _Required_ | Array[String] | Defines the key combinations used to call the command. |

doc/cascadia/TerminalSettings-spec.md

@@ -0,0 +1,233 @@
+# Terminal Settings
+
+* author: Mike Griese __migrie__
+* created on: 2018-Oct-23
+
+## Abstract
+
+This spec will outline how various terminal frontends will be able to interact with the settings for the terminal.
+
+## Terminology
+* **Frontend** or **Application Layer**: This is the end-user experience. This
+  could be a Terminal Application (ex. Project Cascadia) or something that's
+  embedding a terminal window inside of it (ex. Visual Studio). These frontends
+  consume the terminal component as an atomic unit.
+* **Component Layer**: This is the UI framework-dependent implementation of the
+  Terminal component. As planned currently, this is either the UWP or WPF
+  Terminal component.
+* **Terminal Layer**: This is the shared core implementation of the terminal.
+  This is the Terminal Connection, Parser/Adapter, Buffer, and Renderer (but not
+  the UX-dependant RenderEngine).
+
+## User Stories
+1. "Project Cascadia" should be able to have both global settings (such as
+   scrollbar styling) and settings that are stored per-profile (such as
+   commandline, color scheme, etc.)
+2. "Project Cascadia" should be able to load these settings at boot, use them to
+   create terminal instances, be able to edit them, and be able to save them
+   back.
+3. "Project Cascadia" should be able to have terminal instances reflect the
+   changes to the settings when the settings are changed.
+4. "Project Cascadia" should be able to host panes/tabs with different profiles
+   set at the same time.
+5. Visual Studio should be able to persist and edit settings globally, without
+   the need for a globals/profiles structure.
+6. The Terminal should be able to read information from a settings structure
+   that's independant of how it's persisted / implemented by the Application
+7. The Component should be able to have its own settings independent of the
+   application that's embedding it, such as font size and face, scrollbar
+   visibility, etc. These should be settings that are specific to the component,
+   and the Terminal should logically be unaffected by these settings.
+
+## Details
+
+Some settings will need to be Application-specific, some will need to be component-specific, and some are terminal-specific. For example:
+
+Terminal            | Component             | Frontend
+--------------------|-----------------------|------------------
+Color Table         | Font Face, size       | Status Line Visibility, contents
+Cursor Color        | Scrollbar Visibility  | ~~Window Size~~[1]
+History Size        |                       |
+Buffer Size    [1]  |                       |
+
+* [1] I believe only the "Default" or "Initial" buffer size should be the one we truly store in the settings. When the app first boots up, it can use that value to with the font size to figure out how big its window should be. When additional tabs/panes are created, they should inherit the size of the existing window. Similarly, VS could first calculate how much space it has available, then override that value when creating the terminal.
+
+Project Cascadia needs to be able to persist settings as a bipartite globals-profiles structure.
+VS needs to be able to persist settings just as a simple set of global settings.
+
+When the application needs to retrieve these settings, they need to use them as a tripartite structure: frontend-component-terminal settings.
+
+Each frontend will have its own set of settings.
+Each component implementation will also ned to have some settings that control it.
+The terminal also will have some settings specific to the terminal.
+
+### Globals and Profiles
+With \*nix-like terminals, settings are typically structured as two parts:
+  Globals and Profiles.
+
+Globals are settings that affect the entirety of the terminal application. They wouldn't be different from one pane to the next. An example is the Terminal KeyBindings - these should be the same for all tabs/panes that are running as a part of the terminal application.
+
+Profiles are what you might consider per-application settings. These are settings that can be different from one terminal instance to the next. One of the primary differentiators between profiles is the commandline used to start the terminal instance - this enables the user to have both a `cmd` profile and a `powershell` profile, for example. Things like the color table/scheme, font size, history length, these all change per-profile.
+
+Per-Profile             | Globals
+------------------------|------------------------
+Color Table             | Keybindings
+Cursor Color            | Scrollbar Visibility
+History Size            | Status Line Visibility, contents
+Font Face, size         | Window Size
+Shell Commandline       |
+
+### Simple Settings
+
+An application like VS might not even care about settings profiles. They should be able to persist the settings as just a singular entity, and change those as needed, without the additional overhead. Profiles will be something that's more specifc to Project Cascadia.
+
+### Interface Descriptions
+
+```csharp
+public class TerminalSettings
+{
+    Color DefaultForeground;
+    Color DefaultBackground;
+    Color[] ColorTable;
+    Coord? Dimensions;
+    int HistorySize;
+    Color CursorColor;
+    CursorShape CursorShape;
+}
+
+public interface IComponentSettings
+{
+    TerminalSettings TerminalSettings { get; }
+}
+
+public interface IApplicationSettings
+{
+    IComponentSettings ComponentSettings { get; }
+}
+```
+
+The Application can store whatever settings it wants in its implementation of `IApplicationSettings`. When it instantiates a Terminal Component, it will pass its `IComponentSettings` to it.
+
+The component will retrieve whatever settings it wants from that object, and then pass the `TerminalSettings` to the Terminal it creates.
+
+
+The frontend will be able to get/set its settings from the `IApplicationSettings` implementation.
+The frontend will be able to create components using the `IComponentSettings` in its `IApplicationSettings`.
+The Component will then create the Terminal using the `TerminalSettings`.
+
+#### Project Cascadia Settings Details
+
+The `CascadiaSettings` will store the settings as two parts:
+* A set of global data & settings
+* A list of Profiles, that each have more data
+
+When Cascadia starts up, it'll load all the settings, including the Globals and profiles. The Globals will also tell us which profile is the "Default" profile we should use to instantiate the terminal.
+Using the globals and the Profile, it'll convert those to a `ApplicationSettings : IApplicationSettings`.
+It'll read data from that `ApplicationSettings` to initialize things it needs to know.
+* It'll determine whether or not to display the status line
+* It'll query the Component settings for the default size of the component, so it knows how big of a space it needs to reserve for it
+
+It'll then instantiate a `UWPTerminalComponent` and pass it the `UWPComponentSettings`.
+
+This is a rough draft of what these members might all be like.
+```csharp
+class CascadiaSettings
+{
+    void LoadAll();
+    void SaveAll();
+    GlobalAppSettings Globals;
+    List<Profile> Profiles;
+    ApplicationSettings ToSettings(GlobalAppSettings globals, Profile profile);
+    void Update(ApplicationSettings appSettings, GUID profileID);
+}
+class Profile
+{
+    GUID ProfileGuid;
+    string Name;
+    string Commandline;
+    TerminalSettings TerminalSettings;
+    string FontFace;
+    int FontSize;
+    float acrylicTransparency;
+    bool useAcrylic;
+}
+class GlobalAppSettings
+{
+    GUID defaultProfile;
+    Keybindings keybindings;
+    bool showScrollbars;
+    bool showStatusline;
+}
+
+class ApplicationSettings : IApplicationSettings
+{
+    UWPComponentSettings ComponentSettings;
+    Keybindings keybindings;
+    bool showStatusline;
+}
+class UWPComponentSettings : IComponentSettings
+{
+    Point GetDefaultComponentSize();
+    TerminalSettings TerminalSettings;
+    string FontFace;
+    int FontSize;
+    bool showScrollbars;
+    float acrylicTransparency;
+    bool useAcrylic;
+}
+```
+
+### Updating Settings
+
+What happens when the user changes the application's settings? The App,
+  Component, and Terminal might all need to update their settings.
+The component will expose a `UpdateSettings()` method that will cause the
+  Component and Terminal to reload the settings from their settings objects.
+
+```csharp
+interface ITerminalComponent
+{
+    void UpdateSettings(IComponentSettings componentSettings);
+}
+partial class UWPTerminalComponent : ITerminalComponent
+{
+    void UpdateSettings(IComponentSettings componentSettings)
+    {
+        // Recalculate GlyphTypeFace
+        // Recalculate rows/cols using current geometry and typeface
+        // Update our terminal instance:
+        terminal.UpdateSettings(componentSettings.TerminalSettings);
+    }
+}
+```
+#### Updating settings in Project Cascadia
+
+However, when Cascadia's settings change, we're going to possibly change some global settings and possibly some profile settings. The profile's that are changed may or may not be currently active.
+
+> Say we have two different panes open with different profiles (A and B).
+> What happens if we change the settings for one profile's font and not the other's?
+> ~~We resize the height of the terminal to account for the change in height of the win~~
+>
+> We should never change the window size in response to a settings change if there is more than one tab/pane open.
+> > never?
+
+Cascadia would have to maintain a mapping of which components have which profiles:
+```csharp
+class CascadiaTerminalInstance
+{
+    GUID ProfileGuid;
+    UWPTerminalComponent component;
+}
+```
+
+Then, when the settings are closed, it'll enumerate all of the components it has loaded, and apply the updated settings to them. It'll do this by looking up the profile GUID of the component, then getting the `ApplicationSettings` for the profile, then calling `UpdateSettings` on the component.
+
+~~We need to have a way so that only the currently foreground component can change the window size.~~
+I don't like that - if we change the font size, we should just recalculate how many characters can fit in the current window size.
+
+## Questions / TODO
+* How does this interplay with setting properties of the terminal component in XAML?
+    * I would think that the component would load the XAML properties first, and if the controlling application calls `UpdateSettings` on the component, then those in-XAML properties would likely get overwritten.
+    * It's not necessary to create the component with a `IComponentSettings`, nor is it necessary to call `UpdateSettings`. If you wanted to create a trivial settings-less terminal component entriely in XAML, go right ahead.
+    * Any settings that *are* exposed through XAML properties *should* also be exposed in the component's settings implementation as well.
+        * Can that be enforced any way? I doubt it.

doc/cascadia/Unittesting-CppWinRT-Xaml.md

@@ -0,0 +1,527 @@
+# Getting TAEF unittests to work with a C++/WinRT XAML Islands application
+
+* __Author__: Mike Griese @zadjii-msft
+* __Created on__: 2019-06-06
+
+
+So you've built a Win32 application that uses XAML Islands to display it's UI
+with C++/WinRT. How do you go about adding unittests to this application? I'm
+going to cover the steps that I took to get the Windows Terminal updated to be
+able to test not only our C++/WinRT components, but also pure c++ classes that
+were used in the application, and components that used XAML UI elements.
+
+## Prerequisites
+
+Make sure you're using at least the 2.0.190605.7 version of the CppWinRT nuget
+package. Prior to this version, there are some bugs with C++/WinRT's detection
+of static lib dependencies. You might be able to get your build working with
+Visual Studio on earlier versions, but not straight from MsBuild.
+
+Also, if you're going to be running your tests in a CI build of some sort, make
+sure that your tests are running on a machine running at least Windows 18362. If
+your CI isn't running that version, then this doesn't matter at all.
+
+Furthermore, you may need an updated TAEF package as well. Our CI uses the TAEF
+VsTest adapter to allow ADO to run TAEF tests in CI. However, there's a bug in
+the tests adapter that prevents it from running tests in a UAP context. The
+`10.38.190605002` TAEF is the most recent release at the time of writing,
+however, that doesn't have the fix necessary. Fortunately, the TAEF team was
+kind enough to prototype a fix for us, which is the version
+`10.38.190610001-uapadmin`, which we're using in this repo until an official
+release with the fix is available.
+
+## Move the C++/WinRT implementation to a static lib
+
+By default, most (newly authored) C++/WinRT components are authored as a dll
+that can be used to activate your types. However, you might have other classes
+in that binary that you want to be able to test, which aren't winrt types. If
+the implementation is sitting in a DLL, it'll be hard to write a TAEF unittest
+dll that can call the pure c++ types you've defined.
+
+The first thing you're going to need to do is move the implementation of your
+winrt component from a dll to a static lib. Once you have the static lib, we'll
+be able to link it into the dll you were previously producing, as well as being
+able to link it into the dll we'll be using to test the types. Once this is
+complete, your dll project will exist as little more than some extra packaging
+for your new lib, as all your code will be built by the lib.
+
+To aid in this description, I'll be referring to the projects that we changed.
+The dll project we changed to a lib was the `TerminalApp` project. From it, we
+created a new `TerminalAppLib` project, and changed `TerminalApp` to create a
+dll by linking the lib `TerminalAppLib` produced.
+
+### Create the static lib project
+
+We'll start by creating a new static lib project. The easiest way to do this is
+by copying your existing dll `vcxproj` file into a new file. Make sure to change
+the `ProjectGuid` and to add the new project to your `.sln` file. Then, change
+the `ConfigurationType` to `StaticLibrary`. This Lib should be responsible for
+building all of your headers, `.cpp` files, `.idl`s for your winrt types, and
+any `.xaml` files you might have.
+
+You'll likely need to place this new file into a separate directory from the
+existing dll project, as C++/WinRT uses the project directory as the root of the
+intermediate build tree. Each directory should only have one `.vcxproj` file in
+it. For the Terminal project, we created a subdirectory `lib/` underneath
+`TerminalApp/`, and updated the `Include` paths to properly point at the
+original files. You could alternatively put all the source in one directory, and
+have separate `dll/` and `lib/` subdirectories from the source that are solely
+responsible for building their binary.
+
+At this point, you might face some difficulty including the right wimnd
+references, especially from other C++/WinRT dependencies for this project that
+exist in your solution. I don't know why, but I had a fair amount of difficulty
+using a `ProjectReference` from a C++/WinRT StaticLibrary to another C++/WinRT
+project in my solution. If you're referring to any other projects, you'll need
+to set up a reference to their built `.winmd`'s manually.
+
+As an example, here's how we've added a reference to the `TerminalSettings`
+project from our `TerminalAppLib` project:
+
+```xml
+  <ItemGroup>
+    <!-- Manually add references to each of our dependent winmds. Mark them as
+    private=false and CopyLocalSatelliteAssemblies=false, so that we don't
+    propogate them upwards (which can make referencing this project result in
+    duplicate type definitions)-->
+
+    <Reference Include="Microsoft.Terminal.Settings">
+      <HintPath>$(SolutionDir)$(Platform)\$(Configuration)\TerminalSettings\Microsoft.Terminal.Settings.winmd</HintPath>
+      <IsWinMDFile>true</IsWinMDFile>
+      <Private>false</Private>
+      <CopyLocalSatelliteAssemblies>false</CopyLocalSatelliteAssemblies>
+    </Reference>
+  </ItemGroup>
+```
+
+The `HintPath` may be different depending on your project structure - verify
+locally the right path to the `.winmd` file you're looking for.
+
+Notably, you'll also need to put a `pch.h` and `pch.cpp` in the new lib's
+directory, and use them instead of the `pch.h` used by the dll. C++/WinRT will be
+very angry with you if you try to use a `pch.h` in another directory. Since
+we're putting all the code into the static lib project, take your existing
+`pch.h` and move it to the lib project's directory and create an empty `pch.h`
+in the dll project's directory.
+
+### Update the dll project
+
+Now that we havea lib that builds all your code, we can go ahead and tear out
+most of the dead code from the old dll project. Remove all the source files from
+the dll's `.vcxproj` file, save for the `pch.h` and `pch.cpp` files. You _may_
+need to leave the headers for any C++/WinRT types you've authored in this project
+- I'm not totally sure it's necessary.
+
+Now, to link the static lib we've created. For whatever reason, adding a
+`ProjectReference` to the static lib doesn't work. So, we'll need to manually
+link the lib from the lib project. You can do that by adding the lib's output
+dir to your `AdditionalLibraryDirectories`, and adding the lib to your
+`AdditionalDependencies`, like so:
+
+```xml
+  <ItemDefinitionGroup>
+    <Link>
+      <!-- Manually link with the TerminalAppLib.lib we've built. -->
+      <AdditionalLibraryDirectories>$(SolutionDir)\$(Platform)\$(Configuration)\TerminalAppLib;%(AdditionalLibraryDirectories)</AdditionalLibraryDirectories>
+
+      <AdditionalDependencies>TerminalAppLib.lib;%(AdditionalDependencies)</AdditionalDependencies>
+    </Link>
+  </ItemDefinitionGroup>
+```
+
+We are NOT adding a reference to the static lib project's .winmd here. As of the
+2.0.190605.7 CppWinRT nuget package, this is enough for MsBuild and Visual
+Studio to be able to determine that the static lib's  `.winmd` should be included
+in this package.
+
+At this point, you might have some mdmerge errors, which complain about
+duplicate types in one of your dependencies. This might especially happen if one
+of your dependencies (ex `A.dll`) is also a dependency for one of your _other_
+dependencies (ex `B.dll`). In this example, your final output project `C.dll`
+depends on both `A.dll` and `B.dll`, and `B.dll` _also_ depends on `A.dll`. If
+you're seeing this, I recommend adding `Private=false` and
+`CopyLocalSatelliteAssemblies=false` to your dependent dlls. In this example,
+add similar code to `B.dll`:
+
+```xml
+    <ProjectReference Include="$(SolutionDir)src\cascadia\TerminalSettings\TerminalSettings.vcxproj">
+      <Private>false</Private>
+      <CopyLocalSatelliteAssemblies>false</CopyLocalSatelliteAssemblies>
+    </ProjectReference>
+```
+
+where `TerminalSettings` is your `A.dll`, which is included by both `B` and `C`.
+
+We additionally had an `.exe` project that was including our `TerminalApp`
+project, and all its `.xbf` and `.pri` files. If you have a similar project
+aggregating all your resources, you might need to update the paths to point to
+the new static lib project.
+
+At this point, you should be able to rebuild your solution, and everything
+should be working just the same as before.
+
+
+## Add TAEF Tests
+
+Now that you have a static library project, you can start building your unittest
+dll. Start by creating a new directory for your unittest code, and creating a
+`.vcxproj` for a TAEF unittest dll. For the Terminal solution, we use the TAEF
+nuget package `Taef.Redist.Wlk`.
+
+### Referencing your C++/WinRT static lib
+
+This step is the easiest. Add a `ProjectReference` to your static lib project,
+and your lib will be linked into your unittest dll.
+
+```xml
+    <ProjectReference Include="$(SolutionDir)\src\cascadia\TerminalApp\lib\TerminalAppLib.vcxproj" />
+```
+
+Congratulations, you can now instantiate the pure c++ types you've authored in
+your static lib. But what if you want to test your C++/WinRT types too?
+
+### Using your C++/WinRT types
+
+To be able to instantiate your C++/WinRT types in a TAEF unittest, you'll need
+to rely on a new feature to Windows in version 1903 which enables unpackaged
+activation of WinRT types. To do this, we'll need to author a SxS manifest that
+lists each of our types, and include it in the dll, and also activate it
+manually from TAEF.
+
+#### Creating the manifest
+
+First, you need to create a manifest file that lists each dll your test depends
+upon, and each of the types in that dll. For example, here's an excerpt from the
+Terminal's manifest:
+
+```xml
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
+  <file name="TerminalSettings.dll" hashalg="SHA1">
+    <activatableClass name="Microsoft.Terminal.Settings.KeyChord" threadingModel="both" xmlns="urn:schemas-microsoft-com:winrt.v1"></activatableClass>
+    <activatableClass name="Microsoft.Terminal.Settings.TerminalSettings" threadingModel="both" xmlns="urn:schemas-microsoft-com:winrt.v1"></activatableClass>
+  </file>
+  <file name="TerminalApp.dll" hashalg="SHA1">
+    <activatableClass name="TerminalApp.App" threadingModel="both" xmlns="urn:schemas-microsoft-com:winrt.v1"></activatableClass>
+    <activatableClass name="TerminalApp.AppKeyBindings" threadingModel="both" xmlns="urn:schemas-microsoft-com:winrt.v1"></activatableClass>
+    <activatableClass name="TerminalApp.XamlmetaDataProvider" threadingModel="both" xmlns="urn:schemas-microsoft-com:winrt.v1"></activatableClass>
+  </file>
+</assembly>
+```
+
+Here we have two dlls that we depend upon, `TerminalSettings.dll` and
+`TerminalApp.dll`. `TerminalSettings` implements two types,
+`Microsoft.Terminal.Settings.KeyChord` and
+`Microsoft.Terminal.Settings.TerminalSettings`.
+
+#### Linking the manifest to the test dll
+
+Now that we have a manifest file, we need to embed it in your unittest dll. This
+is done with the following properties in your `vcxproj` file:
+
+```xml
+  <PropertyGroup>
+    <GenerateManifest>true</GenerateManifest>
+    <EmbedManifest>true</EmbedManifest>
+  </PropertyGroup>
+  <ItemGroup>
+    <Manifest Include="TerminalApp.Unit.Tests.manifest" />
+  </ItemGroup>
+```
+where `TerminalApp.Unit.Tests.manifest` is the name of your manifest file.
+
+Additionally, you'll need to binplace the manifest _adjacent to your test
+binary_, so TAEF can find it at runtime. I've done this in the following way,
+though I'm sure there's a better way:
+
+```xml
+  <ItemDefinitionGroup>
+    <PostBuildEvent>
+      <!-- Manually copy the manifest to our outdir, because the test will need
+      to find it adjacent to us. -->
+      <Command>
+        (xcopy /Y &quot;$(OpenConsoleDir)src\cascadia\ut_app\TerminalApp.Unit.Tests.manifest&quot; &quot;$(OutDir)\TerminalApp.Unit.Tests.manifest*&quot; )
+      </Command>
+    </PostBuildEvent>
+  </ItemDefinitionGroup>
+```
+
+#### Copying your dependencies
+
+Additionally, any dlls that implement any types your test is dependent upon will
+also need to be in the output directory for the test. Manually copy those DLLs
+to the tests' output directory too. The updated `PostBuildEvent` looks like
+this:
+
+```xml
+  <ItemDefinitionGroup>
+    <PostBuildEvent>
+      <Command>
+        echo OutDir=$(OutDir)
+        (xcopy /Y &quot;$(SolutionDir)src\cascadia\ut_app\TerminalApp.Unit.Tests.manifest&quot; &quot;$(OutDir)\TerminalApp.Unit.Tests.manifest*&quot; )
+
+        (xcopy /Y &quot;$(SolutionDir)$(Platform)\$(Configuration)\TerminalConnection\TerminalConnection.dll&quot; &quot;$(OutDir)\TerminalConnection.dll*&quot; )
+        (xcopy /Y &quot;$(SolutionDir)$(Platform)\$(Configuration)\TerminalSettings\TerminalSettings.dll&quot; &quot;$(OutDir)\TerminalSettings.dll*&quot; )
+        (xcopy /Y &quot;$(SolutionDir)$(Platform)\$(Configuration)\TerminalControl\TerminalControl.dll&quot; &quot;$(OutDir)\TerminalControl.dll*&quot; )
+      </Command>
+    </PostBuildEvent>
+  </ItemDefinitionGroup>
+```
+
+Again, verify the correct paths to your dependant C++/WinRT dlls, as they may be
+different than the above
+
+#### Activating the manifest from TAEF
+
+Now that the manifest lives adjacent to your test dll, and all your dependent
+dlls are also adjacent to the unittest dll, there's only one thing left to do.
+TAEF will not use your dll's manifest by default, so you'll need to add a
+property to your test class/method to tell TAEF to do so. You can do this with
+the following:
+
+```c++
+class SettingsTests
+{
+    // Use a custom manifest to ensure that we can activate winrt types from
+    // our test. This property will tell taef to manually use this as the
+    // sxs manifest during this test class. It includes all the C++/WinRT
+    // types we've defined, so if your test is crashing for an unknown
+    // reason, make sure it's included in that file.
+    BEGIN_TEST_CLASS(SettingsTests)
+        TEST_CLASS_PROPERTY(L"ActivationContext", L"TerminalApp.Unit.Tests.manifest")
+    END_TEST_CLASS()
+
+    // Other Test code here
+}
+```
+
+Now, if you try to add any test methods that instantiate WinRT types you've
+authored, they'll work. That is of course, so long as they don't use XAML. If
+you want to use any XAML types, then you'll have to keep reading.
+
+### Using Xaml Types (with XAML Islands)
+
+To be able to instatiate XAML types in your unittest, we'll need to make use of
+the [XAML Hosting
+API](https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/using-the-xaml-hosting-api)
+(Xaml Islands). This enables you to use XAML APIs from a Win32 context.
+
+
+#### Adding XAML Hosting code
+
+First and foremost, you'll need to add the following to your test's `precomp.h`:
+
+```c++
+#include <winrt/Windows.system.h>
+#include <winrt/Windows.Foundation.Collections.h>
+#include <winrt/Windows.UI.Xaml.Hosting.h>
+#include <windows.ui.xaml.hosting.desktopwindowxamlsource.h>
+```
+
+If you hit a compile warning that refers to `GetCurrentTime`, you'll probably
+also need the following, after you've `#include`'d `Windows.h`:
+
+```c++
+#ifdef GetCurrentTime
+#undef GetCurrentTime
+#endif
+```
+
+Then, somewhere in your test code, you'll need to start up Xaml Islands. I've done this in my `TEST_CLASS_SETUP`, so that I only create it once, and re-use it for each method.
+
+```c++
+
+class TabTests
+{
+    TEST_CLASS_SETUP(ClassSetup)
+    {
+        winrt::init_apartment(winrt::apartment_type::single_threaded);
+        // Initialize the Xaml Hosting Manager
+        _manager = winrt::Windows::UI::Xaml::Hosting::WindowsXamlManager::InitializeForCurrentThread();
+        _source = winrt::Windows::UI::Xaml::Hosting::DesktopWindowXamlSource{};
+
+        return true;
+    }
+
+private:
+    winrt::Windows::UI::Xaml::Hosting::WindowsXamlManager _manager{ nullptr };
+    winrt::Windows::UI::Xaml::Hosting::DesktopWindowXamlSource _source{ nullptr };
+```
+
+#### Authoring your test's `AppxManifest.xml`
+
+This alone however is not enough to get XAML Islands to work. There was a fairly
+substantial change to the XAML Hosting API around Windows build 18295, so it
+explicitly requires that you have your executable's manifest set
+`maxversiontested` to higher than that version. However, because TAEF's `te.exe`
+is not so manifested, we can't just use our SxS manifest from before to set that
+version. Instead, you'll need to make TAEF run your test binary in a packaged
+content, with our own appxmanifest.
+
+To do this, we'll need to author an `Appxmanifest.xml` to use with the test, and
+associate that manifest with the test.
+
+Here's the AppxManifest we're using:
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<Package xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities" xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10" xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10" IgnorableNamespaces="uap">
+
+  <Identity Name="TerminalApp.Unit.Tests.Package"
+          ProcessorArchitecture="neutral"
+          Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"
+          Version="1.0.0.0"
+          ResourceId="en-us" />
+  <Properties>
+    <DisplayName>TerminalApp.Unit.Tests.Package Host Process</DisplayName>
+    <PublisherDisplayName>Microsoft Corp.</PublisherDisplayName>
+    <Logo>taef.png</Logo>
+    <Description>TAEF Packaged Cwa FullTrust Application Host Process</Description>
+  </Properties>
+
+  <Dependencies>
+    <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.18362.0" MaxVersionTested="10.0.18362.0" />
+    <PackageDependency Name="Microsoft.VCLibs.140.00.Debug" MinVersion="14.0.27023.1" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
+    <PackageDependency Name="Microsoft.VCLibs.140.00.Debug.UWPDesktop" MinVersion="14.0.27027.1" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
+  </Dependencies>
+
+  <Resources>
+    <Resource Language="en-us" />
+  </Resources>
+
+  <Applications>
+    <Application Id="TE.ProcessHost" Executable="TE.ProcessHost.exe" EntryPoint="Windows.FullTrustApplication">
+      <uap:VisualElements DisplayName="TAEF Packaged Cwa FullTrust Application Host Process" Square150x150Logo="taef.png" Square44x44Logo="taef.png" Description="TAEF Packaged Cwa Application Host Process" BackgroundColor="#222222">
+        <uap:SplashScreen Image="taef.png" />
+      </uap:VisualElements>
+    </Application>
+  </Applications>
+
+  <Capabilities>
+    <rescap:Capability Name="runFullTrust"/>
+  </Capabilities>
+
+  <Extensions>
+    <Extension Category="windows.activatableClass.inProcessServer">
+      <InProcessServer>
+        <Path>TerminalSettings.dll</Path>
+        <ActivatableClass ActivatableClassId="Microsoft.Terminal.Settings.TerminalSettings" ThreadingModel="both" />
+        <ActivatableClass ActivatableClassId="Microsoft.Terminal.Settings.KeyChord" ThreadingModel="both" />
+      </InProcessServer>
+    </Extension>
+    <!-- More extensions here -->
+  </Extensions>
+</Package>
+```
+
+Change the `Identity.Name` and `Properties.DisplayName` to be more appropriate
+for your test, as well as other properties if you feel the need. TAEF will
+deploy the test package and remove it from your machine during testing, so it
+doesn't terribly matter what these values are.
+
+MAKE SURE that `MaxVersionTested` is higher than `10.0.18295.0`. If it isn't,
+XAML islands will still prevent you from activating it.
+
+UNDER NO CIRCUMSTANCE should you change the `<Application Id="TE.ProcessHost"
+Executable="TE.ProcessHost.exe" EntryPoint="Windows.FullTrustApplication">`
+line. This is how TAEF activates the TAEF host for your test binary. You might
+get a warning about `TE.ProcessHost.exe` being deprecated in favor of
+`TE.ProcessHost.UAP.exe`, but I haven't had success with the UAP version.
+
+Lower in the file, you'll see the `Extensions` block. In here you'll put each of
+the winrt dependencies that your test needs, much like we did for the previous
+manifest. Note that the syntax is _not_ exactly the same as the SxS manifest.
+
+#### Copy the AppxManifest to your `$(OutDir)`
+
+Again, we'll need to copy this appxmanifest adjacent to the test binary so we
+can load it from the test. We'll do this similar to how we did the SxS manifest
+before. The complete `PostBuildEvent` now looks like this:
+
+```xml
+  <ItemDefinitionGroup>
+    <PostBuildEvent>
+      <Command>
+        (xcopy /Y &quot;$(SolutionDir)src\cascadia\ut_app\TerminalApp.Unit.Tests.manifest&quot; &quot;$(OutDir)\TerminalApp.Unit.Tests.manifest*&quot; )
+
+        (xcopy /Y &quot;$(SolutionDir)src\cascadia\ut_app\TerminalApp.Unit.Tests.AppxManifest.xml&quot; &quot;$(OutDir)\TerminalApp.Unit.Tests.AppxManifest.xml*&quot; )
+
+        (xcopy /Y &quot;$(SolutionDir)$(Platform)\$(Configuration)\TerminalConnection\TerminalConnection.dll&quot; &quot;$(OutDir)\TerminalConnection.dll*&quot; )
+        (xcopy /Y &quot;$(SolutionDir)$(Platform)\$(Configuration)\TerminalSettings\TerminalSettings.dll&quot; &quot;$(OutDir)\TerminalSettings.dll*&quot; )
+        (xcopy /Y &quot;$(SolutionDir)$(Platform)\$(Configuration)\TerminalControl\TerminalControl.dll&quot; &quot;$(OutDir)\TerminalControl.dll*&quot; )
+      </Command>
+    </PostBuildEvent>
+  </ItemDefinitionGroup>
+```
+
+The new line here is the line referencing
+`TerminalApp.Unit.Tests.AppxManifest.xml`. You can only have one
+`PostBuildEvent` per project, so don't go re-defining it for each additional
+step - MsBuild will only use the last one. Again, this is probably not the best
+way of copying these files over, but it works.
+
+#### Use the AppxManifest in the test code
+
+Now that we have the AppxManifest being binplaced next to our test, we can
+finally reference it in the test. Instead of using the `ActivationContext` from
+before, we'll use two new properties to tell TAEF to run this test as a package,
+and to use our manifest as the AppxManifest for the package.
+
+```c++
+    BEGIN_TEST_CLASS(TabTests)
+        TEST_CLASS_PROPERTY(L"RunAs", L"UAP")
+        TEST_CLASS_PROPERTY(L"UAP:AppXManifest", L"TerminalApp.Unit.Tests.AppxManifest.xml")
+    END_TEST_CLASS()
+```
+
+The complete Xaml Hosting test now looks like this:
+
+```c++
+    class TabTests
+    {
+        BEGIN_TEST_CLASS(TabTests)
+            TEST_CLASS_PROPERTY(L"RunAs", L"UAP")
+            TEST_CLASS_PROPERTY(L"UAP:AppXManifest", L"TerminalApp.Unit.Tests.AppxManifest.xml")
+        END_TEST_CLASS()
+
+        TEST_METHOD(TryCreateXamlObjects);
+
+        TEST_CLASS_SETUP(ClassSetup)
+        {
+            winrt::init_apartment(winrt::apartment_type::single_threaded);
+            // Initialize the Xaml Hosting Manager
+            _manager = winrt::Windows::UI::Xaml::Hosting::WindowsXamlManager::InitializeForCurrentThread();
+            _source = winrt::Windows::UI::Xaml::Hosting::DesktopWindowXamlSource{};
+
+            return true;
+        }
+
+    private:
+        winrt::Windows::UI::Xaml::Hosting::WindowsXamlManager _manager{ nullptr };
+        winrt::Windows::UI::Xaml::Hosting::DesktopWindowXamlSource _source{ nullptr };
+    };
+    void TabTests::TryCreateXamlObjects(){ ... }
+```
+
+Congratulations, you can now use XAML types from your unittest.
+
+### Using types from `Microsoft.UI.Xaml`
+
+Let's say you're extra crazy and you're using the `Microsoft.UI.Xaml` nuget
+package. If you've followed all the steps above exactly, you're probably already
+fine! You've already put the types in your appxmanifest (there are a lot of
+them). You should be able to call the `Microsoft.UI.Xaml` types without any
+problems.
+
+This is because of a few key lines we already put in the appxmanifest:
+
+```xml
+  <Dependencies>
+    <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.18362.0" MaxVersionTested="10.0.18362.0" />
+    <PackageDependency Name="Microsoft.VCLibs.140.00.Debug" MinVersion="14.0.27023.1" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
+    <PackageDependency Name="Microsoft.VCLibs.140.00.Debug.UWPDesktop" MinVersion="14.0.27027.1" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
+  </Dependencies>
+```
+
+Without these `PackageDependency` entries for the VCLibs, Microsoft.UI.Xaml.dll
+will not be able to load.

doc/contributing.md

@@ -0,0 +1,155 @@
+# Terminal Contributor's Guide
+
+Below is our guidance for how to report issues, propose new features, and submit contributions via Pull Requests (PRs).
+
+## Open Development Workflow
+
+The Windows Terminal team is VERY active in this GitHub Repo. In fact, we live in it all day long and carry out all our development in the open!
+
+When the team finds issues we file them in the repo. When we propose new ideas or think-up new features, we file new feature requests. When we work on fixes or features, we create branches and work on those improvements. And when PRs are reviewed, we review in public - including all the good, the bad, and the ugly parts.
+
+The point of doing all this work in public is to ensure that we are holding ourselves to a high degree of transparency, and so that the community sees that we apply the same processes and hold ourselves to the same quality-bar as we do to community-submitted issues and PRs. We also want to make sure that we expose our team culture and "tribal knowledge" that is inherent in any closely-knit team, which often contains considerable value to those new to the project who are trying to figure out "why the heck does this thing look/work like this???"
+
+### Repo Bot
+
+The team triages new issues several times a week. During triage, the team uses labels to categorize, manage, and drive the project workflow.
+
+We employ [a bot engine](https://github.com/microsoft/terminal/blob/master/doc/bot.md) to help us automate common processes within our workflow.
+
+We drive the bot by tagging issues with specific labels which cause the bot engine to close issues, merge branches, etc. This bot engine helps us keep the repo clean by automating the process of notifying appropriate parties if/when information/follow-up is needed, and closing stale issues/PRs after reminders have remained unanswered for several days.
+
+Therefore, if you do file issues, or create PRs, please keep an eye on your GitHub notifications. If you do not respond to requests for information, your issues/PRs may be closed automatically.
+
+---
+
+## Before you start, file an issue
+
+Please follow this simple rule to help us eliminate any unnecessary wasted effort & frustration, and ensure an efficient and effective use of everyone's time - yours, ours, and other community members':
+
+> 👉 If you have a question, think you've discovered an issue, would like to propose a new feature, etc., then find/file an issue **BEFORE** starting work to fix/implement it.
+
+### Search existing issues first
+
+Before filing a new issue, search existing open and closed issues first: This project is moving fast! It is likely someone else has found the problem you're seeing, and someone may be working on or have already contributed a fix!
+
+If no existing item describes your issue/feature, great - please file a new issue:
+
+### File a new Issue
+
+* Don't know whether you're reporting an issue or requesting a feature? File an issue
+* Have a question that you don't see answered in docs, videos, etc.? File an issue
+* Want to know if we're planning on building a particular feature? File an issue
+* Got a great idea for a new feature? File an issue/request/idea
+* Don't understand how to do something? File an issue/Community Guidance Request
+* Found an existing issue that describes yours? Great - upvote and add additional commentary / info / repro-steps / etc.
+
+When you hit "New Issue", select the type of issue closest to what you want to report/ask/request:
+![New issue types](/doc/images/new-issue-template.png)
+
+### Complete the template
+
+**Complete the information requested in the issue template, providing as much information as possible**. The more information you provide, the more likely your issue/ask will be understood and implemented. Helpful information includes:
+
+* What device you're running (inc. CPU type, memory, disk, etc.)
+* What build of Windows your device is running
+
+  👉 Tip: Run the following in PowerShell Core
+
+  ```powershell
+  C:\> $PSVersionTable.OS
+  Microsoft Windows 10.0.18909
+  ```
+
+  ... or in Windows PowerShell
+
+  ```powershell
+  C:\> $PSVersionTable.BuildVersion
+
+  Major  Minor  Build  Revision
+  -----  -----  -----  --------
+  10     0      18912  1001
+  ```
+
+  ... or Cmd:
+
+  ```cmd
+  C:\> ver
+
+  Microsoft Windows [Version 10.0.18900.1001]
+  ```
+
+* What tools and apps you're using (e.g. VS 2019, VSCode, etc.)
+* Don't assume we're experts in setting up YOUR environment and don't assume we are experts in `<your distro/tool of choice>`. Teach us to help you!
+* **We LOVE detailed repro steps!** What steps do we need to take to reproduce the issue? Assume we love to read repro steps. As much detail as you can stand is probably _barely_ enough detail for us!
+* If you're reporting a particular character/glyph not rendering correctly, the specific Unicode codepoint would be MOST welcome (e.g. U+1F4AF, U+4382)
+* Prefer error message text where possible or screenshots of errors if text cannot be captured
+* We MUCH prefer text command-line script than screenshots of command-line script.
+* **If you intend to implement the fix/feature yourself then say so!** If you do not indicate otherwise we will assume that the issue is our to solve, or may label the issue as `Help-Wanted`.
+
+### DO NOT post "+1" comments
+
+> ⚠ DO NOT post "+1", "me too", or similar comments - they just add noise to an issue.
+
+If you don't have any additional info/context to add but would like to indicate that you're affected by the issue, upvote the original issue by clicking its [+😊] button and hitting 👍 (+1) icon. This way we can actually measure how impactful an issue is.
+
+---
+
+## Contributing fixes / features
+
+For those able & willing to help fix issues and/or implement features ...
+
+### To Spec or not to Spec
+
+Some issues/features may be quick and simple to describe and understand. For such scenarios, once a team member has agreed with your approach, skip ahead to the section headed "Fork, Branch, and Create your PR", below.
+
+Small issues that do not require a spec will be labelled Issue-Bug or Issue-Task.
+
+However, some issues/features will require careful thought & formal design before implementation. For these scenarios, we'll request that a spec is written and the associated issue will be labeled Issue-Feature.
+
+Specs help collaborators discuss different approaches to solve a problem, describe how the feature will behave, how the feature will impact the user, what happens if something goes wrong, etc. Driving towards agreement in a spec, before any code is written, often results in simpler code, and less wasted effort in the long run.
+
+Specs will be managed in a very similar manner as code contributions so please follow the "Fork, Branch and Create your PR" below.
+
+### Writing / Contributing-to a Spec
+
+To write/contribute to a spec: fork, branch and commit via PRs, as you would with any code changes.
+
+Specs are written in markdown, stored under the `\doc\spec` folder and named `[issue id] - [spec description].md`.
+
+👉 **It is important to follow the spec templates and complete the requested information**. The available spec templates will help ensure that specs contain the minimum information & decisions necessary to permit development to begin. In particular, specs require you to confirm that you've already discussed the issue/idea with the team in an issue and that you provide the issue ID for reference.
+
+Team members will be happy to help review specs and guide them to completion.
+
+### Help Wanted
+
+Once the team have approved an issue/spec, development can proceed. If no developers are immediately available, the spec can be parked ready for a developer to get started. Parked specs' issues will be labeled "Help Wanted". To find a list of development opportunities waiting for developer involvement, visit the Issues and filter on [the Help-Wanted label](https://github.com/microsoft/terminal/labels/Help-Wanted).
+
+---
+
+## Development
+
+### Fork, Clone, Branch and Create your PR
+
+Once you've discussed your proposed feature/fix/etc. with a team member, and you've agreed an approach or a spec has been written and approved, it's time to start development:
+
+1. Fork the repo if you haven't already
+1. Clone your fork locally
+1. Create & push a feature branch
+1. Create a [Draft Pull Request (PR)](https://github.blog/2019-02-14-introducing-draft-pull-requests/)
+1. Work on your changes
+
+### Code Review
+
+When you'd like the team to take a look, (even if the work is not yet fully-complete), mark the PR as 'Ready For Review' so that the team can review your work and provide comments, suggestions, and request changes. It may take several cycles, but the end result will be solid, testable, conformant code that is safe for us to merge.
+
+> ⚠ Remember: **changes you make may affect both Windows Terminal and Windows Console and may end up being re-incorporated into Windows itself!** Because of this, we will treat community PR's with the same level of scrutiny and rigor as commits submitted to the official Windows source by team members and partners.
+
+### Merge
+
+Once your code has been reviewed and approved by the requisite number of team members, it will be merged into the master branch. Once merged, your PR will be automatically closed.
+
+---
+
+## Thank you
+
+Thank you in advance for your contribution! Now, [what's next on the list](https://github.com/microsoft/terminal/labels/Help-Wanted)? 😜

doc/reference/UTF8-torture-test.txt

@@ -0,0 +1,212 @@
+
+UTF-8 encoded sample plain-text file
+‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾
+
+Markus Kuhn [ˈmaʳkʊs kuːn] <http://www.cl.cam.ac.uk/~mgk25/> — 2002-07-25
+
+
+The ASCII compatible UTF-8 encoding used in this plain-text file
+is defined in Unicode, ISO 10646-1, and RFC 2279.
+
+
+Using Unicode/UTF-8, you can write in emails and source code things such as
+
+Mathematics and sciences:
+
+  ∮ E⋅da = Q,  n → ∞, ∑ f(i) = ∏ g(i),      ⎧⎡⎛┌─────┐⎞⎤⎫
+                                            ⎪⎢⎜│a²+b³ ⎟⎥⎪
+  ∀x∈ℝ: ⌈x⌉ = −⌊−x⌋, α ∧ ¬β = ¬(¬α ∨ β),    ⎪⎢⎜│───── ⎟⎥⎪
+                                            ⎪⎢⎜⎷ c₈   ⎟⎥⎪
+  ℕ ⊆ ℕ₀ ⊂ ℤ ⊂ ℚ ⊂ ℝ ⊂ ℂ,                   ⎨⎢⎜       ⎟⎥⎬
+                                            ⎪⎢⎜ ∞     ⎟⎥⎪
+  ⊥ < a ≠ b ≡ c ≤ d ≪ ⊤ ⇒ (⟦A⟧ ⇔ ⟪B⟫),      ⎪⎢⎜ ⎲     ⎟⎥⎪
+                                            ⎪⎢⎜ ⎳aⁱ-bⁱ⎟⎥⎪
+  2H₂ + O₂ ⇌ 2H₂O, R = 4.7 kΩ, ⌀ 200 mm     ⎩⎣⎝i=1    ⎠⎦⎭
+
+Linguistics and dictionaries:
+
+  ði ıntəˈnæʃənəl fəˈnɛtık əsoʊsiˈeıʃn
+  Y [ˈʏpsilɔn], Yen [jɛn], Yoga [ˈjoːgɑ]
+
+APL:
+
+  ((V⍳V)=⍳⍴V)/V←,V    ⌷←⍳→⍴∆∇⊃‾⍎⍕⌈
+
+Nicer typography in plain text files:
+
+  ╔══════════════════════════════════════════╗
+  ║                                          ║
+  ║   • ‘single’ and “double” quotes         ║
+  ║                                          ║
+  ║   • Curly apostrophes: “We’ve been here” ║
+  ║                                          ║
+  ║   • Latin-1 apostrophe and accents: '´`  ║
+  ║                                          ║
+  ║   • ‚deutsche‘ „Anführungszeichen“       ║
+  ║                                          ║
+  ║   • †, ‡, ‰, •, 3–4, —, −5/+5, ™, …      ║
+  ║                                          ║
+  ║   • ASCII safety test: 1lI|, 0OD, 8B     ║
+  ║                      ╭─────────╮         ║
+  ║   • the euro symbol: │ 14.95 € │         ║
+  ║                      ╰─────────╯         ║
+  ╚══════════════════════════════════════════╝
+
+Combining characters:
+
+  STARGΛ̊TE SG-1, a = v̇ = r̈, a⃑ ⊥ b⃑
+
+Greek (in Polytonic):
+
+  The Greek anthem:
+
+  Σὲ γνωρίζω ἀπὸ τὴν κόψη
+  τοῦ σπαθιοῦ τὴν τρομερή,
+  σὲ γνωρίζω ἀπὸ τὴν ὄψη
+  ποὺ μὲ βία μετράει τὴ γῆ.
+
+  ᾿Απ᾿ τὰ κόκκαλα βγαλμένη
+  τῶν ῾Ελλήνων τὰ ἱερά
+  καὶ σὰν πρῶτα ἀνδρειωμένη
+  χαῖρε, ὦ χαῖρε, ᾿Ελευθεριά!
+
+  From a speech of Demosthenes in the 4th century BC:
+
+  Οὐχὶ ταὐτὰ παρίσταταί μοι γιγνώσκειν, ὦ ἄνδρες ᾿Αθηναῖοι,
+  ὅταν τ᾿ εἰς τὰ πράγματα ἀποβλέψω καὶ ὅταν πρὸς τοὺς
+  λόγους οὓς ἀκούω· τοὺς μὲν γὰρ λόγους περὶ τοῦ
+  τιμωρήσασθαι Φίλιππον ὁρῶ γιγνομένους, τὰ δὲ πράγματ᾿
+  εἰς τοῦτο προήκοντα,  ὥσθ᾿ ὅπως μὴ πεισόμεθ᾿ αὐτοὶ
+  πρότερον κακῶς σκέψασθαι δέον. οὐδέν οὖν ἄλλο μοι δοκοῦσιν
+  οἱ τὰ τοιαῦτα λέγοντες ἢ τὴν ὑπόθεσιν, περὶ ἧς βουλεύεσθαι,
+  οὐχὶ τὴν οὖσαν παριστάντες ὑμῖν ἁμαρτάνειν. ἐγὼ δέ, ὅτι μέν
+  ποτ᾿ ἐξῆν τῇ πόλει καὶ τὰ αὑτῆς ἔχειν ἀσφαλῶς καὶ Φίλιππον
+  τιμωρήσασθαι, καὶ μάλ᾿ ἀκριβῶς οἶδα· ἐπ᾿ ἐμοῦ γάρ, οὐ πάλαι
+  γέγονεν ταῦτ᾿ ἀμφότερα· νῦν μέντοι πέπεισμαι τοῦθ᾿ ἱκανὸν
+  προλαβεῖν ἡμῖν εἶναι τὴν πρώτην, ὅπως τοὺς συμμάχους
+  σώσομεν. ἐὰν γὰρ τοῦτο βεβαίως ὑπάρξῃ, τότε καὶ περὶ τοῦ
+  τίνα τιμωρήσεταί τις καὶ ὃν τρόπον ἐξέσται σκοπεῖν· πρὶν δὲ
+  τὴν ἀρχὴν ὀρθῶς ὑποθέσθαι, μάταιον ἡγοῦμαι περὶ τῆς
+  τελευτῆς ὁντινοῦν ποιεῖσθαι λόγον.
+
+  Δημοσθένους, Γ´ ᾿Ολυνθιακὸς
+
+Georgian:
+
+  From a Unicode conference invitation:
+
+  გთხოვთ ახლავე გაიაროთ რეგისტრაცია Unicode-ის მეათე საერთაშორისო
+  კონფერენციაზე დასასწრებად, რომელიც გაიმართება 10-12 მარტს,
+  ქ. მაინცში, გერმანიაში. კონფერენცია შეჰკრებს ერთად მსოფლიოს
+  ექსპერტებს ისეთ დარგებში როგორიცაა ინტერნეტი და Unicode-ი,
+  ინტერნაციონალიზაცია და ლოკალიზაცია, Unicode-ის გამოყენება
+  ოპერაციულ სისტემებსა, და გამოყენებით პროგრამებში, შრიფტებში,
+  ტექსტების დამუშავებასა და მრავალენოვან კომპიუტერულ სისტემებში.
+
+Russian:
+
+  From a Unicode conference invitation:
+
+  Зарегистрируйтесь сейчас на Десятую Международную Конференцию по
+  Unicode, которая состоится 10-12 марта 1997 года в Майнце в Германии.
+  Конференция соберет широкий круг экспертов по  вопросам глобального
+  Интернета и Unicode, локализации и интернационализации, воплощению и
+  применению Unicode в различных операционных системах и программных
+  приложениях, шрифтах, верстке и многоязычных компьютерных системах.
+
+Thai (UCS Level 2):
+
+  Excerpt from a poetry on The Romance of The Three Kingdoms (a Chinese
+  classic 'San Gua'):
+
+  [----------------------------|------------------------]
+    ๏ แผ่นดินฮั่นเสื่อมโทรมแสนสังเวช  พระปกเกศกองบู๊กู้ขึ้นใหม่
+  สิบสองกษัตริย์ก่อนหน้าแลถัดไป       สององค์ไซร้โง่เขลาเบาปัญญา
+    ทรงนับถือขันทีเป็นที่พึ่ง           บ้านเมืองจึงวิปริตเป็นนักหนา
+  โฮจิ๋นเรียกทัพทั่วหัวเมืองมา         หมายจะฆ่ามดชั่วตัวสำคัญ
+    เหมือนขับไสไล่เสือจากเคหา      รับหมาป่าเข้ามาเลยอาสัญ
+  ฝ่ายอ้องอุ้นยุแยกให้แตกกัน          ใช้สาวนั้นเป็นชนวนชื่นชวนใจ
+    พลันลิฉุยกุยกีกลับก่อเหตุ          ช่างอาเพศจริงหนาฟ้าร้องไห้
+  ต้องรบราฆ่าฟันจนบรรลัย           ฤๅหาใครค้ำชูกู้บรรลังก์ ฯ
+
+  (The above is a two-column text. If combining characters are handled
+  correctly, the lines of the second column should be aligned with the
+  | character above.)
+
+Ethiopian:
+
+  Proverbs in the Amharic language:
+
+  ሰማይ አይታረስ ንጉሥ አይከሰስ።
+  ብላ ካለኝ እንደአባቴ በቆመጠኝ።
+  ጌጥ ያለቤቱ ቁምጥና ነው።
+  ደሀ በሕልሙ ቅቤ ባይጠጣ ንጣት በገደለው።
+  የአፍ ወለምታ በቅቤ አይታሽም።
+  አይጥ በበላ ዳዋ ተመታ።
+  ሲተረጉሙ ይደረግሙ።
+  ቀስ በቀስ፥ ዕንቁላል በእግሩ ይሄዳል።
+  ድር ቢያብር አንበሳ ያስር።
+  ሰው እንደቤቱ እንጅ እንደ ጉረቤቱ አይተዳደርም።
+  እግዜር የከፈተውን ጉሮሮ ሳይዘጋው አይድርም።
+  የጎረቤት ሌባ፥ ቢያዩት ይስቅ ባያዩት ያጠልቅ።
+  ሥራ ከመፍታት ልጄን ላፋታት።
+  ዓባይ ማደሪያ የለው፥ ግንድ ይዞ ይዞራል።
+  የእስላም አገሩ መካ የአሞራ አገሩ ዋርካ።
+  ተንጋሎ ቢተፉ ተመልሶ ባፉ።
+  ወዳጅህ ማር ቢሆን ጨርስህ አትላሰው።
+  እግርህን በፍራሽህ ልክ ዘርጋ።
+
+Runes:
+
+  ᚻᛖ ᚳᚹᚫᚦ ᚦᚫᛏ ᚻᛖ ᛒᚢᛞᛖ ᚩᚾ ᚦᚫᛗ ᛚᚪᚾᛞᛖ ᚾᚩᚱᚦᚹᛖᚪᚱᛞᚢᛗ ᚹᛁᚦ ᚦᚪ ᚹᛖᛥᚫ
+
+  (Old English, which transcribed into Latin reads 'He cwaeth that he
+  bude thaem lande northweardum with tha Westsae.' and means 'He said
+  that he lived in the northern land near the Western Sea.')
+
+Braille:
+
+  ⡌⠁⠧⠑ ⠼⠁⠒  ⡍⠜⠇⠑⠹⠰⠎ ⡣⠕⠌
+
+  ⡍⠜⠇⠑⠹ ⠺⠁⠎ ⠙⠑⠁⠙⠒ ⠞⠕ ⠃⠑⠛⠔ ⠺⠊⠹⠲ ⡹⠻⠑ ⠊⠎ ⠝⠕ ⠙⠳⠃⠞
+  ⠱⠁⠞⠑⠧⠻ ⠁⠃⠳⠞ ⠹⠁⠞⠲ ⡹⠑ ⠗⠑⠛⠊⠌⠻ ⠕⠋ ⠙⠊⠎ ⠃⠥⠗⠊⠁⠇ ⠺⠁⠎
+  ⠎⠊⠛⠝⠫ ⠃⠹ ⠹⠑ ⠊⠇⠻⠛⠹⠍⠁⠝⠂ ⠹⠑ ⠊⠇⠻⠅⠂ ⠹⠑ ⠥⠝⠙⠻⠞⠁⠅⠻⠂
+  ⠁⠝⠙ ⠹⠑ ⠡⠊⠑⠋ ⠍⠳⠗⠝⠻⠲ ⡎⠊⠗⠕⠕⠛⠑ ⠎⠊⠛⠝⠫ ⠊⠞⠲ ⡁⠝⠙
+  ⡎⠊⠗⠕⠕⠛⠑⠰⠎ ⠝⠁⠍⠑ ⠺⠁⠎ ⠛⠕⠕⠙ ⠥⠏⠕⠝ ⠰⡡⠁⠝⠛⠑⠂ ⠋⠕⠗ ⠁⠝⠹⠹⠔⠛ ⠙⠑
+  ⠡⠕⠎⠑ ⠞⠕ ⠏⠥⠞ ⠙⠊⠎ ⠙⠁⠝⠙ ⠞⠕⠲
+
+  ⡕⠇⠙ ⡍⠜⠇⠑⠹ ⠺⠁⠎ ⠁⠎ ⠙⠑⠁⠙ ⠁⠎ ⠁ ⠙⠕⠕⠗⠤⠝⠁⠊⠇⠲
+
+  ⡍⠔⠙⠖ ⡊ ⠙⠕⠝⠰⠞ ⠍⠑⠁⠝ ⠞⠕ ⠎⠁⠹ ⠹⠁⠞ ⡊ ⠅⠝⠪⠂ ⠕⠋ ⠍⠹
+  ⠪⠝ ⠅⠝⠪⠇⠫⠛⠑⠂ ⠱⠁⠞ ⠹⠻⠑ ⠊⠎ ⠏⠜⠞⠊⠊⠥⠇⠜⠇⠹ ⠙⠑⠁⠙ ⠁⠃⠳⠞
+  ⠁ ⠙⠕⠕⠗⠤⠝⠁⠊⠇⠲ ⡊ ⠍⠊⠣⠞ ⠙⠁⠧⠑ ⠃⠑⠲ ⠔⠊⠇⠔⠫⠂ ⠍⠹⠎⠑⠇⠋⠂ ⠞⠕
+  ⠗⠑⠛⠜⠙ ⠁ ⠊⠕⠋⠋⠔⠤⠝⠁⠊⠇ ⠁⠎ ⠹⠑ ⠙⠑⠁⠙⠑⠌ ⠏⠊⠑⠊⠑ ⠕⠋ ⠊⠗⠕⠝⠍⠕⠝⠛⠻⠹
+  ⠔ ⠹⠑ ⠞⠗⠁⠙⠑⠲ ⡃⠥⠞ ⠹⠑ ⠺⠊⠎⠙⠕⠍ ⠕⠋ ⠳⠗ ⠁⠝⠊⠑⠌⠕⠗⠎
+  ⠊⠎ ⠔ ⠹⠑ ⠎⠊⠍⠊⠇⠑⠆ ⠁⠝⠙ ⠍⠹ ⠥⠝⠙⠁⠇⠇⠪⠫ ⠙⠁⠝⠙⠎
+  ⠩⠁⠇⠇ ⠝⠕⠞ ⠙⠊⠌⠥⠗⠃ ⠊⠞⠂ ⠕⠗ ⠹⠑ ⡊⠳⠝⠞⠗⠹⠰⠎ ⠙⠕⠝⠑ ⠋⠕⠗⠲ ⡹⠳
+  ⠺⠊⠇⠇ ⠹⠻⠑⠋⠕⠗⠑ ⠏⠻⠍⠊⠞ ⠍⠑ ⠞⠕ ⠗⠑⠏⠑⠁⠞⠂ ⠑⠍⠏⠙⠁⠞⠊⠊⠁⠇⠇⠹⠂ ⠹⠁⠞
+  ⡍⠜⠇⠑⠹ ⠺⠁⠎ ⠁⠎ ⠙⠑⠁⠙ ⠁⠎ ⠁ ⠙⠕⠕⠗⠤⠝⠁⠊⠇⠲
+
+  (The first couple of paragraphs of "A Christmas Carol" by Dickens)
+
+Compact font selection example text:
+
+  ABCDEFGHIJKLMNOPQRSTUVWXYZ /0123456789
+  abcdefghijklmnopqrstuvwxyz £©µÀÆÖÞßéöÿ
+  –—‘“”„†•…‰™œŠŸž€ ΑΒΓΔΩαβγδω АБВГДабвгд
+  ∀∂∈ℝ∧∪≡∞ ↑↗↨↻⇣ ┐┼╔╘░►☺♀ fi<>⑀₂ἠḂӥẄɐː⍎אԱა
+
+Greetings in various languages:
+
+  Hello world, Καλημέρα κόσμε, コンニチハ
+
+Box drawing alignment tests:                                          █
+                                                                      ▉
+  ╔══╦══╗  ┌──┬──┐  ╭──┬──╮  ╭──┬──╮  ┏━━┳━━┓  ┎┒┏┑   ╷  ╻ ┏┯┓ ┌┰┐    ▊ ╱╲╱╲╳╳╳
+  ║┌─╨─┐║  │╔═╧═╗│  │╒═╪═╕│  │╓─╁─╖│  ┃┌─╂─┐┃  ┗╃╄┙  ╶┼╴╺╋╸┠┼┨ ┝╋┥    ▋ ╲╱╲╱╳╳╳
+  ║│╲ ╱│║  │║   ║│  ││ │ ││  │║ ┃ ║│  ┃│ ╿ │┃  ┍╅╆┓   ╵  ╹ ┗┷┛ └┸┘    ▌ ╱╲╱╲╳╳╳
+  ╠╡ ╳ ╞╣  ├╢   ╟┤  ├┼─┼─┼┤  ├╫─╂─╫┤  ┣┿╾┼╼┿┫  ┕┛┖┚     ┌┄┄┐ ╎ ┏┅┅┓ ┋ ▍ ╲╱╲╱╳╳╳
+  ║│╱ ╲│║  │║   ║│  ││ │ ││  │║ ┃ ║│  ┃│ ╽ │┃  ░░▒▒▓▓██ ┊  ┆ ╎ ╏  ┇ ┋ ▎
+  ║└─╥─┘║  │╚═╤═╝│  │╘═╪═╛│  │╙─╀─╜│  ┃└─╂─┘┃  ░░▒▒▓▓██ ┊  ┆ ╎ ╏  ┇ ┋ ▏
+  ╚══╩══╝  └──┴──┘  ╰──┴──╯  ╰──┴──╯  ┗━━┻━━┛  ▗▄▖▛▀▜   └╌╌┘ ╎ ┗╍╍┛ ┋  ▁▂▃▄▅▆▇█
+                                               ▝▀▘▙▄▟

doc/specs/#1235 - Azure cloud shell connector/spec.md

@@ -0,0 +1,78 @@
+---
+author: Pankaj Bhojwani pankaj.d.bhoj@gmail.com
+created on: 2019-06-12
+last updated: 2019-06-12
+issue id: #1235
+---
+
+# Azure cloud shell connector
+
+## Abstract
+
+This spec goes over the details of how a feature enabling Windows Terminal users to connect to the Azure cloud shell should behave. It includes implementation and design considerations. 
+
+## Inspiration
+
+The idea is to give developers access to their Azure services smoothly within the Windows Terminal app, letting them engage with Azure technologies in a convenient manner. By integrating the Azure cloud shell into Windows Terminal, we can do just that. 
+
+## Solution Design
+
+The flowchart below shows the process by which the Azure cloud shell will be integrated into Windows Terminal. 
+
+![Sol Design](images/solDesign.png)
+
+The first three steps - authenticating the user, requesting a cloud shell and requesting a terminal - will be done via http requests. These requests will use the [cpprestsdk](https://github.com/Microsoft/cpprestsdk) library as that library is also owned by Microsoft, making it easy to resolve issues should any arise. 
+
+Authenticating the user will use [device code flow](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/Device-Code-Flow) since Windows Terminal does not support browser access (yet). As for the authentication endpoint, Azure AD v1.0 will be used because Azure AD v2.0 (also known as Microsoft Identity Platform) [does not support login to personal accounts with device code flow](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/Device-Code-Flow#constraints) at this time. Furthermore, upon successful authentication, the login/token information will be stored so that users will not need to repeatedly go through device code flow for future logins. Since this is sensitive information, the tokens will be stored with [Windows Storage](https://docs.microsoft.com/en-us/uwp/api/windows.storage) and encrypted with [Windows Security Data Protection](https://docs.microsoft.com/en-us/uwp/api/windows.security.cryptography.dataprotection.dataprotectionprovider). 
+
+The last step - connecting to the terminal - will be done via a websocket connection to allow easier communication between the app and the server. 
+
+The entire feature will be implemented in an isolated manner - i.e. it should have little to no dependency on the Windows Terminal app itself. This will allow the feature to become a plugin/extension once Windows Terminal supports plugins. More specifically, the connector will ascribe to the existing ITerminalConnection interface, making this simply another type of connection that Windows Terminal can make. 
+
+## UI/UX Design
+
+Upon successful implementation, a new profile option will appear for users as illustrated in the picture below (the profile will have its own unique icon when implemented).
+
+![Az Prof](images/azProf.png)
+
+As for the rest of the UI, the implementation will adopt the user's preferences from the Windows Terminal app. 
+
+## Capabilities
+
+### Accessibility
+
+This feature will not impact accessibility of Windows Terminal. 
+
+### Security
+
+Any feature that connects to a network introduces some security risks. However, with proper usage of Azure AD v1.0 and careful storage of tokens received from the server, these risks will be mitigated. 
+
+### Reliability
+
+This feature will not impact reliability of Windows Terminal. 
+
+### Compatibility
+
+With the implementation being mostly decoupled from the Windows Terminal app itself, no existing code/behaviours should break due to this feature. 
+
+### Performance, Power, and Efficiency
+
+This feature will not impact performance, power or efficiency of Windows Terminal.
+
+## Potential Issues
+
+1. This implementation depends on another open source project, [cpprestsdk](https://github.com/Microsoft/cpprestsdk). Thus, any issues with their code will affect this feature. However, given that cpprestsdk is a Microsoft project, we can expect a level of reliability and also solve issues internally if needed.
+2. The proposed authentication endpoint is Azure AD v1.0 instead of Azure AD v2.0 (also known as Microsoft Identity Platform). Azure AD v1.0 is still supported for now, but there is a risk of it becoming deprecated at some point in the future. However, given that it is once again another Microsoft-owned project, we can request support for it through an internal channel. In the worst case, our implementation can switch to Microsoft Identity Platform (which would only requires some minor edits to the http requests). 
+3. The Azure cloud shell API is not public, meaning that implementing this feature in an official capacity would require app permissions from the Azure cloud shell team. This brings about another dependency, but once again issues can be resolved through internal Microsoft channels. 
+
+## Future considerations
+
+This could potentially be the first plugin for Windows Terminal once the app allows for plugins/extensions! 
+
+## Resources
+
+* [Azure AD v1.0](https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-overview)
+* [cpprestsdk](https://github.com/Microsoft/cpprestsdk)
+* [Device code flow](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/Device-Code-Flow)
+* [Windows Storage](https://docs.microsoft.com/en-us/uwp/api/windows.storage)
+* [Windows Security Data Protection](https://docs.microsoft.com/en-us/uwp/api/windows.security.cryptography.dataprotection.dataprotectionprovider)

doc/specs/spec-template.md

@@ -0,0 +1,58 @@
+---
+author: <first-name> <last-name> <github-id>/<email>
+created on: <yyyy-mm-dd>
+last updated: <yyyy-mm-dd>
+issue id: <github issue id>
+---
+
+# Spec Title
+
+## Abstract
+
+[comment]: # Outline what this spec describes
+
+## Inspiration
+
+[comment]: # What were the drivers/inspiration behind the creation of this spec.
+
+## Solution Design
+
+[comment]: # Outline the design of the solution. Feel free to include ASCII-art diagrams, etc.
+
+## UI/UX Design
+
+[comment]: # What will this fix/feature look like? How will it affect the end user?
+
+## Capabilities
+
+[comment]: # Discuss how the proposed fixes/features impact the following key considerations:
+
+### Accessibility
+
+[comment]: # How will the proposed change impact accessibility for users of screen readers, assistive input devices, etc.
+
+### Security
+
+[comment]: # How will the proposed change impact security?
+
+### Reliability
+
+[comment]: # Will the proposed change improve reliabilty? If not, why make the change?
+
+### Compatibility
+
+[comment]: # Will the proposed change break existing code/behaviors? If so, how, and is the breaking change "worth it"?
+
+### Performance, Power, and Efficiency
+
+## Potential Issues
+
+[comment]: # What are some of the things that might cause problems with the fixes/features proposed? Consider how the user might be negatively impacted.
+
+## Future considerations
+
+[comment]: # What are some of the things that the fixes/features might unlock in the future? Does the implementation of this spec enable scenarios?
+
+## Resources
+
+[comment]: # Be sure to add links to references, resources, footnotes, etc.

doc/submitting_code.md

@@ -0,0 +1,26 @@
+
+# Branches in Openconsole
+
+In Openconsole, `dev/main` is the master branch for the repo.
+
+Any branch that begins with `dev/` is recognized by our CI system and will automatically run x86 and amd64 builds and run our unit and feature tests. For feature branchs the pattern we use is `dev/<alias>/<whatever you want here>`. ex. `dev/austdi/SomeCoolUnicodeFeature`. The important parts are the dev prefix and your alias.
+
+`inbox` is a special branch that coordinates Openconsole code to the main OS repo.
+
+The code will be checked into the OS repo at `/onecore/windows/core/console/open`. It would be prudent to make sure that directory builds in razzle with your submitted changes.
+
+# Code Submission Process
+
+Because we build outside of the OS repo, we need a way to get code back into it once it's been merged into `dev/main`. This is done by cherry-picking the PR to the `inbox` branch once it has been merged (and preferably squashed) into `dev/main`. We have a tool called Git2Git that listens for new merges into `inbox` and replicates the commits over to the OS repo. Feel free to approve and complete the `inbox` PR yourself. About a minute after the `inbox` PR is submitted, Git2Git will create a PR in the OS repo under the alias `miniksa`. It will automatically target the OS branch we're using at the time, it just needs you to go approve and complete it. Once that merge is completed it is a good idea to build the OS branch with the new code in it to make sure that the PR won't be the cause of a build break that evening.
+
+## What to do when cherry-picking to inbox fails
+
+Sometimes VSTS doesn't want to allow a cherry pick to the inbox branch. It might have a valid reason or it might just be finicky. You'll need to complete the merge manually on a local machine. The steps are:
+
+1. make sure you have pulled the latest commits for the `dev/main` and `inbox` branches
+2. make a new branch from inbox
+3. cherry-pick the commits from the PR to the newly created branch (this is easier if you squashed your commits when you merged into `dev/main`
+4. fix any merge conficts and commit
+5. push the new branch to the remote
+6. create a new PR of that branch in `inbox`
+7. complete PR and continue on to completing the auto-created PR in the OS repo

doc/user-docs/UsingJsonSettings.md

@@ -0,0 +1,128 @@
+# Editing Windows Terminal JSON Settings
+
+One way (currently the only way) to configure Windows Terminal is by editing the profiles.json settings file. At
+the time of writing you can open the settings file in your default editor by selecting
+`Settings` from the WT pull down menu.
+
+The settings are stored in the file `$env:LocalAppData\Packages\Microsoft.WindowsTerminal_<randomString>\RoamingState\profiles.json` 
+
+Details of specific settings can be found [here](../cascadia/SettingsSchema.md). A general introduction is provided below.
+
+The settings are grouped under four headings:
+
+1. Global: Settings that apply to the whole application e.g. Default profile, initial size etc.
+2. Key Bindings: Actually a sub field of the global settings, but worth discussing separately
+3. Profiles: A group of settings to be applied to a tab when it is opened using that profile. E.g. shell to use, cursor shape etc.
+4. Schemes: Sets of colors for background, text etc. that can be used by profiles
+
+## Global Settings
+
+These settings define startup defaults.
+
+* Theme
+* Title Bar options
+* Initial size
+* Default profile used when WT is started
+
+Example settings include
+
+```json
+    "defaultProfile" : "{58ad8b0c-3ef8-5f4d-bc6f-13e4c00f2530}",
+    "initialCols" : 120,
+    "initialRows" : 50,
+    "requestedTheme" : "system",
+    "keybinding" : []
+    ...
+```
+
+## Key Bindings
+
+This is an array of key chords and shortcuts to invoke various commands.
+Each command can have more than one key binding.
+
+NOTE: Key bindings is a subfield of the global settings and
+key bindings apply to all profiles in the same manner.
+
+## Profiles
+
+A profile contains the settings applied when a new WT tab is opened. Each profile is identified by a GUID and contains
+a number of other fields.
+
+* Which command to execute on startup - this can include arguments.
+* Starting directory
+* Which color scheme to use (see Schemes below)
+* Font face and size
+* Various settings to control appearance. E.g. Opacity, icon, cursor appearance, display name etc.
+* Other behavioural settings. E.g. Close on exit, snap on input, .....
+
+Example settings include
+
+```json
+    "closeOnExit" : true,
+    "colorScheme" : "Campbell",
+    "commandline" : "wsl.exe -d Debian",
+    "cursorColor" : "#FFFFFF",
+    "cursorShape" : "bar",
+    "fontFace" : "Hack",
+    "fontSize" : 9,
+    "guid" : "{58ad8b0c-3ef8-5f4d-bc6f-13e4c00f2530}",
+    "name" : "Debian",
+    "startingDirectory" : "%USERPROFILE%/wslhome"
+    ....
+```
+
+The profile GUID is used to reference the default profile in the global settings.
+
+The values for background image stretch mode are documented [here](https://docs.microsoft.com/en-us/uwp/api/windows.ui.xaml.media.stretch)
+
+##  Color Schemes
+
+Each scheme defines the color values to be used for various terminal escape sequences.
+Each schema is identified by the name field. Examples include
+
+```json
+    "name" : "Campbell",
+    "background" : "#0C0C0C",
+    "black" : "#0C0C0C",
+    "blue" : "#0037DA",
+    "foreground" : "#F2F2F2",
+    "green" : "#13A10E",
+    "red" : "#C50F1F",
+    "white" : "#CCCCCC",
+    "yellow" : "#C19C00"
+    ...
+```
+
+The schema name can then be referenced in one or more profiles.
+
+## Configuration Examples:
+
+### Add a custom background to the WSL Debian terminal profile
+
+1. Download the Debian SVG logo https://www.debian.org/logos/openlogo.svg
+2. Put the image in the
+ `$env:LocalAppData\Packages\Microsoft.WindowsTerminal_<randomString>\RoamingState\`
+ directory (same directory as your `profiles.json` file).
+
+    __NOTE__:  You can put the image anywhere you like, the above suggestion happens to be convenient.
+3. Open your WT json properties file.
+4. Under the Debian Linux profile, add the following fields:
+```json
+    "backgroundImage": "ms-appdata:///Roaming/openlogo.jpg",
+    "backgroundImageOpacity": 0.3,
+    "backgroundImageStretchMode":  "Fill",
+```
+5. Make sure that `useAcrylic` is `false`.
+6. Save the file.
+7. Jump over to WT and verify your changes.
+
+Notes:
+1. You will need to experiment with different color settings
+and schemes to make your terminal text visible on top of your image
+2. If you store the image in the UWP directory (the same directory as your profiles.json file),
+then you should use the URI style path name given in the above example.
+More information about UWP URI schemes [here](https://docs.microsoft.com/en-us/windows/uwp/app-resources/uri-schemes).
+3. Instead of using a UWP URI you can use a:
+    1. URL such as
+`http://open.esa.int/files/2017/03/Mayer_and_Bond_craters_seen_by_SMART-1-350x346.jpg` 
+    2. Local file location such as `C:\Users\Public\Pictures\openlogo.jpg`

doc/user-docs/index.md

@@ -0,0 +1,90 @@
+# Windows Terminal User Documentation
+
+NOTE: At the time of writing Windows Terminal is still under active development and many things will
+change. If you notice an error in the docs, please raise an issue. Or better yet, please file a PR with an appropriate update!
+
+## Installing Windows Terminal 
+
+### From Source Code
+
+Follow the instructions in this repo's [README](/README.md#developer-guidance).
+
+### From the Microsoft Store
+
+1. Make sure you have upgraded to the current Windows 10 release (at least 1903)
+2. Search for Windows Terminal in the Store
+3. Review the minimum system settings to ensure you can successfully install Windows Terminal
+4. Install in the normal fashion
+
+## Starting Windows Terminal
+
+From the Windows Start menu, select Windows Terminal and run the application.
+
+Note: You can right click on the application item and run with Windows Administrator privilege if required.
+
+The default shell is PowerShell.
+
+
+### Command line options
+
+None at this time. See issue [#607](https://github.com/microsoft/terminal/issues/607)
+
+## Multiple Tabs
+
+Additional shells can be started by hitting the `+` button from the tab bar -- a new instance of the
+default shell is displayed (default shortcut `Ctrl+Shift+1`).
+
+## Running a Different Shell
+
+Note: The following text assumes you have WSL installed.
+
+To choose a different shell (e.g. `cmd.exe` or WSL `bash`) then
+
+1. Select the `down` button next to the `+` in the tab bar
+2. Choose your new shell from the list (more on how to extend the list in the config section)
+
+## Starting a new PowerShell tab with admin privilege
+
+There is no current plan to support this feature for security reaons. See issue [#623](https://github.com/microsoft/terminal/issues/632)
+
+## Using cut and paste in the Terminal window
+
+### With PowerShell
+
+* Copy - Select the text with mouse (default left button), then right click with mouse
+* Paste - by default use `<ctrl>+v`>, or right click with mouse
+
+### With Bash
+
+* Copy - Select the text with mouse (default left button), then right click with mouse
+* Paste - Right click with mouse
+
+## Add a "Open Windows Terminal Here" to File Explorer
+
+Not currently supported "out of the box". See issue [#1060](https://github.com/microsoft/terminal/issues/1060)
+
+## Configuring Windows Terminal
+
+At the time of writing all Windows Terminal settings are managed via a json file.
+
+From the `down` button in the top bar select Settings (default shortcut `Ctrl+,`).
+
+Your default json editor will open up the Terminal settings file. The file can be found
+at `$env:LocalAppData\Packages\Microsoft.WindowsTerminal_<randomString>/RoamingState`
+
+An introduction to the the various settings can be found [here](UsingJsonSettings.md).
+
+The list of valid settings can be found in the [Profiles.json Documentation](../cascadia/SettingsSchema.md) doc.
+
+## Tips and Tricks:
+
+1. In PowerShell you can discover if the Windows Terminal is being used by checking for the existence of the environment variable `WT_SESSION`.
+
+    Under pwsh you can also use
+`(Get-Process -Id $pid).Parent.Parent.ProcessName -eq 'WindowsTerminal'`
+
+    (ref https://twitter.com/r_keith_hill/status/1142871145852440576)
+
+2. Terminal zoom can be changed by holding `Ctrl` and scrolling with mouse.
+3. If `useAcrylic` is enabled in profiles.json, background opacity can be changed by holding `Ctrl+Shift` and scrolling with mouse.
+4. Please add more Tips and Tricks

doc/virtual-dtors.md

@@ -0,0 +1,35 @@
+# Virtual Destructors for Interfaces
+
+
+* author: Mike Griese __migrie__
+* created on: 2019-Feb-20
+
+As you look through the code, you may come across patterns that look like the following:
+
+``` c++
+
+    class IRenderData
+    {
+    public:
+        virtual ~IRenderData() = 0;
+        // methods
+    };
+
+    inline IRenderData::~IRenderData() {}
+
+```
+
+You may ask yourself, why is the destructor deleted, then later defined to the
+  default destructor? This is a good question, because it seems both unintuitive
+  and unnecessary. However, if you don't define your interfaces exactly like
+  this, then sometimes on object destruction, the interface's dtor will be
+  called instead of the destructor for the base class. There is other
+  strangeness that can occur as well, the details of which escape my memory from
+  when @austdi and I first investigaved this early 2018.
+
+The end result of not defining your interfaces exacly like this will be that
+  occasionally, when destructing objects, you'll get a segfault.
+
+To check that this behavior works, I direct your attention to the VtIoTests.
+  There are a bunch of tests in that module that create objects, then delete
+  them, to make sure that they won't ever crash.

pkg/appx/OpenConsolePackage.wapproj

@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="utf-8"?>
+<Project ToolsVersion="15.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+  <Import Project="..\..\common.openconsole.props" Condition="'$(OpenConsoleDir)'==''" />
+  <Import Project="$(OpenConsoleDir)src\wap-common.build.pre.props" />
+
+  <PropertyGroup Label="Configuration">
+    <TargetPlatformVersion>10.0.17763.0</TargetPlatformVersion>
+    <TargetPlatformMinVersion>10.0.17134.0</TargetPlatformMinVersion>
+    <!--
+    These two properties are very important!
+    Without them, msbuild will stomp MinVersion and MaxVersionTested in the
+    Package.appxmanifest and replace them with whatever our values for
+    TargetPlatformMinVersion and TargetPlatformVersion are.
+     -->
+    <AppxOSMinVersionReplaceManifestVersion>false</AppxOSMinVersionReplaceManifestVersion>
+    <AppxOSMaxVersionTestedReplaceManifestVersion>false</AppxOSMaxVersionTestedReplaceManifestVersion>
+
+    <!-- In a WAP project, this suppresses a spurious dependency on the non-Desktop VCLibs. -->
+    <IncludeGetResolvedSDKReferences>false</IncludeGetResolvedSDKReferences>
+
+    <!-- Suppress the inclusion of Windows.winmd in the appx. -->
+    <SkipUnionWinmd>true</SkipUnionWinmd>
+  </PropertyGroup>
+
+  <PropertyGroup>
+    <ProjectGuid>2D310963-F3E0-4EE5-8AC6-FBC94DCC3310</ProjectGuid>
+
+    <EntryPointExe>OpenConsole.exe</EntryPointExe>
+    <EntryPointProjectUniqueName>..\..\src\host\exe\Host.EXE.vcxproj</EntryPointProjectUniqueName>
+  </PropertyGroup>
+
+  <PropertyGroup>
+    <GenerateAppInstallerFile>False</GenerateAppInstallerFile>
+  </PropertyGroup>
+
+  <PropertyGroup Condition="!Exists('OpenConsolePackage_TemporaryKey.pfx')">
+    <AppxPackageSigningEnabled>false</AppxPackageSigningEnabled>
+    <AppxBundle>Never</AppxBundle>
+  </PropertyGroup>
+
+  <PropertyGroup Condition="Exists('OpenConsolePackage_TemporaryKey.pfx')">
+    <AppxPackageSigningEnabled>true</AppxPackageSigningEnabled>
+    <AppxAutoIncrementPackageRevision>False</AppxAutoIncrementPackageRevision>
+    <PackageCertificateKeyFile>OpenConsolePackage_TemporaryKey.pfx</PackageCertificateKeyFile>
+  </PropertyGroup>
+
+  <ItemGroup Condition="Exists('OpenConsolePackage_TemporaryKey.pfx')">
+    <None Include="OpenConsolePackage_TemporaryKey.pfx" />
+  </ItemGroup>
+
+  <ItemGroup>
+    <AppxManifest Include="Package.appxmanifest">
+      <SubType>Designer</SubType>
+    </AppxManifest>
+  </ItemGroup>
+
+  <ItemGroup>
+    <Content Include="images\LockScreenLogo.scale-200.png" />
+    <Content Include="images\Square150x150Logo.scale-200.png" />
+    <Content Include="images\Square44x44Logo.scale-200.png" />
+    <Content Include="images\Square44x44Logo.targetsize-16_altform-unplated.png" />
+    <Content Include="images\Square44x44Logo.targetsize-24_altform-unplated.png" />
+    <Content Include="images\Square44x44Logo.targetsize-32_altform-unplated.png" />
+    <Content Include="images\Square44x44Logo.targetsize-48_altform-unplated.png" />
+    <Content Include="images\Square44x44Logo.targetsize-256_altform-unplated.png" />
+    <Content Include="images\StoreLogo.png" />
+    <Content Include="images\Wide310x150Logo.scale-200.png" />
+  </ItemGroup>
+
+  <Import Project="$(OpenConsoleDir)src\wap-common.build.post.props" />
+
+  <ItemGroup>
+    <ProjectReference Include="..\..\src\host\exe\Host.EXE.vcxproj" />
+    <ProjectReference Include="..\..\src\propsheet\propsheet.vcxproj" />
+  </ItemGroup>
+
+  <Target Name="OpenConsoleStompSourceProjectForWapProject" BeforeTargets="_ConvertItems">
+    <ItemGroup>
+      <_TemporaryFilteredWapProjOutput Include="@(_FilteredNonWapProjProjectOutput)" />
+      <_FilteredNonWapProjProjectOutput Remove="@(_FilteredNonWapProjProjectOutput)" />
+      <_FilteredNonWapProjProjectOutput Include="@(_TemporaryFilteredWapProjOutput)">
+        <SourceProject></SourceProject> <!-- Blank SourceProject, which WapProj uses to name subdirectories. -->
+      </_FilteredNonWapProjProjectOutput>
+    </ItemGroup>
+  </Target>
+</Project>