As I previously mentioned a little over a month ago in my blog article PowerShell Script Module Design Philosophy, I'm transitioning my module build process to a non-monolithic design in development and a monolithic design for production to take advantage of the best of both worlds. Be sure to read the previously …
Read More

This week, I'll continue where I left off in my previous blog article PowerShell Script Module Design Philosophy.

Moving forward, the development versions of my PowerShell script modules will use a non-monolithic design where each function is dot-sourced from the PSM1 file. When I move them to production, I'll convert …

Read More

Years ago, when I first learned how to create PowerShell script modules, I built them with all the functions in one huge monolithic PSM1 file. I like the monolithic script module design from a performance and security standpoint along with the ease of signing fewer files if you’re taking advantage of code signing to …
Read More

Using asterisks (*) in your module manifest is a bad idea no matter how you look at it. First, your module will be slower because it will have to figure out what to export. More importantly, if you use a "#Requires -Modules" statement in your functions and they're in separate PS1 files, all of the specified …
Read More

I recently began updating my PowerShell script module build process. Updating my Plaster template was one of the first things I needed to do. If you haven't already read my blog article about Using Plaster to create a PowerShell Script Module template, I'd recommend beginning there as this blog article assumes you …
Read More

There's been a lot of debate about script module design as of lately and instead of tweeting something out asking for responses, I thought I would post it here via a blog article.

Back when I first started creating PowerShell script modules, I placed all of my functions in the PSM1 file and later started placing each …

Read More