Have you been keeping an eye on the SAPIEN Information Center? If not, here are some articles you may have missed!
- Working with SemanticVersion in PowerShell
by June Blender, November 3, 2016
As the versions of Windows PowerShell and PowerShell (not only Windows!) proliferate, it becomes more important to know on which version of PowerShell your shared scripts and modules are running. Beginning in the open-source versions of PowerShell 6.0-alpha, the version object in $PSVersionTable.PSVersion switched from a System.Version object to a System.Management.Automation.SemanticVersion object.
- Requiring a Version of PowerShell
by June Blender, November 2, 2016
This article is taken from my Avoiding Version Chaos in a Multi-Version World talk, which I first delivered for the Mississippi PowerShell User Group in January 2016, but revised substantially to include PowerShell 6.0.0-alpha.
- Setting Parameter Attributes in PowerShell Help
by June Blender, November 1, 2016
Explains where the values of the parameter attributes originate and how to change them, including the little-known SupportsWildcards and PSDefaultValue attributes.
- Hidden Charms of PowerShell Studio – #2
by June Blender, October 2, 2016
To keep our scripting tools cutting-edge, we add features every day, driven by blitz-speed technology changes (open-source, cross-platform PowerShell!), a creative and experienced staff, and customer requests.
- Using Statement: Import PowerShell Classes from Modules
by June Blender, September 28, 2016
To import the classes defined in a module, you can’t use Import-Module or even #Requires -Module. Instead, use the Using statement, introduced in PowerShell 5.0, which imports the module, including its classes. The Using statement is not yet documented, so this is a bit confusing. Let’s examine it.
- Using the Return Keyword in PowerShell Classes
by June Blender, September 22, 2016
The Return keyword in PowerShell isn’t particularly well understood. It’s explained in about_Return, but it’s pretty obscure. And, to complicate matters, the Return keyword works very differently in PowerShell classes. This post describes how Return works in standard PowerShell and PowerShell classes.
- A Branded Image for a PowerShell GUI App
by June Blender, September 8, 2016
Even though we’re primarily scripters, we occasionally build applications with a graphic user interface (GUI). And, we want them to look nice. Specifically, we want them to look like we built them in 2016, not 1996.
- Get Release Notes
by June Blender, August 28, 2016
One of the best things about shared PowerShell scripts and modules is that they change a lot. The authors, the community, and development teams are continuously improving them. But, that creates a responsibility for users to discover changes and for development teams to help us do so.