Skip to content

PSProfile v0.6.0
Compare
Choose a tag to compare
@scrthq scrthq released this 02 Nov 17:11
v0.6.0
21487ea
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Changelog

0.6.0 - 2019-11-02

  • Issue #21 - Thank you @corbob!
    • Fixed: Project folder discovery logic to ensure that project folders with the same name are added to the dictionary without conflict.
  • Issue #22 - Thank you @corbob!
    • Added: WithInsiders switch parameter to Open-Code, Edit-PSProfilePrompt, and Edit-PSProfileInitScript.
  • Issue #23
    • Fixed: $PSProfile variable should exist regardless of when you import the module (removed conditional variable setting from PSM1).
  • Issue #26
    • Fixed: $PSProfile._globalize() internal method will now update $PSDefaultParameterValue to $global":PSDefaultParameterValue on InitScripts / ExternalScripts / etc so $PSDefaultParameterValue persists in the main session as intended.
  • Issue #27
    • Removed: Set-Prompt alias to prevent conflict with oh-my-posh module.
  • Issue #29
    • Fixed: Secrets now persist across refreshes and sessions as intended. Details:
      • Removed PSProfileVault class, replaced with pure hashtable.
      • Updated the Secrets management functions to work directly against the Vault hashtable.
  • Issue #31

Instructions

IMPORTANT: You MUST have the following modules installed as a prerequisite to using this module, otherwise the module will fail to import! Installing the module from the repo source or the release page does not automatically install dependencies!!

Module Dependencies:

  1. Click here to download the PSProfile.zip file attached to the release.
  2. If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.

    This is to prevent having to unblock each file individually after unzipping.

  3. Unzip the archive.
  4. (Optional) Place the module folder somewhere in your PSModulePath.

    You can view the paths listed by running the environment variable $env:PSModulePath

  5. Import the module, using the full path to the PSD1 file in place of PSProfile if the unzipped module folder is not in your PSModulePath: 
    # In $env:PSModulePath
Import-Module PSProfile

# Otherwise, provide the path to the manifest:
Import-Module -Path C:\MyPSModules\PSProfile\\PSProfile.psd1
Assets 3
Loading