One command you will use quite a bit in PowerShell is called Get‑Command.
Now, nothing mysterious in that name.
This cmdlet does one thing, which is reflected in the name, get
me the commands in my PowerShell session.
Now, if you run Get‑Command with no parameters,
you'll see everything that PowerShell knows about.
Or, you can use wildcards with the name of the thing you'd like to
manage. In this example, I'm asking PowerShell to get me all the
commands that have file somewhere in the name.
Now, you don't have to concern yourself at this point with the version
or source, just knowing the name is the key point.
By the way,
I should point out that technically you are using a parameter with Get‑Command.
The parameter, ‑Name, is positional, meaning you don't have to type it.
The *file* is technically that parameter value.
Get‑Command has a few other explicit parameters, such as the type of a
command. Type the parameter name, don't forget the dash followed by a space
and the values, in this case function and cmdlet.
Some commands have a way to auto complete possible values.
This is one of them.
After you hit the spacebar, after commandtype,
you can press the Tab key and PowerShell will cycle
through all the possible values.
You don't really have to memorize a lot of things in PowerShell, just
build up that muscle memory to use tab completion,
or at least give it a try.
It doesn't work all the time, but it doesn't hurt to try.
You can also limit your command search by the noun.
This requires that you type the ‑Noun parameter.
You can use wildcards around the noun name if you aren't sure, and
then find it from there based on the results that you get. And you
can do the same thing with ‑Verb, or combine them. I'll show you how when we get to the demo.