In January, I had the honor of presenting to the Mississippi PowerShell User Group (MSPSUG). I’ve known the organizers, Mike Robbins and Rohn Edwards for years, and truly respect them. The PSUG is online-only, which makes it a challenge for presenters, but they attract a very sophisticated audience, so my talks there are really conversations. […]
Category: Best practices
Using Group-Object to Detect Command Name Conflicts
The Group-Object cmdlet, one of the original provider cmdlets, is as old as Windows PowerShell. It was introduced in version 1.0 and hasn’t changed at all since then. But, it is one of my favorites. (You can tell when I love a cmdlet by the number of examples. Group-Object has 9!) In fact, when you use it […]
Running PowerShell Scripts: Survey Results
We’re always evaluating the best, easiest, and most efficient ways to write, run, and publish Windows Powershell scripts and modules. But, our starting point is always how people work now. We were curious about how PowerShell scripters, including managers, ran scripts, and how their employees ran scripts written for them. To gather this information, […]
How I learned to love DialogResult
This post discusses the DialogResult property of buttons, which often confuses beginning PowerShell GUI app designers. When I first started learning how to write PowerShell GUI applications, I thought of the DialogResult property of buttons as the “evil property.” What else would I think? If the DialogResult property of a button is set to any […]
Where are v3 and v4? PowerShell Versions in PowerShell Studio
In this post, we explain why PowerShell Studio can run your scripts only the versions of Windows PowerShell that are installed on local and remote computers. If you’ve recently upgraded to Windows 10 from Windows 7, 8, or 8.1, you’ll notice quickly that you now have Windows PowerShell 5.0. Depending on your upgrade path and […]
Output from a Script in an Executable File
This is the fourth blog in a multi-part series about designing a Windows PowerShell script that will be packaged in an executable file. Passing Parameters to a Script in an Executable File explains how to use the special parsing features of PowerShell Studio and PrimalScript to make passing parameters easy for PowerShell users and authors. […]
Displaying Help for a Script in an Executable File
This is the third blog in a multi-part series about designing a Windows PowerShell scripts that will be packaged in an executable file. Passing Parameters to a Script in an Executable File explains how to use the special parsing features of PowerShell Studio and PrimalScript to make passing parameters easy for PowerShell users and authors. […]
Parsing Parameters for a Script in an Executable File
This is the second blog in a multi-part series about designing a Windows PowerShell script that will be packaged in an executable file. Passing Parameters to a Script in an Executable File explains how to use the special parsing features of PowerShell Studio and PrimalScript to make passing parameters easy for PowerShell users and authors. […]
Using Module-Qualified Cmdlet Names
Open-source projects and new methods of distributing modules, such as PowerShellGet and the PowerShell Gallery, have significantly increased the availability of Windows PowerShell modules. While we once relied on modules from Microsoft, we now can select from hundreds of new modules developed in the community. The upside of having so many modules is vastly increased […]
