- Aug
- 2,300
- 111
At present, TCC is using a third-party tool for utilizing PowerShell;
...which is for the (obsolete) PowerShell 5.1;
Is there a path in which TCC will be able to utilize the current PowerShell Core via PSHELL?
Joe
Code:
e:\utils>pshell /s "get-host"
Name : PowerShell SSH Components C++ Edition
Version : 1.0.0.3756
InstanceId : 186cbdb6-f8e9-4331-a018-a8d11f7f6d28
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-CA
CurrentUICulture : en-US
PrivateData :
DebuggerEnabled : True
IsRunspacePushed :
Runspace :
...which is for the (obsolete) PowerShell 5.1;
Code:
PS E:\utils> get-host
Name : ConsoleHost
Version : 5.1.18362.145
InstanceId : 2b03671f-0d7b-49b2-90a0-44a4a2bd3038
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-CA
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspace
Is there a path in which TCC will be able to utilize the current PowerShell Core via PSHELL?
Code:
PS E:\utils> get-host
Name : ConsoleHost
Version : 6.2.1
InstanceId : 208accd2-30ad-4697-a4cb-31011c00f943
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-CA
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspace
Joe