New powershell Analyzer with Suspendshell and Single Line "Immediate Mode"

As per my blog:

http://www.karlprosser.com/coder/?p=52

Powershell Analyzer New Build - get yours now before your old ones
expires. Version .11 expires on the 15th of Sept so rush now and
download version .13 . This version has a lot of foundational changes
and modifications and has been released to my beta testers for a few
weeks now, with no serious infrastructure bugs reported. If so do find
any bugs, just put them in a comment on this blog. I need to get
bugzilla worked out so we can have some organization going on. So whats
new?


Thank you for your continued usage and support of Powershell Analyzer.
Here is a new build, i have done a lot of work redoing the threading
and really hope that i can get some testing feedback on this one (just
reply to the email with any bugs).

Here is a link to the new build.

http://www.karlprosser.com/vbre232/psanalyzer-13.zip

The main features that have been added are:

1) Support for Suspend (and $host.enternestedprompt ).. When you type
something with -confirm, you can now go into the suspend shell and type
more commands then at your leisure type exit and go back to the choice
that you had. Just like the real powershell.

2) The return of Immediate Mode. Those of you who used my initial MSH
analyzer, you would have noticed the immediate mode where you could
type a one liner and press enter and it would run.. That has returns,
so in this one line type your one liner and press enter and it will
run, also it has build in history, so in the immediate mode textbox
press the Up or down key and cycle through the history of commands,
list like at the command prompt, however the immediate mode also has
Intellisense.

How you can help me.
The first thing is I want to know if it locks up doing anything, and if
it doesn't work
Because of the threading, some of the earlier bugs I had were
1) enter nested prompt not working, not able to exit,
$nestedpromptlevel not reflecting the real level
2) lockups, hangs
3) after going into a nestedprompt, intellisense /variable
hovering etc not working
4) Bad results in the property grid and results explorer (if its
not getting what you think it should ) run the same thing in version
..11 and see if it's the same, if its not please tell me.
5) Try creating multiple runspaces, and doing multiple nested
levels, see if all goes as expected
6) If the LAST command you run happens instead of the current
one, sometimes I had it doing this on say an intellisense . , or a
variable hover

Hopefully the threading model is very stable now, but I appreciate your
feedback

To help debug the levels I often change my prompt with something like
this
function prompt
{
'PS ' + $ ( Get-Location) + $ (if ( $nestedpromptlevel -ge 1) {
'>'+$nestedpromptlevel + '>' }) + '> '
}

So what can you expect next? Well my next release will be with
powershell RC2, and it should have a redesigned and richer GUI, and a
lot of different output visualizations, and in time I will be making a
list of the features I plan to list and let people vote on the order of
how they are implemented.
A little after the RC2 Release a plan to do a Webcast. And I'm starting
postponed work on a portal "PowershellLive.com" I am doing this
together with Tobias Weltner the maker of PowerShellIDE.

-Enjoy - Karl