PowerShell Modules can be Painful

Building a PowerShell module should not be too hard. In fact, on the surface it’s pretty simple. Collect a bunch of functions, classes, enumerations, (whatever else you want), bundle them together and provide a wrapper in the form of a PSD1/PSM file. Building a module should be straightforward – and it is – except when you make dumb mistakes. Don’t make my mistakes.

Installing Utilities Folder with PowerShell

Just stashing this here in prep for a larger article. As written the above will install the utilities in C:\UTILS. However, some workstations may block these types of installs. In that event, I’ve added a flag ($IsMachine) which can be flipped to False and install in the current user’s profile.

Installing the Latest Notepad++ with PowerShell

I just needed a place to stash this and my GitHub didn’t seem appropriate. I make no guarantees that this will work and it’s only been tested on one system so far. I added the -Unique flag to the end of the download URL detection as indicated in a below message. (Again, nice catch!)

A Reflection on Stan Lee

As I write this, I’m currently in the hotel room preparing for a SolarWinds User Group in Frankfurt, Germany. I heard the news about Stan Lee’s passing at the dinner table surrounded by coworkers and friends when in London and got to thinking about how a single person can have such a large impact. I think that we all would like to feel like we can have a similar impact.

Read more