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 \u2013script filename.ps1 \u2013line xxx as needed and launch the whole thing from the command line, but let\u2019s face it, if you do that more than twice it gets a bit old.<\/p>\n
PrimalScript already saves your breakpoints with your files, so once you set them they are just there. Now, just open the files you need and select the new \u201cDebug Multiple Scripts\u201d topic.<\/p>\n
Select the startup file and the secondary files accordingly:<\/p>\n And click OK. That\u2019s it, the debugger will now just pace through your files and stop at your breakpoints:<\/p>\n Hitting the first breakpoint in our startup file<\/em><\/p>\n <\/p>\n Hitting the breakpoint in the second file <\/em><\/p>\n <\/em> <\/p>\n And a third file<\/em><\/p>\n <\/p>\n![\"image\"](\"http:\/\/www.sapien.com\/blog\/wp-content\/uploads\/2012\/09\/image.png\" "\\"image\\"")
<\/a><\/p>\n<\/a><\/p>\n<\/a> <\/p>\n<\/a> <\/p>\n<\/a> <\/p>\n