PsGet - Automate Install of PowerShell Modulesīut what about PowerShell modules? PowerShell modules aren’t installed in the traditional sense, they are really copied to a folder in the user’s PowerShell Modules directory.Įnter PsGet. So the install of something like Java is reduced to something like: This gives the consumer the ability to script the install of software and not just development artifacts. This leads us to… Chocolatey - Software as Packagesīuilt upon NuGet, chocolatey takes the concept of packages and applies it to software installs. NuGet out of the box is great, but it is really meant for managing development dependencies and requires some extra extension to manage software. The ability to resolve packages solves the issue of managing PowerShell dependencies. If the package has dependencies, those dependencies are downloaded automatically when the package is resolved. NuGet allows for an application to set a dependency on a released package.

The Solutions NuGet - Dependency Management Windows Management Framework v5.0 is currently in Preview and has package management capabilities that I can’t use because they are not production ready. I would like to give the Operations team a one liner that they can use to install the latest package dependencies and not have to worry about digging around on google to find out how to install the module.

If a module has a dependency, it should automatically download that dependency. I would also like to benefit from package management and not need to copy folders and files around in order to get reuse out of my modules.

I have a few PowerShell modules that I work with that I’d like to distribute internally but I don’t want to manually copy the modules into the PowerShell modules folders. Creating Reusable PowerShell Modules with PsGet and ChocolateyĪs automation becomes more popular, teams need a way to organize scripts in source control and ultimately deliver those scripts to a runtime environment in a consistent and repeatable way.

Chocolatey powershell