It might be my particular configuration, but I seem to be having issues with remoting when using PowershellPlus. I had the issue with version 3.0 which I figured might be fixed in the beta since it is a v2 feature. I don't understand the behavior as in any case it should be a function of powershell not of the particular environment. However it only seems to be an issue in the powershellplus environment. If I run a new subshell it works. As can be seen in the screenshot below the error that I am getting is: The method or operation is not implemented.
It's not your particular configuration. It doesn't work here too (even in the latest private beta release). It looks like interactive remoting (Enter-PSSession and Exit-PSSession) is not implemented yet in PowerShell Plus host.
Do you know why the powershellplus host has to implement specific commands? I would think that everything is passed to the powershell engine...
We already know about this issue with PowerShellPlus. PowerShell v2 implements a new interface that we currently do not support that breaks backward compatibility with PowerShell v1.
Whenever a PowerShell host tries to enter an interactive remote session (as happens when you enter Enter-PSSession), the host looks for a specific interface. If that interface is not there, the host will deny the request, and the user receives a "not supported" exception.In order to support interactive remote sessions, the PSP host has to implement the interface which is not possible when we compile against PS V1 (since this interface was introduced in V2). When we compile against V2, we can easily implement the interface. However, the purpose of this interface is to build a runspace stack. Building this stack is implemented by Microsoft as a private class which we cannot access and reuse. We would therefore have to re-engineer this part ourselves.
So, as you can see, this one is not particularly easy to fix.
@MoMez
You might find this sample that shows how to build a host application that supports calls to remote computers by using the Enter-PsSession and Exit-PsSession cmdlets ( http://msdn.microsoft.com/en-us/library/ee706546(VS.85).aspx ) interesting. And Host06 sample as well.
Thanks to all. Thanks Aleksander, That makes allot of sense, now that I think about it...
I have good news and bad news...
We have code working that will support Interactive Remoting.
The bad news is that this code implements an interface that is only available on PowerShell v2. We currently compile everything on a build machine that has PowerShell v1 in order to provide the best backward compatibility to PowerShell v1 while still supporting PowerShell v2 functionality. However, the interface implementation cannot be wrapped and supporting multiple versions of the same PowerShellPlus release is not something we want to tackle right now.
The plan is to move forward with the current release since there are so many new features and enhancements. We will be making this the last release that supports PowerShell v1. Once we have delivered this release, we will move quickly on to another shorter release cycle that supports interactive remoting but will be dropping PowerShell v1 support going forward at that time.
We are currently tracking to release 3.1 within a month, so anticipate we could have another release out by February or March that would support interactive remoting.
For anyone that may have objections to this, please feel free to drop me some feedback.