Cannot find info on hosting terminal in another app.

[sharpninja]

We need documentation on hosting the console. Project templates would be very helpful.

[DHowett-MSFT]

This is very well-documented on our docs.microsoft.com section

[DHowett-MSFT]

There's also samples in this repository.

[sharpninja]

There are no samples or document for hosting in a UWP process, which has been promised for a long time. Please reopen.

[DHowett-MSFT]

We haven’t promised documentation on that, because hosting an unconstrained application from a UWP context is currently impossible. This is why we didn’t build the terminal as a UWP. That’s just not something the platform supports.

[sharpninja]

This is literally line 4, as a Priority 0 item:

Terminal's core will be hostable as a UWP (and perhaps WPF) Control so that apps can host/embed a high quality Terminal. This will satisfy a long-standing ask from many customers and partners for a hostable/embeddable Terminal Control.

[source](https://github.com/microsoft/terminal/blob/master/doc/terminal-v1-roadmap.md)

…

________________________________ From: Dustin L. Howett (MSFT) <notifications@github.com> Sent: Thursday, February 13, 2020 4:11 PM To: microsoft/terminal <terminal@noreply.github.com> Cc: The Sharp Ninja <ninja@thesharp.ninja>; Author <author@noreply.github.com> Subject: Re: [microsoft/terminal] Cannot find info on hosting terminal in another app. (#4572) We haven’t promised documentation on that, because hosting an unconstrained application from a UWP context is currently impossible. This is why we didn’t build the terminal as a UWP. That’s just not something the platform supports. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#4572?email_source=notifications&email_token=AD3GCLE4BVNKY2PNGGCQBGTRCXARRA5CNFSM4KU25ZHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELWZXCY#issuecomment-585997195>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD3GCLFVVFSAQIK2JFIT23TRCXARRANCNFSM4KU25ZHA>.

[zadjii-msft]

Okay you're not wrong about that. That doc is maybe a little out of date, but I guess we did mention that publicly.

The way the terminal's architecture is designed, it's certainly possible to re-use the terminal control in other UWP projects. However, I think we've let the priority of that particular feature slip a bit as we approach 1.0. AS it currently stands, I don't think that we'll have the cycles to be able to officially support a nuget package or something for the terminal control in the 1.0 timeframe. I think it was more important for us to prepare for allowing arbitrary apps to host the control, and that we've most certainly done.

Thant being said, it'd definitely be possible to unofficially use the TerminalControl.dll and TerminalControl.winmd that's built from this project in other projects. I'm not saying you should do this. I'm saying you could.

@DHowett-MSFT is alluding to the fact that launching other processes from a UWP context is fraught with peril. Those perils is why we've chosen the Win32+Xaml Hosting model for the Terminal. That being said, you could totally add a terminal to a pure UWP application. Just be aware that it's a here be dragons path.

We probably should add documentation on this, but I'm going to toss it on the backlog, since I don't think we'll want to author documentation at this time while things are still changing pretty rapidly.