Issue after PowerShell Studio 5.6.158 update
Posted: Fri Feb 08, 2019 9:24 am
Since installing the PowerShell Studio 5.6.158 update this morning on my Windows 10 1803 x64 system I'm finding many functions/Cmdlets referenced in scripts not being "detected" (the text is grey instead of blue, and auto-complete in regards to parameters doesn't work). This includes Cmdlets from the builtin ActiveDirectory module as well as functions from my own script modules. I first noticed this happening after I updated a script module under the WindowsPowerShell\Modules folder in my 'My Documents' folder and clicking the 'Refresh Local Cache' button in the Home ribbon in PowerShell Studio. Prior to doing that I didn't notice anything not being detected.
I found that in the PowerShell Cache Editor the Modules that I'm having issues with are present (with the exception that my most recently updated script module was showing the wrong version and the latest version had to be imported), but not checked. I've tried checking the modules and clicking 'Build Cache', following by 'Close', but the functions/Cmdlets are still not detected. If I go back into the PowerShell Cache Editor the module are still checked. Closing/Re-opening PowerShell Studio after checking the modules and clicking 'Build Cache' does seem to result in the functions/Cmdlets being detected.
In previous versions of PowerShell Studio Cmdlets in modules from RSAT (like Get-ADUser) would always automatically be detected, and script modules I placed in my 'My Documents' folder would also automatically be detected, and if I updated them I could click the 'Refresh Local Cache' button and within a minute the new script module would be imported, without having to close/relaunch PowerShell Studio. Has the functionality around all this been changed in this new version, or is something just not working as it's supposed to?
Thanks,
Cody
I found that in the PowerShell Cache Editor the Modules that I'm having issues with are present (with the exception that my most recently updated script module was showing the wrong version and the latest version had to be imported), but not checked. I've tried checking the modules and clicking 'Build Cache', following by 'Close', but the functions/Cmdlets are still not detected. If I go back into the PowerShell Cache Editor the module are still checked. Closing/Re-opening PowerShell Studio after checking the modules and clicking 'Build Cache' does seem to result in the functions/Cmdlets being detected.
In previous versions of PowerShell Studio Cmdlets in modules from RSAT (like Get-ADUser) would always automatically be detected, and script modules I placed in my 'My Documents' folder would also automatically be detected, and if I updated them I could click the 'Refresh Local Cache' button and within a minute the new script module would be imported, without having to close/relaunch PowerShell Studio. Has the functionality around all this been changed in this new version, or is something just not working as it's supposed to?
Thanks,
Cody