Archive for the ‘Windows PowerShell’ Category


SAPIEN Script Packager updates and new features.

Monday, October 24th, 2016 by Alex Riedel
The Script Packager in PrimalScript 2016 gets an update with the next service build (7.2.95). Since this service build changes the locations where your executable files are generated and some new options are available, we thought we'd let you know about these changes before they are actually released. Based on your feedback, the script engine selection in the Packager settings was too confusing. So we updated the user interface to minimize the number of selections and provide you with a preview of what this selection will do. Furthermore, as many of you indicated that you still need to support 32…   More »

Setting up PowerShell on your Mac (Update!)

Friday, August 19th, 2016 by Ferdinand Rios
Now that PowerShell is available on the Mac, we thought it would be useful to show how easy it is to setup a Mac terminal session that automatically opens into PowerShell. Figure 1 shows what we mean. [caption id="attachment_12634" align="aligncenter" width="1130"] Figure 1 - PowerShell Terminal Session[/caption] First you need to download the PowerShell macOS package from here (look for the Get PowerShell section in the and install it using the directions found here . Once PowerShell is installed and running on your system, follow the instructions below to set up your PowerShell terminal Here are the steps to follow: Open Terminal on…   More »

HelpUri v. HelpInfoUri

Tuesday, August 16th, 2016 by June Blender
Although the names are similar and often confused, these properties are different. If you confuse them, the help for your PowerShell commands and modules won't work. The HelpUri property stores the URL (http or https) of online help for a command. It's a property of commands (cmdlets, functions, workflows). When a user runs Get-Help -Online, Get-Help opens the default browser to the HelpUri property value. The HelpInfoUri property of modules stores the URL of the online location of the HelpInfo XML file that enables updatable help for the module. In fact, a non-null value of HelpInfoUri indicates that the module…   More »

Writing Help for Dynamic Parameters

Monday, August 8th, 2016 by June Blender
Because dynamic parameters can be added to a command from multiple sources, the command author (who writes the help) cannot predict the dynamic parameters that might be available at runtime. Therefore, Get-Help expects dynamic parameters to be documented in the help file for the code that adds the dynamic parameters; not the code that has the dynamic parameters. This makes sense in theory, but, in practice, it's not discoverable and it's very confusing for users. To write help for the dynamic parameters that you add to cmdlets and functions, you need to sneak it into the description. I'll show you…   More »

How Do Multi-Form Projects Work?

Thursday, July 28th, 2016 by June Blender
Applies to: PowerShell Studio 2016, Windows PowerShell 3.0+ I recently wrote an article with step-by-step instructions for creating a very simple multi-form PowerShell GUI application. In our sample app, we use PowerShell Studio features that make it very easy to open a child form from the main form and gets the text in the textbox on the child form. In this article, I'll explain what goes on in the background to make these features work. You might not care -- just so they work -- and that's fine. But if you're wondering how this happens, or you need to debug…   More »

Write a Multi-Form PowerShell GUI App

Tuesday, July 26th, 2016 by June Blender
Tested on: PowerShell 2.0+, PowerShell Studio 2016 This step-by-step example shows you how to create a very simple multi-form PowerShell GUI app. The app consists of a parent form that gets data from a child form and displays it. When you finish, you'll know how to use the basic multi-form features of PowerShell Studio. For details about how these features work under the covers, see How Do Multi-Form Projects Work? For this task, we assume that you know how to create a single-form PowerShell GUI app or that you've participated in a Thinking in Events hands-on lab. Otherwise, start with…   More »

Introducing the SAPIEN Information Center

Tuesday, July 12th, 2016 by June Alane Reif
Over the years, the articles in this blog have grown extensively. There's a lot of valuable information in here, but it's become hard to find because it's mixed in with various tour announcements, special offers, conference recaps, and the like. So, we have decided to pull the important articles and place them—along with information relevant to PowerShell and scripting—in a more organized and easily searchable venue. We are proud to introduce the SAPIEN Information Center. The most recent articles are always highlighted in a list on the left side of the window. The SAPIEN Information Center currently has the following…   More »

PrimalScript 2016 service build adds CPU and memory performance graphs

Thursday, July 7th, 2016 by Alex Riedel
The latest service build of PrimalScript 2016 (7.2.91) adds performance graphs for your scripts. To enable this feature you just need to make the “Performance” tab visible before you execute your script. Performance data can be collected on any script run from within PrimalScript as long as you enabled output redirection. That means this applies to PowerShell, VBScript, Perl or any other script that you run from within PrimalScript. The output window will also display the peak values during the execution of your script when it finishes. Since collecting this data while executing your script obviously adds additional CPU and…   More »

PowerShell Studio 2016 – Service Release & High DPI Support

Tuesday, July 5th, 2016 by David Corrales
We released a new service build of PowerShell Studio 2016 (v5.2.124)!   Here’s what’s new: High DPI Support We have added high DPI support to PowerShell Studio’s UI. Those of you who previously ran PowerShell Studio on a high DPI monitor (Windows 10 in particular) probably noticed that the application appeared fuzzy. The fuzzy appearance is caused by Windows’ scaling of non-DPI aware applications. The good news is that this no longer the case with PowerShell Studio 2016. Not DPI Aware DPI Aware High DPI Layouts With high DPI screens, you will require high DPI layouts. When PowerShell Studio detects…   More »

Using a ModuleSpecification Object

Monday, June 27th, 2016 by June Blender
With the advent of side-by-side module versions in Windows PowerShell 5.0, the lovely, but obscure ModuleSpecification object has become your new best friend. Use it to make sure that the commands and module that you use are the ones that you intend. Using ModuleSpecification Let's start with an example. I want to get the Expand-Archive command in the Microsoft.PowerShell.Archive cmdlet. I can use Get-Command, of course, but when I surround the command name with wildcard characters to make sure it searches, it returns this: PS C:\ > Get-Command *Expand-Archive* CommandType Name Version Source ----------- ---- ------- ------ Function Expand-Archive…   More »