Quick access

Getting started with Script Browser 1.3.2

Download: http://www.microsoft.com/download/details.aspx?id=42525
Script Browser enables you to search and reuse over 9000 script samples from within your scripting environment. It puts thousands of scripts at your fingertips when you automate your IT.

Hello, We have "My Documents" redirected in our environment which seems to cause an issue on install. Error is:
Error 1001. An Exception Occurred during Commit phase of the installation. This exception will be ignored and installation will continue. However, the application might not function correctly after installation is complete. --> Access to the path '\\remoteserver\documents$\username' is denied.
But the install then rolls back rather than ignoring the exception as one would expect from the error text. I've worked around this by just running it as a user without that policy, but it would be nice to get that fixed.

We are fixing the 1001 install problem in the upcoming 1.1 update of Script Browser. Here is a temp workaround:
Start a new cmd command prompt as administrator (run as administrator), navigate the ScriptBrowser.msi file, and run the msi.
After you launch the Script Browser after the successful installation, you may want to change the sample download location in the settings immediately to a local folder. We do not support downloading samples to a shared folder in the current version.

The line below generates an error which prevents the Script Browser from working.
$scriptBrowser = $psISE.CurrentPowerShellTab.VerticalAddOnTools.Add('Script Browser', [ScriptExplorer.Views.MainView], $true)
This is the error message:
Exception calling "Add" with "3" argument(s): "Cannot create element because an exception occurred with the message: The specified registry key does not exist..
Parameter name: controlType"
The error message does not list the registry key that does not exist.
Thoughts?

Hello,
Thank you for reporting the issue.
We have found the problem and fixed it in our source control. The issue impacts users whose locale treats double number as #,#### (e.g. 1,2). Before we release the 1.1 version of Script Browser in the near future to include the fix and some small features, would you please try the following workaround that a MVP figured out?
http://powershelltaskforce.com/2014/04/problem-with-the-new-script-browser-add-on-for-ise-and-culture-settings/
Best Regards,
Microsoft All-In-One Script Framework