You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Port features from ConsoleHost to Cross-Platform Host #495
We still need to close on whether or not we keep the native host around for PInvoke stuff for FullCLR PowerShell (populating the jumplist, fixing shortcuts, etc.) or rewrite that code to unify to a single managed host. We also use the native host today for hosting different CLRs (i.e. powershell -version 2) and we need to close on whether this is still needed.
The room generally agrees that we should leave the native host be for FullCLR PowerShell until we have more time to mess around with the managed host. No real reason to get rid of the native host today.
Activity
vors commentedon Feb 20, 2016
One of the big 'Usability' annoyance that hopefully would be resolved: Tab-completion drops the end of the line.
Scenario
Write something, i.e.
Now find command in history and try to replace
.by another path and use tab-completion to complete the path.You will find that it drops the rest of the pipeline.
palladia commentedon Feb 21, 2016
Thanks for testing. I've opened PR #569 to address this scenario.
[-]Port Nano powershell managed host to Linux[/-][+]Port features from ConsoleHost to Cross-Platform Host[/+]andyleejordan commentedon Mar 1, 2016
Per last engineering sync, we will be going with our existing cross-platform host, and porting features as we can from the full/core
ConsoleHost.andyleejordan commentedon Mar 28, 2016
The first step for this is to run the
ConsoleHosttests against our host. Until that is done, we won't know what we don't have implemented.andyleejordan commentedon Apr 20, 2016
This is in progress as we get more BVT/DRT tests ported.
joeyaiello commentedon May 5, 2016
We still need to close on whether or not we keep the native host around for PInvoke stuff for FullCLR PowerShell (populating the jumplist, fixing shortcuts, etc.) or rewrite that code to unify to a single managed host. We also use the native host today for hosting different CLRs (i.e. powershell -version 2) and we need to close on whether this is still needed.
The room generally agrees that we should leave the native host be for FullCLR PowerShell until we have more time to mess around with the managed host. No real reason to get rid of the native host today.