When you develop PowerShell scripts that are required to run on machines other than your own, you should test if they can survive without your specific environment.
Your PowerShell profiles are such a dependency. Since you cannot always be sure what environment you will find on another machine, testing your scripts without your usual profile seems like a good idea.
Since PowerShell has multiple possible profiles, this can become just a tad cumbersome. PrimalScript 2009’s PowerShell Profile Manager can make this a bit easier.
You launch it from the SAPIEN Tools section in the PrimalScript’s Tools Browser.
Under Windows Vista, Windows 2008 Server and Windows 7, you will be presented with an elevation prompt. Since some of PowerShell’s profiles reside in system folders this is a required step.
The Profile Manager itself is a simple application, enabling you to enable or disable a specific profile, and, with the click of a button, load it into PrimalScript for editing.
Checking and un-checking the various profiles will simply rename the corresponding files and thereby prevent or enable loading.
It is important to note that any running shells, custom hosts etc. are not affected by these changes. You must restart them if you want your profile changes to apply.
1 comment on “PrimalScript 2009 includes PowerShell Profile Manager”
Comments are closed.