OneScript Team Blog

A world of automation script samples based on IT Pros' real-world tasks

Releasing Script Browser & Script Analyzer for Windows PowerShell ISE

Releasing Script Browser & Script Analyzer for Windows PowerShell ISE

  • Comments 5
  • Likes

Here we'd like to share a piece of good news with everybody:  today we have a new app released – Script Browser for Windows PowerShell ISE.

Script Browser for Windows PowerShell ISE was designed and developed in response to many IT Pros’ and MVPs’ feedback during the MVP Global Summit.  It puts nearly 10K script examples at IT Pros fingertips when they write scripts to automate their IT tasks. Users can search, learn, download and manage scripts from within their scripting environment - PowerShell ISE - with just a few button clicks.  It saves the time of switching back and forth between webpages and scripting environment, and also the trouble of countless download, copy, and paste operations.  Bundled with Script Browser is another neat feature called ‘Script Analyzer’ that automatically analyzes user’s script against 7 PowerShell best practices, and suggests improvements. Click here to get it now and share the announcements from the Windows PowerShell product team with your IT friends to make their work easier.

Getting started with Script Browser 1.0


It is very essential that an app satisfies users’ requirements. Therefore, feedback is of prime importance. For Script Browser, MVPs are one of the key sources where we get constructive feedback. When the Script Browser was demoed at the 2013 MVP Global Summit in November, 2014 Japan MVP Open Day, and a Product Group Interaction event, the MVP community proposed insightful improvements. For instance, MVPs suggested showing a script preview before users can decide to download the complete script package. MVPs also wanted to be able to search for script samples offline. These were great suggestions, and the team immediately added the features to the release. We have collected a pool of great ideas (e.g. MVPs also suggested that the Best Practice rules checking feature in Script Analyzer should be extensible). We are committed to continuously improving the app based on your feedback.

We have an ambitious roadmap for Script Browser. For example, we plan to add more script repositories to the search scope. We are investigating integration with Bing Code Search. We are also trying to improve the extensibility of Script Analyzer rules. Some features, like script sample sharing and searching within an enterprise, are still in their infancy.

We sincerely suggest you give Script Browser a try (click here to download). If you love what you see in Script Browser, please recommend it to your friends and colleagues. If you encounter any problems or have any suggestions for us, please contact us at onescript@microsoft.com.  Your precious opinions and comments are more than welcome.

 

 

Acknowledgement

Individually, we are one drop. Together, we are an ocean.  The v1 release of Script Browser is a big collaborative effort from many teams at Microsoft.   Mei Liang, Dan Ruder, Jialiang Ge, Bill Grauer, Allen Ding, Allen Li, Huajun Gu (MVP), Qi Fu from Microsoft CSS worked with the PowerShell Product Group represented by John Slack (PM), Frederic Francois, Samuel Li, Susan Mings, Vlad Carpenco, and Kriti Jindal, and the TechNet Script Center team represented by Bryant Hawthorne.  Pei Wang and Satoru Kitabata localized the app to 14 languages.  Microsoft GARAGE (Ben Gilbert is the PM) provides a perfect platform to demonstrate the app and internally crowd-source ideas and effort to make it better. Nearly 20 Microsoft Garage volunteers, and even their wifes, contributed test and localization to the release: Michael Janelle-Montcalm, Tiago Damasceno, Leland Holmquest's wife Geylan Holmquest, Petr Rybak, Igor Rybak, Piotr Walaszek, Cale Teeter's wife, Jose Cardenas Salazar, Aldo Mendoza Saucedo, Damian Leibaschoff (PSS), Markus Jansen, Tim Sullivan, Jorge Aleman Rodriguez, Ronald Aigner, Roberto Aldaba Mendez, Raffaele Limosani, Christian Kuhtz, Eric Chang (MSR), Erik Millan Jimenez, Tino Morenz.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • ISE opens and errors as it tries to load it from PowerShellISE_profile, some of the error text:

    Add-Type : Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
    At \\profilepath\profile\Documents\WindowsPowerShell\Microsoft.PowerShellISE_profile.ps1:9 char:1
    + Add-Type -Path 'C:\Program Files (x86)\Microsoft Corporation\Microsoft Script Br ... +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [Add-Type], ReflectionTypeLoadException
    + FullyQualifiedErrorId : System.Reflection.ReflectionTypeLoadException,Microsoft.PowerShell.Commands.AddTypeCommand

    Exception calling "Add" with "3" argument(s): "Cannot create element because an exception occurred with the message: The invocation of the constructor on type
    'ScriptExplorer.Views.TechNetView' that matches the specified binding constraints threw an exception..
    Parameter name: controlType"
    At \\profilepath\profile\Documents\WindowsPowerShell\Microsoft.PowerShellISE_profile.ps1:11 char:1
    + $scriptBrowser = $psISE.CurrentPowerShellTab.VerticalAddOnTools.Add('Script Brow ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ArgumentException


    The lines added to the profile are:

    #Script Browser Begin
    #Version: 1.2.1
    Add-Type -Path 'C:\Program Files (x86)\Microsoft Corporation\Microsoft Script Browser\System.Windows.Interactivity.dll'
    Add-Type -Path 'C:\Program Files (x86)\Microsoft Corporation\Microsoft Script Browser\ScriptBrowser.dll'
    Add-Type -Path 'C:\Program Files (x86)\Microsoft Corporation\Microsoft Script Browser\BestPractices.dll'
    $scriptBrowser = $psISE.CurrentPowerShellTab.VerticalAddOnTools.Add('Script Browser', [ScriptExplorer.Views.MainView], $true)
    $scriptAnalyzer = $psISE.CurrentPowerShellTab.VerticalAddOnTools.Add('Script Analyzer', [BestPractices.Views.BestPracticesView], $true)
    $psISE.CurrentPowerShellTab.VisibleVerticalAddOnTools.SelectedAddOnTool = $scriptBrowser
    #Script Browser End


    The execution policy is unrestricted, any ideas from anyone will be much appreciated.

  • Just realised my .Net is not as up-to-date as I thought (only on 4.0), will try 4.5 and advise.

  • Yep - latest version of .Net helps.

  • thank you

  • Script browser 1.4 is showing reproducible error only upon retrieving a certain number of listings and same version of Script Browser was not displaying this behavior a week ago. This behavior/error only began few days ago and reproducible on multiple machines. Filter for only Powershell and Powershell Workflow, sort by release date, scroll to bottom. Script Browser will successfully pull next 10 results. Unlike a week ago when it was able to scroll into thousands, when it hits 90 (was 70 for a couple of days) it then displays red "Network error. Please check your internet connection and the proxy setting" error at top of results. Scrolling back up and down forces Script Browser to re-attempt to retrieve next 10 but will never be successful. This product not listed under standard support so not sure where else to report this bug.