Posts Tagged ‘Debugger’


PrimalScript 2014 PowerShell Debugger enhancements

Monday, August 18th, 2014 by Alex Riedel
PrimalScript 2104’s PowerShell Debugger has received a minor update with build 7.0.44. The variables window now shows the actual .NET type of the underlying variable in a separate column. In addition to that you can also see array data. If you look closely at the screenshot above you see a “[… Click to see array values …] for the variable called “myArray”. Clicking on that will retrieve the first 20 items in this array. It only retrieves a maximum of 20 items for performance reasons and because this particular way of displaying the array data does not lend itself to…   More »

PrimalScript 2014: VBScript gets a debug console

Monday, March 31st, 2014 by Alex Riedel
One of the many things on our users wish list was the ability to change variables while debugging. While we where looking to solve that, we also looked for a way to call functions while stopped at a breakpoint or execute any arbitrary code that may help facilitate testing and debugging. Since we already have a debug console doing that exact same thing for PowerShell, we thought it would be best to do the same thing for VBScript and JScript. So now setting a variable or an objects property is as easy as typing it into the console. Call functions,…   More »

But it works on my machine…

Thursday, May 16th, 2013 by Alex Riedel
We have all heard that phrase. We have all faced that scenario. A script runs perfectly fine on your machine or any VM you have, but just refuses to do anything useful on that one server where it really matters. Error messages can be notoriously unhelpful. “Access denied”, yes, but to WHAT and WHY? And everyone’s favorite “Unknown error” makes for a very frustrating day at the office. If you have physical or remote desktop access to that server it’s pretty easy, just use whatever debugger you have, install it on that machine and see what happens. Or, in case…   More »

Debugging PowerShell modules with PrimalScript 2012

Friday, October 12th, 2012 by Alex Riedel
The latest service build of PrimalScript 2012 (6.5.132) makes debugging modules a bit easier. If you are developing a script module you most likely already have a script that exercises the various cmdlets in your module. Just load that script and your psm1 file into PrimalScript, set your breakpoints and hit F5 with your module file active. This dialog will show you all the open PowerShell scripts. Just select the one you use to drive or test your module and press OK. And there we are, hitting the breakpoint inside your module. It’s as simple as that. All other debugging…   More »

Debugging multiple scripts with PrimalScript 2012

Thursday, October 11th, 2012 by Alex Riedel
Debugging a simple script with a few lines is not a big deal, hit debug and step through it. Almost any PowerShell related editor can do that today. But what if you need to debug a complete system of scripts interacting with one another? This new service build of PrimalScript 2012 introduces the ability to debug multiple scripts. Sure you could type Set-PSBreakPoint –script filename.ps1 –line xxx as needed and launch the whole thing from the command line, but let’s face it, if you do that more than twice it gets a bit old. PrimalScript already saves your breakpoints with…   More »

PowerShell V3 breakpoint bug

Monday, September 24th, 2012 by Alex Riedel
While we are adapting and verifying all our bits and pieces for PowerShell V3 and Windows 8, we sometimes stumble across little changes from PowerShell V2 behavior. Most of the time this is pretty simple and we can adapt our code to a new object or a change of where the information is located. Sometimes however we come across a real bug. This is one of these instances. The following has been tested in Windows 8 RTM with the PowerShell V3 ISE (64 Bit). Take the following simple script: We will put a breakpoint on line 2 and hit run:…   More »

SAPIEN at Tech-Ed 2012

Tuesday, May 29th, 2012 by Ferdinand Rios
Once again, SAPIEN will be in attendance at Tech-Ed 2012, this year held in Orlando from June 11th - 14th. If you are going to be there, look for us at booth 1748. This year, we will be focussing on our Powershell related products: PrimalScript 2012, PowerShell Studio 2012 and iPowerShell Pro.   PrimalScript 2012 is the newest iteration of our cornerstone product sporting a redesigned UI, File Tab backstage view, redesigned print page, editor improvements, native Powershell remoting, an improved debugger with tracepoints and Remote PowerShell debugging.   PowerShell Studio 2012 replaces PrimalForms and adds a host of new…   More »

PrimalScript 2012: What’s new? (Part 6)

Monday, May 7th, 2012 by Alex Riedel
VBScript users have told me on occasion that they are really jealous of one feature of PowerShell: Write-Debug Depending on the value of $DebugPreference this produces output when needed but makes it easy to silence diagnostic output once a script moves to production. VBScript and JScript developers have to sprinkle WScript.Echo calls through their code and then go and comment them out before handing the script off. In a large script with hundreds or even thousands of lines that can be a daunting and error prone task. You don't want to disable real output and not forget any diagnostic output.…   More »

Feature Peek PrimalScript 2011: Debugging with arguments

Tuesday, March 22nd, 2011 by Alex Riedel
Many of the scripts you develop use command line arguments to specify data that needs to be passed to the script. In a production environment these parameters usually change for each invocation of a script. For debugging however most developers use a fixed set of test parameters for any given script, which allows you to easily reproduce the state you need for debugging a specific item. In the past that meant that for each script you had to manually set the parameters somewhere in a dialog box before debugging. It also meant that you somehow had to remember what the…   More »

Feature Peek PrimalForms 2011: Debugger

Monday, March 14th, 2011 by David Corrales
You saw PrimalScripts 2011’s new PowerShell debugger and now its time to show you the same debugger in PrimalForms 2011. Multi-Platform Support Since PrimalForms 2011 shares the same debugger as PrimalScript, it  also supports 32 bit & 64 bit script execution with the option to elevate. Variables Pane View all the session variables and their property values. (Fig 1: Variables Pane) Watch Pane The Watch Pane allows you to specify variable expressions that you wish to monitor without having to search for the variable. (Fig 2: Watch Pane) Call Stack Pane View the current call stack when debugging your scripts…   More »