major language except for PowerShell. If you're interested in publishing AWS Lambda functions, by using a PowerShell container image, add your voice to this GitHub issue report. One of the AWS developers has responded and expressed interest in prioritizing, but we need to show interest / demand for this feature.

PowerShell scripts and modules. That tool is called the PowerShell Integrated Scripting Editor (ISE), which was originally included out-of-box with Windows 7 and PowerShell version 2.0. Over the years, PowerShell developers have used tools like Quest PowerGUI and Visual Studio with the PowerShell Tools Extension to write, test, and debug their PowerShell code. In fact, not all that long ago, I wrote about moving from PowerGUI over to Visual Studio for your PowerShell development work. Since then, the momentum in the software field has gotten more and more agile, requiring developers to invest more and more time learning, and less time focusing on their business logic.

Visual Studio Code to debug your script modules. In this video, we'll build a simple PowerShell script module, and then use the Pester unit testing module to write some failing tests. Then, we'll set a breakpoint in our module and break into the debugger when we execute the Pester unit tests. Once execution is paused, we'll step through the module code line by line, to discover where things are going wrong. We'll then fix the module code, and ensure that our Pester unit tests are passing.

containers! Let's take a look at how this works.

clean up a folder with old log files on an hourly basis. Instead of using your operating system's task scheduler (ie. systemd on Linux, MacOS, or Windows Task Scheduler), you can use PowerShell to create a Timer.

Studio Code for PowerShell development work. It doesn't matter if you're using Linux, Mac, or Windows, you can be productive as a PowerShell developer on any development platform!