Recognize non-installed modules

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 8 years and 5 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
Cliving
Posts: 57
Last visit: Tue Apr 25, 2023 12:37 pm

Recognize non-installed modules

Post by Cliving »

Hello, I was wondering if there was a way I can specify a path to powershell modules that live either locally or on a network share such that the exported cmdlets and functions get the syntax coloring, tab completion, and so forth within the scripting environment. These modules are either ones usually imported through a profile or are dev versions that I would like to work with. I'm familiar with the 'Refresh' option in the object browser, but that only appears to work with installed modules.

Is there a method by which I can add additional module(s) and/or their location(s)? If not, I'm happy to post in the feature request section. Thanks.

OS: Windows 8.1 Enterprise x64
PowerShell Studio 2015: v4.2.95
User avatar
SAPIEN Support Forums
Posts: 945
Last visit: Thu Oct 22, 2015 1:10 pm

Recognize non-installed modules

Post by SAPIEN Support Forums »

This is an automated post. A real person will respond soon.

Thank you for posting, Cliving.

Did you remember to include the following?
  • 1. Product, version and build (e.g. Product: PowerShell Studio 2014, Version & Build: 4.1.71. Version and build information can be found in the product's About box accessed by clicking the blue icon with the 'i' in the upper right hand corner of the ribbon.)
    2. Specify if you are running a 32 or 64 bit version
    3. Specify your operating system and if it is 32 or 64 bit.
    4. Attach a screenshot if your issue can be seen on the screen
    5. Attach a zip file if you have multiple files (crash reports, log entries, etc.) related to your issue.
If not, please take a moment to edit your original post or reply to this one.

*** Make sure you do not post any licensing information ***
User avatar
davidc
Posts: 5913
Last visit: Mon Jul 08, 2019 8:55 am
Been upvoted: 2 times

Re: Recognize non-installed modules

Post by davidc »

As of today, you have to make sure these modules are located in one of the paths defined in PSModulePath.

I believe this is feature on our wish list, but I will make sure it is added if not already.

In the meantime, you can temporarily copy the modules to one of these locations or add the paths to the environmental variable. Then refresh the cache. Once the cache is build, you then can restore the modules to their previous locations.

David
David
SAPIEN Technologies, Inc.
User avatar
Cliving
Posts: 57
Last visit: Tue Apr 25, 2023 12:37 pm

Re: Recognize non-installed modules

Post by Cliving »

Thank you.
This topic is 8 years and 5 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.