History

Leonard Hecker b0396f1741 Make ToolsVersion more consistent in our project files (#13535 ) While working on another PR related to this I noticed that my VS generates `.vcxproj` files that are a bit different to the ones we have. This commit is a quick search & replace of all our project files to make (primarily) their `ToolsVersion` more in line with what VS does itself: No `ToolsVersion` for `.vcxproj`, `ToolsVersion="15.0"` for `.csproj` and `ToolsVersion="4.0"` for `.filters` files.		2022-07-26 22:31:42 +00:00
..
GUIConsole.ConPTY	Remove UTF-8 BOM from all files (#11821 )	2021-11-29 12:54:35 -06:00
GUIConsole.WPF	Make ToolsVersion more consistent in our project files (#13535 )	2022-07-26 22:31:42 +00:00
GUIConsole.sln	Remove UTF-8 BOM from all files (#11821 )	2021-11-29 12:54:35 -06:00
README.md	Add GUIConsole sample (#285 )	2019-05-18 18:17:36 +00:00

README.md

GUIConsole

This is an example of what the skeleton of a custom WPF console might look like.

The GUIConsole.WPF project is a WPF application targeting .NET 4.6.1. It creates a single WPF Window that acts as the console, and keeps the underlying console visible.

The GUIConsole.ConPTY project is a .NET Standard 2.0 library that handles the creation of the console, and enables pseudoconsole behavior. Terminal.cs contains the publicly visible pieces that the WPF application will interact with. Terminal.cs exposes two things that allow reading from, and writing to, the console:

ConsoleOutStream, a FileStream hooked up to the pseudoconsole's output pipe. This will output VT100.
WriteToPseudoConsole(string input), a method that will take the given string and write it to the pseudoconsole via its input pipe. This accepts VT100.