Product, version and build: PowerShell Studio 2016 5.2.119
32 or 64 bit version of product: 64
Operating system: Win 8.1
32 or 64 bit OS: 64
PowerShell Version: 5.0.10586.117
Hello,
I noticed that $PSCmdlet is not available when editing Advanced Functions inside PowerShell Studio.
For example if I try to work on the following script and add $PSCmdlet at the line 90, It does not show in intellisense.
https://raw.githubusercontent.com/lazyw ... esktop.ps1
Did I miss something ?
Thank you
$PSCmdlet is not available
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.
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.
Re: $PSCmdlet is not available
I just want to add that $PSCmdlet is working in adv functions but not in a multi layers/scopes one like the one in the link
Let me know if I can provide more information.
I hope this is not me missing out something... :-/
Thank you.
Let me know if I can provide more information.
I hope this is not me missing out something... :-/
Thank you.
Francois-Xavier Cat
PowerShell MVP/SAPIEN MVP
PowerShell MVP/SAPIEN MVP
Re: $PSCmdlet is not available
This issue should be resolved in the next service release.
David
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: $PSCmdlet is not available
Awesome! Thanks Daviddavidc wrote:This issue should be resolved in the next service release.
David
Francois-Xavier Cat
PowerShell MVP/SAPIEN MVP
PowerShell MVP/SAPIEN MVP