Microsoft has been busy with the next iteration of PowerShell. As you should already know, this version will run cross-platform. The executable, or engine, is naturally different than what you are used to with Windows PowerShell. As I was trying out the latest PowerShell beta, I needed to identify the path to the current PowerShell engine. I then thought it might be helpful to get even more details so I put together a quick PowerShell function called Get-PowerShellEngine.<\/p>\n
<\/p>\n
Getting the current PowerShell engine is pretty easy because we can use the built-in $pid variable which references the process ID for the current PowerShell session.<\/p>\n
Get-Process -id $pid | Select -ExpandProperty Path\r\n<\/pre>\nYou can try that out in any PowerShell session and you should get a path like C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe or C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell_ise.exe.\u00a0 But since I always want more, I decided to grab some additional properties from $PSVersionTable and $Host. The complete function is a gist on GitHub<\/a>.<\/p>\n