{"id":14161,"date":"2017-12-07T06:30:15","date_gmt":"2017-12-07T14:30:15","guid":{"rendered":"https:\/\/www.sapien.com\/blog\/?p=14161"},"modified":"2017-12-06T19:41:56","modified_gmt":"2017-12-07T03:41:56","slug":"powershell-studio-feature-nugget-refreshing-local-cache-powershell-cmdlets-and-modules","status":"publish","type":"post","link":"https:\/\/dev.sapien.com\/blog\/2017\/12\/07\/powershell-studio-feature-nugget-refreshing-local-cache-powershell-cmdlets-and-modules\/","title":{"rendered":"PowerShell Studio Feature Nugget – Refreshing Local Cache PowerShell Cmdlets and Modules"},"content":{"rendered":"

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

\"\"<\/a><\/p>\n

The module must be located in a PSModulePath directory in order to be discovered by the caching process.\u00a0Use the following PowerShell one-liner(s) to display the content stored in the PSModulePath: “$env:PSModulePath<\/strong>“, or “$env:PSModulePath.Split(‘;’)<\/strong>“.<\/p>\n

\"\"<\/a><\/p>\n

Because PowerShell Studio uses a cache of the modules, newly installed modules will not be displayed automatically in the Object Browser.<\/p>\n

There are two ways you can update the cache:<\/p>\n

    \n
  1. Refresh Cache –\u00a0<\/strong>Refresh the cache using the \u00a0button via the Ribbon->Home->Platform->Refresh Cache.<\/li>\n<\/ol>\n

    \"\"<\/a><\/p>\n

      \n
    1. Or use the PowerShell Cache Editor<\/strong>\u00a0 – to modify and update the existing cache, which can be found via the Ribbon->File->Home->Platform->Edit Cache\u00a0icon.<\/li>\n<\/ol>\n

      \"\"<\/a><\/p>\n

      This will open the “PowerShell Cache Editor<\/strong>“.<\/p>\n

      \"\"<\/a><\/p>\n

      Using the Cache Editor to manually add or update a module<\/h4>\n

      In order to load the new module(s) manually, follow these steps:<\/p>\n

        \n
      1. Open the \u201cPowerShell Cache Editor<\/strong>\u201c.<\/li>\n
      2. For example, look at the SQLPS module which has two versions installed:
        \n        \"\"<\/a><\/li>\n
      3. Uncheck the older version – 1.0, then check the newer version (14.0).<\/li>\n
      4. To update the Object Browser with the changes, click on the \u201cBuild Cache<\/strong>\u201c, and \u201cClose<\/strong>\u201d the editor.
        \n        \"\"<\/a><\/li>\n<\/ol>\n

        Now, the local cache has been updated with the module(s) you want to use in PowerShell Studio. Please notice that when you hover the mouse over the module name, the module version will be displayed.<\/p>\n

        \"\"<\/a><\/p>\n

        At this point, the selected module is available under the Object Browser section and can be easily added using the following steps:<\/p>\n

          \n
        1. By drag-drop from the Object Browser.
          \n          \"\"<\/a><\/li>\n
        2. Or, by just typing the command and the PrimalSense will response with a list of commands to choose.
          \n          \"\"<\/a><\/li>\n<\/ol>\n

          Notice, while working with the \u201cPowerShell Cache Editor<\/strong>\u201d, there’s no need to use the “Refresh Local Cache<\/strong>“.<\/p>\n

          Just remember, when having multiple versions of the same module, make sure to use the latest one.<\/p>\n","protected":false},"excerpt":{"rendered":"

          One feature of PowerShell Studio that you want to pay attention to is the PowerShell Cache Editor.\u00a0When PowerShell Studio is opened for the first time, it creates a cache of all available cmdlets and modules that are on your local machine. The *cached cmdlets and modules are used to provide PrimalSense, syntax coloring for your […]<\/p>\n","protected":false},"author":47,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1143,703,303],"tags":[28,1080,1016,1188],"class_list":["post-14161","post","type-post","status-publish","format-standard","hentry","category-powershell","category-powershell-studio","category-tip","tag-powershell","tag-powershell-modules","tag-powershell-studio","tag-powershell-studio-2017"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/14161","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=14161"}],"version-history":[{"count":16,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/14161\/revisions"}],"predecessor-version":[{"id":14255,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/14161\/revisions\/14255"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=14161"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=14161"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=14161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}