Use this forum to ask questions after your subscription maintenance expires or before you buy. Need information on licensing or pricing? Questions about a trial version? This is the right place for you. No scripting questions, please.
Forum rules DO NOT POST SUBSCRIPTION NUMBERS, LICENSE 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.
This topic is 6 years and 10 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.
Product, version and build: PowerShell Studio 2017 (5.4.140.0) 32 or 64 bit version of product: 64-bit Operating system: Windows 8.1 32 or 64 bit OS: 64-bit
I'm trying to get PowerShell Studio to load some custom modules (.psm1) that I use in a lot of my scripts, so that PrimalSense will be aware of the functions/parameters/etc.
I have done the following in order to attempt to make this happen. (Still can't post images; copy and paste the links to view them.)
If you updated your module without increasing the version number it will not be re-imported because it thinks it is already cached.
So either delete the module first and then import it again or increase the version number when you make changes to your module.
This is the first time I have ever tried to import the module, and none of its functions are recognized by PrimalSense, so the version number is irrelevant.
In that case please provide some more information about your module. Is it exporting functions? Classes?
Are none of the functions in your module visible? Can you see the module and its functions in the Object browser?
I can't send you that specific module since it contains proprietary code that I can't share, but I can provide a second module that is exhibiting the same behavior. What would be the best way for me to do so?
This topic is 6 years and 10 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.