Microsoft Script Explorer for Windows PowerShell (pre-release) helps scripters find Windows PowerShell scripts, snippets, modules, and how-to guidance in online repositories such as the TechNet Script Center Repository, PoshCode, local or network file systems and Bing Search Repository
Microsoft® Script Explorer for Windows PowerShell® (pre-release) helps scripters find Windows PowerShell scripts, snippets, modules, and how-to guidance in online repositories such as the TechNet Script Center Repository, PoshCode, local or network file systems and Bing Search Repository. Microsoft® Script Explorer enables:
- Integrated community and Microsoft resources to help you unlock the power of Windows PowerShell.
- Seamless searching across online repositories to locate script samples relevant to you
- Establishing and searching local, network, and corporate script repository is easy
Supported Operating Systems: Windows 7 Service Pack 1, Windows 8 Consumer Preview, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2, Windows Server 8 Beta, Windows Vista Service Pack 2
- Windows PowerShell 2.0/3.0 ISE (Client computer that is to run Script Explorer as an add-on)
- Microsoft .NET Framework 4
The installer works on both x86 and x64 platforms. It tries to update the All Users Windows PowerShell ISE profile file located at %windir%\system32\WindowsPowerShell\v1.0\ Microsoft.PowerShell_profile.ps1. It updates the profile file for both x86 and x64. Refer to the troubleshooting section in User Guide for information on how to update the profile file manually in case the installer fails to do so because of insufficient permissions. User Guide: http://go.microsoft.com/fwlink/?LinkId=245439 Deployment and Troubleshooting Guide: http://go.microsoft.com/fwlink/?LinkId=245460 Known Limitations:
- During installation, Script Explorer updates the ISE profile file Microsoft.PowerShell_profile.ps1 (All Users profile) located in %windir%\system32\WindowsPowerShell\v1.0\ by adding the following entry %windir%\Script Explorer V1\ScriptExplorer CTP\Microsoft.ScriptExplorer.ps1. If the All Users profile file is already signed, this change invalidates the file signature and the user must resign the profile file. If the Windows PowerShell ExecutionPolicy is set to AllSigned, then user must sign %windir%\Script Explorer V1\ScriptExplorer CTP\Microsoft.ScriptExplorer.ps1 and %windir%\system32\WindowsPowerShell\v1.0\Microsoft.PowerShell_profile.ps1.
- Script Explorer currently handles all signed snippets, scripts and modules as unsigned files. Using Script Explorer application, if a user saves a script, snippet or module to disk from TechNet/PoshCode/Network Location or Local file system, Script Explorer adds custom metadata to the file(s) which invalidates the file signature. The workaround is to resign the file.
- Searching for modules in Local File System displays all .zip file(s) present in the indexed local file system. These .zip files can be module files or any other compressed files. In these sutuations, manual filtering is needed.