Please notice that when you hover the mouse over the module name, the module version will be displayed.Īt this point, the selected module is available under the Object Browser section and can be easily added using the following steps:

Now, the local cache has been updated with the module(s) you want to use in PowerShell Studio.

To update the Object Browser with the changes, click on the “ Build Cache“, and “ Close” the editor.

Uncheck the older version – 1.0, then check the newer version (14.0).

For example, look at the SQLPS module which has two versions installed:.

In order to load the new module(s) manually, follow these steps: Using the Cache Editor to manually add or update a module This will open the “ PowerShell Cache Editor“.

Or use the PowerShell Cache Editor – to modify and update the existing cache, which can be found via the Ribbon->File->Home->Platform->Edit Cache icon.

Refresh Cache – Refresh the cache using the button via the Ribbon->Home->Platform->Refresh Cache.

There are two ways you can update the cache: The module must be located in a PSModulePath directory in order to be discovered by the caching process. Use the following PowerShell one-liner(s) to display the content stored in the PSModulePath: “ $env:PSModulePath“, or “ $env:PSModulePath.Split(‘ ’)“.īecause PowerShell Studio uses a cache of the modules, newly installed modules will not be displayed automatically in the Object Browser.

The *cached cmdlets and modules are used to provide PrimalSense, syntax coloring for your PowerShell scripts, and are displayed in the Object Browser. One feature of PowerShell Studio that you want to pay attention to is the PowerShell Cache Editor. When PowerShell Studio is opened for the first time, it creates a cache of all available cmdlets and modules that are on your local machine.

Sapien powershell studio update list