Primal

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 4 years and 11 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
mjgelinas
Posts: 2
Last visit: Thu Mar 14, 2024 8:40 am

Primal

Post by mjgelinas »

To help you better we need some information from you.

*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***

Product, version and build:
PrimalScript (64 Bit)
Build: v7.4.127
OS: Windows 10 Enterprise (64 Bit)
Build: v10.0.17134

*** Please add details and screenshots as needed below. ***

DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM

PrimalScript function references intermittently display either "NO" information or incorrect information regarding number of times the function is called in a module.
PrimalScript also doesn't have information regarding references to modules that are included in the local PowerShell cache it builds periodically. PowerShell Studio readily provides information about a function and it's module location when hovered over, PrimalScript does not. (is this functionality that will be added at some point?)
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 20
Been upvoted: 37 times

Re: Primal

Post by Alexander Riedel »

"PrimalScript function references intermittently display either "NO" information or incorrect information regarding number of times the function is called in a module."
That would point to a parser error. Since PowerShell is a language with a certain 'latitude' on syntax, that is quite possible. But in order to
really determine that, we would need an actual sample.

As for the last part, just so I understand this correctly, you want PrimalScript to tell you exactly where PowerShell will load a module from when you hover of a function or cmdlet before it is actually executed?
Alexander Riedel
SAPIEN Technologies, Inc.
This topic is 4 years and 11 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.