How to create permanent PowerShell Aliases

Question

I want to create an alias of a cmdlet that doesn't expire after I close the current session of Powershell, let's say I have this alias :

C:UsersAymen> New-Alias Goto Set-Location

This perfectly creates the Goto alias, but I want to use it even after I close the current session, how can I achieve that.

Note:

The PowerShell Help system suggests that I can export the aliases I create, and import them next time I open a new session, actually that's not really what I'm looking, for, is there a direct clear way to keep having a alias after I create it through different sessions

Answer 1

UPDATED - January 2021

It's possible to store in a profile.ps1 file any PowerShell code to be executed each time PowerShell starts. There are at least 6 different paths where to store the code depending on which user has to execute it. We will consider only 2 of them: the "all users" and the "only your user" paths (follow the previous link for further options).

To answer your question, you only have to create a profile.ps1 file containing the code you want to be executed, that is:

New-Alias Goto Set-Location

and save it in the proper path:

• "$HomeDocuments" (usually C:Users<yourname>Documents): only your user will execute the code. This is the recommended location You can quickly find your profile location by running echo $profile in PowerShell
• $PsHome (C:WindowsSystem32WindowsPowerShellv1.0): every user will execute this code

IMPORTANT: remember you need to restart your PowerShell instances to apply the changes.

TIPS

• If both paths contain a profile.ps1 file, the all-users one is executed first, then the user-specific one. This means the user-specific commands will overwrite variables in case of duplicates or conflicts.

• Always put the code in the user-specific profile if there is no need to extend its execution to every user. This is safer because you don't pollute other users' space (usually, you don't want to do that).
  Another advantage is that you don't need administrator rights to add the file to your user-space (you do for anything in C:WindowsSystem32).

• If you really need to execute the profile code for every user, mind that the $PsHome path is different for 32bit and 64bit instances of PowerShell. You should consider both environments if you want to always execute the profile code.

  The paths are:

  • C:WindowsSystem32WindowsPowerShellv1.0 for the 64bit environment
  • C:WindowsSysWow64WindowsPowerShellv1.0 for the 32bit one (Yeah I know, the folder naming is counterintuitive, but it's correct).