PowerShell Aliasing

Additional filtering is possible on multiple criteria, like the -Definition or -Name of the alias. Both
parameters support wildcards, which allows you to, for example, find any alias for Get- commandlets.

Therefore, we want to define our aliases in the profile file. If you want to learn how that works, read the article in MS Documentation.

Inside your profile you can use the same command to create your aliases as in your interactive session.

To get the aliases you may have already created in your session you can just filter your history.

If you want some inspirations on common aliases I collected, check out my personal profile I recently open sourced.

For example, this will not work. There will be no error on creation, but running it PowerShell will not be able to locate the commandlet.

There is a way to work around this, however it is quite limited, as it removes the capability to tab complete or even use any of the other parameters the aliased commandlet can provide.

Unfortunately I am not aware of a way to solve this limitation, if you are, please reach out to me, and I am happy to add it for anyone else interested.

Addendum: Shortly after this article was released, ScriptRunner’s very own Achim Wieser provided one possible solution for this issue, which contains the use of an advanced function as a wrapper.

You can find a more detailed description of his approach on Marco Kamners Blog.

Or even worse, there could be a different command behind the alias, breaking the whole script or altering its effects.

Working in VSCode using aliases will, by default, be shown as a warning and the default ms-vscode.powershell extensions even provides an automated way of resolving any alias in your code by opening the command bar and typing PowerShell: Expand Alias.