Version 0.1.1.7
1. Recompiled for new Windows PowerShell RC1 (Refresh version)
2. Using "Thread Pooling" method to schedule multiple Host threads. So Sever can potentially
accept more connections. (Old version uses one thread per connection method).
3. Using a separate thread actively reclaim resources from broken connection and dead host.
4. Clean exit when stop service: Disconnect all clients and dispose all running hosts.
5. Gracefully disconnect client when server reach maximum client capacity.
6. Fix: Nested Prompt stack error when multiple clients connected.
7. Fix: Server unable to exit when connection closed unexpectedly by client.
8. Fix: "SetShouldExit" method re-throw "SocketException" Error
Tags: msh monad PowerShell
When I try to run the client, I get this:
ReplyDeletePS D:\WORK\PowerShell\client> .\Start-RemoteHost.ps1 127.0.0.1 8080
Exception calling "LoadFile" with "1" argument(s): "The system cannot find the
file specified. (Exception from HRESULT: 0x80070002)"
At D:\WORK\PowerShell\client\Start-RemoteHost.ps1:4 char:46
+ [void][System.Reflection.Assembly]::LoadFile( <<<< "D:\PowerShellRemoting.Cl
ientPSHost.dll") | out-null
New-Object : Cannot find type [PowerShellRemoting.ClientPSHost]: make sure the
assembly containing this type is loaded.
At D:\WORK\PowerShell\client\Start-RemoteHost.ps1:7 char:30
+ $RemotingClient = new-object <<<< PowerShellRemoting.ClientPSHost($RemoteEP
,$host.ui)
You cannot call a method on a null-valued expression.
At D:\WORK\PowerShell\client\Start-RemoteHost.ps1:8 char:23
+ $RemotingClient.Start( <<<< )
Sorry, for the inconvience.
ReplyDeleteYou are required to make a little change in the start-remotehost.ps1
[void][System.Reflection.Assembly]::LoadFile("D:\PowerShellRemoting.ClientPSHost.dll") | out-null
Where D:\PowerShellRemoting.ClientPSHost.dll is just an example of how to load the assmembly. You will have to change the "full path" to where you acctually saved PowerShellRemoting.ClientPSHost.dll
If it still not work, pls tell me.