Steve Lee

Principal Software Engineer Manager, PowerShell

Principal Software Engineer Manager PowerShell 7, PowerShellGet, PSScriptAnalyzer, VSCode-PowerShell extension, PowerShellEditorServices, etc...

Post by this author

Parsing Text with PowerShell (3/3)

This is the third and final post in a three-part series. In the previous posts, we looked at the different operators what are available to us in PowerShell. When analyzing crashes at DICE, I noticed that some of the C++ runtime binaries where missing debug symbols. They should be ...

Parsing Text with PowerShell (2/3)

This is the second post in a three-part series. The operator The operator splits one or more strings into substrings. The first example is a name-value pattern, which is a common parsing task. Note the usage of the Max-substrings parameter to the operator. We want to ensure that it ...

Parsing Text with PowerShell (1/3)

This is the first post in a three part series. A task that appears regularly in my workflow is text parsing. It may be about getting a token from a single line of text or about turning the text output of native tools into structured objects so I can leverage the power of PowerShell. I ...

Announcing General Availability of the Windows Compatibility Module 1.0.0

The Windows Compatibility module () is a PowerShell module that lets PowerShell Core 6 scripts access Windows PowerShell modules that are not yet natively available on PowerShell Core. (Note: the list of unavailable commands is getting smaller with each new release of PowerShell Core. This module is just for things aren't natively supported ...

PowerShell Standard Library: Build single module that works across Windows PowerShell and PowerShell Core

This is the first of a series of blog posts that will help you take advantage of a new NuGet package PowerShellStandard Library 5.1.0. This package allows developers to create modules that are portable between Windows PowerShell 5.1 and PowerShell Core 6.0. This means that you can create PowerShell modules that run on Windows, Linux, and ...

Increased Windows Modules coverage with PowerShell Core 6.1

During the May 2018 Community Call and a tweet a few weeks later, we mentioned that PowerShell team was spending significant time in the Windows codebase. We even demoed using the Active Directory PowerShell Module from PowerShell Core 6 during the PowerShell Community Call. We started investigating some of the top requested modules ...

PowerShell Core 6.1 Roadmap

The release of PowerShell Core 6.0 is only the beginning and we are already thinking about the next leg of our journey. Most of the effort of the team with PowerShell Core 6.0 was in these areas: The community did some amazing work to add new capabilities in both the engine as well as cmdlets! If you participated in the ...

PowerShell Core 6 Release Candidate

PowerShell Core 6 Release Candidate Last year, we announced that PowerShell was not only Open Source, but also cross platform.  The finish line is in sight and we recently published the Release Candidate for PowerShell Core 6! PowerShell Team ♥ Community It has been an amazing experience for the team working with the community on ...

PowerShell Core 6 Beta.1 Release

Approximately 9 months ago, we announced PowerShell Core 6 on GitHub being not only Open Source, but also cross platform. Today, I'm proud to announce we are moving out of alpha and into beta! We realize that moving a technology that started in Windows to Linux has to fit in properly to be accepted and provide a great experience across all ...

Using PowerShell Modules in Azure Functions

Previously, I blogged about how I created PowerShell GitHub Dashboard using Azure Functions to run a PowerShell script and didn't use PowerShell Modules as I didn't find an easy way to do it with Azure Functions.  Stefan informed me that you can easily do it using FTP!  Today, I'm publishing a guest blog post that Stefan authored that ...