Boe Prox

Of course. I'm going to spend a little time this weekend doing some "catch up" to approve PRs and then begin setting up the branches.

I think this last version (1.7.4.2) will be the last version to support V2. I'll split this off onto a V2 branch that will exist just for those who need...

I created a [new branch](https://github.com/proxb/PoshRSJob/tree/PowerShellV2Support) for the V2 side. Next up is to push a new Master branch that only supports V3+.

@AspenForester I can make that update and roll it in with the 1.7.5.0 update. Thanks for pointing that out!

The runspacepools are always running at max capacity unless there are no longer any jobs to process. I'll have to look at the PSJob cmdlet and test what you are...

@MVKozlov Is this one fixed with one of the previous PRs? I'm trying to play cleanup on old issues.

My only concern with this is that by add the current host to the runspacepool creation, all of the streams (Verbose, Debug, etc...) will leak to the current console instead...

This is a tough one because you cannot step into the runspace to supply the credentials needed when the prompt occurs. In fact it throws the error as soon as...

From what I can tell, there isn't a good way to accomplish this other than having a file and forcing the user to manually import the file into the runspace...

@MatthewMWR Thanks for the explanation on this! I already have an update planned to release (1.6.0.0) so this one will be added in the follow on release (1.6.1.0).