Chris Gardner

That's a fair point, we're doing a lot with dev and test labs where as much as possible is broken down into reusable building blocks that are split up by...

I much prefer to have my tests in a separate folder to my functions, it keeps things contained in a more logical structure and allows me to just ship out...

Use the RequiredModules section of the psd1 file and then PowerShellGet will handle the rest for you.

I'm becoming more of a fan of using a build script to pull all the function files into a single psm1 that you bundle with a Psd1 and publish just...

I use the same script for dev builds as for the CI pipeline build, it makes sure my build process is always the same no matter where I run it....

The basic script I use is this. It's a little hard coded at the end for figuring out which functions to make public (assumes Verb-Noun) but I'd only want to...

> Wouldn’t debugging and breakpoints be an issue if the functions are copied to the psm1? It's not really, you either run the build script once and then set the...

Another case of the building a single psm1 instead of dot sourcing all the ps1 files is PowerShellGet who went through this a little while ago (after having a monolithic...

The big reasons for discouraging aliases is readability and maintainability. You can't guarantee anyone coming along later will know what a particular alias means and that will act as a...

You can set up some style rules in the VSCode preferences, either at the user or workspace level, and set it to format on save or paste (or change?). This...