PowerShell

If you have a few minutes, I would like you to check out The PowerShell News Podcast. The Podcast is hosted by two Microsoft MVPs, Mick Pletcher and Harjit Dhaliwal. They have several episodes posted that cover a good range of PowerShell topics.

I met with Mick in person on his travels back from the MVP Summit and we connected with Harjit remotely for their latest episode, Episode 6 - Interview with Kevin Marquette from the SoCal PowerShell User Group. We talked about the SoCal PowerShell User Group, the great team that I work with at loanDepot, and a bit about my contributions to the PowerShell community.

I look forward to listening to their future episodes and connecting with them again in the future.

I touched base on the idea of Using a NuGet server for a PSRepository a few days ago. This is the ideal way to distribute modules to other systems. This can include community modules. Today, I am going to cover the process that I use to republish modules from the PSGallery to an internal PSRepository.

In my post talking about Your first internal PSScript repository, I used a network share to show how easy it is to get started. I am going to take that idea to the next step and publish a module to a NuGet server. This is how we manage our modules internally.

As your library of scripts and automation grows, everything you do will start to depend on your common datasets. Datasets like your user information or server details. Just think about how many scripts and tools you already have that either get a list of servers or you provide it a list of servers. It may be time for you to create a common interface to your data.

I just released another major update to PSGraph. This release includes new keywords and helps unlock more features of Graphviz. These features will make it easier to build entity and data model diagrams.

For a period of time, Windows Defender was flagging several important PowerShell modules as infected with Peasecto.A. This would prevent users from running or installing those modules. Some of the impacted modules included PackageManagement, MSOnline, PSScriptAnalyzer, and VMware.PowerCLI. Even VSCode was feeling the pain. The good news is that the issue is resolved for some modules now.

I just saw the PowerShell team post an update on the future of Desired State Configuration (DSC). This is the first real update after the release of PowerShell Core 6.0. Without DSC support in PowerShell Core, there have been a lot of questions in the community. I want to take a moment to share my thoughts on what the PowerShell Team had to say.

Like many other languages, PowerShell has commands for controlling the flow of execution within your scripts. One of those statement is the switch statement and in PowerShell, it offers features that are not found in other languages. Today we will take a deep dive into working with the PowerShell switch.

Over on /r/PowerShell, we share with each other things that we have done with PowerShell every month and reflect on that at the end of the year. As I look back on my year in PowerShell, I see that I have accomplished quite a bit. Not only have I done great work in a professional setting but I have also done a lot for the PowerShell community this year.

The pwsh.exe process is the new name for PowerShell Core starting with version 6.0. The executable changed names from powershell.exe to pwsh.exe. Let’s take a look at this executable.

I have been presenting my PSGraph module to a few Powershell user groups. One thing I do in my demos is use local system information to generate graphs. Things like network connections and process relationships. Some of them have turned out to be quite useful. So I have started compiling them into a new module called PSGraphPlus.

One of the commands that I find myself running all the time from this module is Show-GitGraph. I spent today working on it and I would like to share my progress.

Have you ever noticed that some people use StringBuilder in their PowerShell scripts and wondered why? The whole point of using StringBuilder is to concatenate or build large strings. There are ways to do this in PowerShell already, so why would someone turn to this DotNet object?

Every once in a while, I see someone ask for a way to track changes to something. It reminds me of a script I wrote once to track changes made in Active Directory. Twice a day, my team was emailed with a report showing all the user account, group membership, and group policies that were changed. It turned out to be a valuable tool in giving everyone visibility to the changes that were recently made.

I’m reminded of that script because I handled that scenario in a very generic way that could be applied to many other things that you would want to monitor.

When I set out to write PSGraph, it started as a way to just write GraphViz instructions in PowerShell. The structure and syntax of GraphViz heavily influenced how I build the commands in PSGraph. This release polishes some of those commands and starts to work on doing more than just translating command. My focus of 1.2 was to make subgraphs easier to work with.

I am just getting started on a new module PSGraphPlus and if you know me, this is when I take a look at how I build modules. I fleshed out a lot of little bugs with my Full Module Plaster Template and I spent a little time working on my module build script. I may talk about that build process in another post but for the sake of this conversation, it is just a script that I run that performs several actions on my module. It runs tests, bumps the version and publishes to the PSGallery.

Today, I am going to walk you through how I bump that version based on changes in my module.