As you've seen, PowerShell modules are an
appealing way for authors of code to
deliver their commands to users, such as
yourself, and they make it really easy to
consume and work with. You saw that a
PowerShell module, in its most simple
form, is really just a set of commands
packaged up as one entity, and all
commands inside of that module are
typically related to working with a single
platform, system, or service. You're now
aware of the PSModulePath and its
importance when working with PowerShell
modules. If you only take one thing away
from this module, it should be that the
paths in the PSModulePath variable are
where modules are located by default, and
you get benefits from storing modules
here, such as the ease of importing and
auto‑loading. Speaking of importing, you
also explored how to import PowerShell
modules into the current session, both by
using a name and a path to a module, and
then saw firsthand how the auto‑import
works. The commands inside of a module are
what you'll end up running both
interactively and inside any scripts that
you build, and you worked with several
methods for identifying and filtering
which commands are included inside of the
module. With that said, we aren't stopping
there. Coming up in the next and final
module of this course, you'll learn how to
manage PowerShell modules, including
installing new modules from the PowerShell
Gallery, to make many, many more commands
available to you right at your fingertips.
You'll learn about updating, removing, and
uninstalling modules, and in the theory
component of the module, you'll understand
the concepts around package managers and
repositories. It's going to be a lot of
fun, and it builds a lot on the concepts
you've just learned in this module. I hope to see you there.