32 or 64 bit version of product: 64bit
Operating system: Windows 7 Home Premium and Windows 10 Enterprise
32 or 64 bit OS: both 64bit
When I first saw this happening I had NO idea what was causing it.
Now that I have written a PSF expressly for the SAPIEN forums I believe that I know exactly what is causing this behavior.
If you use the SAPIEN ConvertTo-DataTable function, which is a GREAT piece of code that I love.
DO NOT set a breakpoint AT or BEFORE the function call where one of the following things is to be evaluated and displayed in the Watch panel:
Code: Select all
When you have this script/form loaded in PSS first set a breakpoint somewhere AFTER the ConvertTo-DataTable function is called.
Then after as many runs as you want to make through the program using the "Retry loading data" button, enter one or both of the two above things to the Watch panel.
(I did not check the DataTable object first to see whether it had a Count property before I added that to the Watch panel )
Then hit the "Retry loading data" button again and see what happens.
After that has gone south once in a Debug Run it can not get better by itself, you have to stop Debugging and remove these "bad guys" from the Watch panel then you CAN run Debug again without this problem.
While writing this test program I took a look at the DataTable object and found these two calls for showing the information that I was trying to get by using the .Count call above.
Code: Select all
I don't think that SAPIEN wants the Watch panel to be having this effect.
I do remeber seeing an article in the internet about property hijacking and I am pretty sure that is happening here.
I hope you can fix the Watch panel from having such a side effect when someone, like me, puts something in there that does NOT work but keeps it from breaking the object.