Contents

PowerShell Profiles - The profile.ps1 file

Contents

Welcome to this blog series about PowerShell profiles. I’m using PowerShell profiles for a couple of months now to make life a lot easier. To start this blog series, I would like to show you my Profile.ps1 file. It’s located in “C:\Users\\Documents\WindowsPowerShell”. Because I use my PowerShell profiles at multiple locations such as my work notebook, home computer and sometimes at projects, I need to make sure that my PowerShell script home is always right so that the rest of the PowerShell profile is able to load successfully. That’s why I have these commands at the beginning of my profile: [code language="PowerShell”] # Set the Home Directory for Powershell to start in $ScriptHomeOneDrive = “$Home\OneDrive\Scripts” $ScriptHomeDocuments = “$Home\Documents\Scripts” $ScriptHomeMyDocuments = “$Home\My Documents\Scripts” if((Test-Path -Path $ScriptHomeOneDrive )) { $ENV:ScriptHome = $ScriptHomeOneDrive } Elseif((Test-Path -Path $ScriptHomeDocuments )) { $ENV:ScriptHome = $ScriptHomeDocuments } Else { $ENV:ScriptHome = $ScriptHomeMyDocuments } Set-Location $ENV:ScriptHome [/code] Because I’m using OneDrive as my script repository, I need to make sure that the script start in my OneDrive\Scripts directory. When I have access to a computer or server without OneDrive, I need to use the Documents folderĀ as my script home. On some servers, the “Documents” folder is named as “My Documents”, so that’s why I use that folder too. [code language="PowerShell”] # Load the base functions . .\Startup\_PSH_BASE.ps1 [/code] The above code will load my base file which is located in my OneDrive folder or in my Documents folder. Now I can use my OneDrive folder to sync all my scripts between multiple computers and make changes to the profile from every device. Make sure you sign those PowerShell Profile Scripts, so that you know that it’s not changed! In my next post, I’ll show the structure of my _PSH_BASE.ps1 file and other files that are part of my PowerShell profile.