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: Powershell Studio 2019 5.6.157
32 or 64 bit version of product: 64
Operating system: Windows 10
32 or 64 bit OS: 64
*** Please add details and screenshots as needed below. ***
DO NOT POST SUBSCRIPTIONS, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
My powershell Studio is no longer able to show variables in debug mode. It used to take a few minutes to process but now it doesn't finish processing at all. I'm also getting two new error message with this version:
ERROR: Split-Path : Cannot bind argument to parameter 'Path' because it is null.
Globals.ps1 (246, 14): ERROR: At Line: 246 char: 14
ERROR: + Split-Path $hostinvocation.MyCommand.path
ERROR: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ERROR: + CategoryInfo : InvalidData: (:) [Split-Path], ParameterBindingValidationException
ERROR: + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.SplitPathCommand
ERROR: Exception setting "AutoCompleteMode": "Current thread must be set to single thread apartment (STA) mode before OLE calls can be made. Ensure that your Main
ERROR: function has STAThreadAttribute marked on it."
NewHireApp.Run.ps1 (20102, 2): ERROR: At Line: 20102 char: 2
ERROR: + $comboboxLocation.AutoCompleteMode = 'Suggest'
ERROR: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ERROR: + CategoryInfo : NotSpecified: (:) [], SetValueInvocationException
ERROR: + FullyQualifiedErrorId : ExceptionWhenSetting
ERROR:
Can I revert to the previous working version?
Version 5.6.157 debugging issue
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.
- cnguyen2016
- Posts: 3
- Last visit: Wed Apr 29, 2020 10:13 am
- Alexander Riedel
- Posts: 8479
- Last visit: Thu Mar 28, 2024 9:29 am
- Been upvoted: 37 times
Re: Version 5.6.157 debugging issue
Please follow instructions here:
viewtopic.php?f=12&t=13618
viewtopic.php?f=12&t=13618
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
- cnguyen2016
- Posts: 3
- Last visit: Wed Apr 29, 2020 10:13 am
Re: Version 5.6.157 debugging issue
Thanks, the update worked. However I'm getting prompted every time I debug.
- Attachments
-
- powershell2019b.PNG (24.13 KiB) Viewed 1772 times
Re: Version 5.6.157 debugging issue
We released the v5.6.158 service build that resolves this issue:
https://www.sapien.com/blog/2019/02/05/ ... -v5-6-158/
https://www.sapien.com/blog/2019/02/05/ ... -v5-6-158/
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.