Dear Support, My activation status shows 2 activations ( 2 machines) but i use only one. The 2nd activation might have been for a laptop that crashed. So the 2nd one never was released or deactivated. In the near future I want to transfer the license to a colleague, so need to deactivate my current ...

Conditional breakpoints are grayed out when Powershell V2 is selected. You must have PowerShell V3 or higher installed and selected. If you have the script analyzer installed, it should be under Program files or in the modules folder under your My Documents folder. These are the two default locatio...

Product, version and build:7.2.84 32 or 64 bit version of product:64 Operating system:Win7 32 or 64 bit OS:64 Blog "Setting Conditional Breakpoints" states that this is available in PrimalScript 2016 as well. Editing a PS1 file the related options Set Variable Breakpoint/Set Function Breakpoint/Edi...

Sapien says: Just keep it on your flash drive and run it wherever you need it.
Unfortunately that is not true due to the license key, it simply won't run on a different machine. What is the point of the flash drive if not wherever.
btw: nice product!

The Check for Updates issue has been resolved. A bit too much of a 32-64 bit mix. Removed obsolete 32bit entries.
There has been an error on my part: 7.0.30 install was 32bit.
That needed a repair to function. 7.0.31 is 64bit. repair is gone.

Win7 64 bit, PrimalScript 2014 64 bit Program and Features shows all installs for PrimalScript 2014 and without size. 2012 version was not removed rightaway when updating to 2014. Now uninstalled 2012, but the entry is still there. Can remove that through registry. Is this Uninstall-Install effect s...

Too late, they were ok. Edit is and was associated with PrimalScript. Before install "Open" was the default action. After the install "Edit" was the default. That behaviour was observed on two different machines. I agree, it not supposed to do that. But it did. No further harm done.