Autocompletion fail

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 2 years and 2 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.
mjbrown
Posts: 4
Last visit: Sat Oct 28, 2023 12:41 pm
Has voted: 1 time

Autocompletion fail

Post by mjbrown »

Product, version and build: SAPIEN PowerShell Studio 2021 v.5.8.196
Operating system: Windows Server 2016
PowerShell version(s): 5 & 7

Hi, PrimalSense autocompletion has stopped functioning as expected. This seems to have happened after parameterizing a small script. The available options seem to correctly sense the context within the param() function similar to the example shown in your documentation at /manuals/powershell_studio/sps_primalsense.html
autocompletion in parameter
autocompletion in parameter
parameterContext.png (28.54 KiB) Viewed 5549 times
However when I move out of the param() block, I am not getting the cmdlet autocompletion I am expecting. In the screen capture, I would expect to see a list of cmdlets that begin with the verb get but I do not.
autocompletion fail in script body
autocompletion fail in script body
regularPSContext.png (11.78 KiB) Viewed 5549 times
I have tried removing the script block, and all other code in the file. I still don't get a list of cmdlets after typing a verb. I have tried closing the program, creating a brand new file, saving it with a .ps1 extension and still no luck.

Thanks in advance.
by Alexander Riedel » Thu Jan 06, 2022 9:56 am
7.2.x is not supported yet. Give it another day or two.
Go to full post
User avatar
Alexander Riedel
Posts: 8478
Last visit: Tue Mar 26, 2024 8:52 am
Answers: 19
Been upvoted: 37 times

Re: Autocompletion fail

Post by Alexander Riedel »

Which PowerShell version and platform is currently selected on the Ribbon bar?
Alexander Riedel
SAPIEN Technologies, Inc.
mjbrown
Posts: 4
Last visit: Sat Oct 28, 2023 12:41 pm
Has voted: 1 time

Re: Autocompletion fail

Post by mjbrown »

That did it. Thanks!
Any next steps to get this functionality back while using PS 7 engine?

I had PS 7 selected, no cmdlets suggested in autocomplete dialog.
No cmdlets available in ver. 7
No cmdlets available in ver. 7
PS7Selected.png (126.04 KiB) Viewed 5537 times
I switched to PS5, cmdlets are available in autocomplete dialog.
Cmdlets are available in ver. 5
Cmdlets are available in ver. 5
PS5Selected.png (144.03 KiB) Viewed 5537 times
User avatar
Alexander Riedel
Posts: 8478
Last visit: Tue Mar 26, 2024 8:52 am
Answers: 19
Been upvoted: 37 times

Re: Autocompletion fail

Post by Alexander Riedel »

Which PowerShell 7 version do you have installed?
Alexander Riedel
SAPIEN Technologies, Inc.
mjbrown
Posts: 4
Last visit: Sat Oct 28, 2023 12:41 pm
Has voted: 1 time

Re: Autocompletion fail

Post by mjbrown »

I recently installed 7.2.1 a few days after I installed PS studio.
That's probably when this happened. I can't remember which version of 7 I was running when PowerShell studio was first installed.
User avatar
Alexander Riedel
Posts: 8478
Last visit: Tue Mar 26, 2024 8:52 am
Answers: 19
Been upvoted: 37 times

Re: Autocompletion fail

Post by Alexander Riedel »

7.2.x is not supported yet. Give it another day or two.
Alexander Riedel
SAPIEN Technologies, Inc.
mjbrown
Posts: 4
Last visit: Sat Oct 28, 2023 12:41 pm
Has voted: 1 time

Re: Autocompletion fail

Post by mjbrown »

Sweet. Thank you sir!

<This is me meeting the 50 character requirement.>
This topic is 2 years and 2 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.