Just in case you missed it. With the latest service builds of PrimalScript 2012 and PowerShell Studio 2012 we added support for PowerShell V3. PrimalScript 2012 version switch PowerShell Studio 2012 version switch As you can see it’s pretty easy to switch which version you want to develop for, just press a button. […]
PowerShell Studio Manual
The PowerShell Studio manual was included with the v3.1.9 service release of PowerShell Studio 2012. The SAPIEN Document Explorer must be installed in order to view the manual. You can access the manual from PowerShell Studio by pressing the “Product Manual” button, which is located in the Help tab of the ribbon: Use […]
Developing PowerShell scripts for other machines (Part 2)
Yesterday we showed you how to export the cache information on a remote machine. Today we go through the steps to actually use that information. Remember that we exported the cache file on that Windows 2008R2 machine as “WIN2008R2TESTVM.CacheExport”. Let’s assume we put that file on the desktop of your local machine. Now fire up […]
SAPIEN Gets ZOMBIFIED!
Faster than you can scream “SHAWWWWWN!,” Halloween will be here and we are feeling a bit goofy. So much so that we’re gearing up for a S-C-A-R-Y special, just for you! On Halloween, October 31, buy 5-packs of PowerShell Studio 2012 at 50% off! What?! You heard right—50% off! This will happen only on our […]
Developing PowerShell scripts for other machines (Part 1)
One of the challenges you face while developing any PowerShell script is that modules that reside on your target platform are not available on your local computer. Just as an example, try installing Microsoft SharePoint 2010 modules on your 32 bit Windows XP/Vista/7/8 machine. It just won’t work. PrimalScript 2012 and SAPIEN PowerShell Studio 2012 […]
Debugging PowerShell modules with PrimalScript 2012
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 […]
Major Service Release (10/11/2012)
New versions of PrimalScript 2012 and PowerShell Studio 2012 are available. Registered users can download the latest service builds from MySAPIEN. Release Notes: PrimalScript 2012 v 6.5.132: ADD: PowerShell V3 support ADD: Support for multiple remote machines with individual cache data ADD: Added CacheExport Tool ADD: Support for debugging multiple powershell scripts. ADD: Support for […]
Debugging multiple scripts with PrimalScript 2012
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 […]
Get help for modules on other machines
When you develop scripts for other computers you don’t always have the luxury of installing the relevant modules on your own computer. In many cases they simply won’t install because you are running the wrong OS or don’t have some required server software running. Luckily the context sensitive help in PrimalScript or PowerShell Studio doesn’t […]
How to get support from SAPIEN
Once a year we need to refresh this information, so forgive us if you heard this before. Our trial software is usually not crippled in any way, so just because your are evaluating it nothing should be switched off. So if something is grayed out or inaccessible, it’s usually a configuration issue and not because […]
