Final Std_Out Powershell teaser

[spl]

The attached .wbt script is as simple as it gets to (1) determine PS is installed via Registry query (2) and if installed output available modules in gridview.

And, for the curious, the Powershell Gallery is the main repository of some pretty incredible modules. Put this sample into the previous code I posted to see what can be installed

Code Select Expand

;sample 5
q = '*WMI*'  ; or try '*Excel*'  or '*SQL*'
args = "Find-Module {q} | Select Name, Version, Author, ProjectUri, Description | Out-Gridview -Title 'Searching for {q} Modules' -PassThru"
args = StrReplace(args,'{q}',q)

[td]

I tried the above, but it ran for so long that the OS decided the process had hung. Being an impatient soul, I eventually just killed it.

[spl]

I tried the above, but it ran for so long that the OS decided the process had hung. Being an impatient soul, I eventually just killed it.

I had Jim test it before I uploaded. I have over 300 modules installed, and it took a long time for me to get a GUI gridview. But it was meant to terminate immediately if reg entry was not there. Besides, most of the stuff could just be run from commandline. Sorry, you had an issue --- maybe a problem with Winbatch

[JTaylor]

It took about 10 seconds to display for me but I only had about 75+- modules.

Jim

[spl]

It took about 10 seconds to display for me but I only had about 75+- modules.

Jim

Thanks Jim. I put these STD_Out scripts together in about 90 seconds. This latest one would be for those that didn't play with PS or realize it was even installed --- so I figured they would have minimal modules installed. One can move the BoxShut() in the udf to the end of the main script to keep that window alive, and you can mess with the timeout parameter in the udf. No harm, no foul -- like I wrote 'just trying to keep the conversation lively'