15 Maret 2012 20:43
Once I find a script I want to be able to run it right from script explorer UI... with a GUI form to fill in parameters.
This would be similar to how Script Nodes work in PowerGUI... but the problem with PowerGUI script nodes is you have to spend a bunch of clicks and copy/paste time to create them so it winds up being fairly static. If you instead put this kind of UX on script explorer you get the best of both worlds... dynamic discoverability of scripts + easy parameter fill out and running.
I could understand reservations about so easily running discovered scripts which might be poorly written or malicious... but UX friction is not a security boundary so I don't think that is a good reason not to do a feature like this. Executionpolicy would still be in place. Also there could maybe be some scoping specific to ScriptExplorer... like maybe it only runs scripts from a trusted corp reppository.
My experience with helping enterprises to adopt Powershell tells me that most potential users of shared scripts lack the powershell experitise to successfully save a web powershell fragment as a viable script, and then successfully execute that script (figuring out correct syntax to fill in all parameters, etc). I think that the kind of discoverability envisioned by ScriptExplorer coupled with a "Run from here" feature and PowerGUI style parameter completion would make script sharing within an enterprise and among the community much more meaningful.
- Diedit oleh Matthew Reynolds [MSFT] 15 Maret 2012 20:45 typos