Page 1 of 1

Setting Conditional Breakpoints

Posted: Tue May 03, 2016 1:03 am
by PeterW
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/Edit Breakpoints are always grayed out.
Do i miss or misunderstand something?
The (Build and Run) Analyze returns "PSScriptAnalyzer is not installed in its default location0 error(s), 0 warning(s)"
Help is appreciated

Re: Setting Conditional Breakpoints

Posted: Tue May 03, 2016 1:11 am
by Alexander Riedel
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 locations. Do you have it some place else installed?

Re: Setting Conditional Breakpoints

Posted: Tue May 03, 2016 1:52 am
by PeterW
Alexander Riedel wrote: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 locations. Do you have it some place else installed?
Thanks Alexander, your reply answered all my questions.