Pog v0.12.0

Full Changelog: v0.11.0...v0.12.0

• Exported commands and shortcuts are now automatically kept in sync. It is no longer necessary to call Export-Pog after updating to a new version, as long as no new exports were added since the last version.
• Package repository is now unified with package generator repository – each generated package stores the generator at .pog/generator.psd1 (see 038f946 for rationale).
• Added new package generator cmdlets to make generating packages from GitHub releases much easier.
• When overwriting an export, print the package that owned the previous export.
• Use a Pog-specific User-Agent for all network requests by default.
• Added Get-PogRepository cmdlet.
• Release .zip is now generated from the CI.
• Lot of bugfixes and error message improvements.

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run ./Pog/setup.cmd (or ./Pog/setup.ps1, if you're in PowerShell).

Pog v0.11.0

Full Changelog: v0.10.0...v0.11.0

• Added a very basic Update-Pog command which lists and updates all outdated packages.
• Added an automated update script for Pog itself (see README).
• Renamed multiple commands to make the names more consistent (noun for most commands is now either Pog or PogRepository).
• Install-Pog and Uninstall-Pog should now be a bit more resistant to tampering from Windows Defender.
• Export-Command and Export-Shortcut now correctly handle name casing changes.
• Lots of internal fixes and improvements.

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run Pog/setup.cmd.

Pog v0.10.0

Full Changelog: v0.9.2...v0.10.0

• Import-Pog can now show a diff against the previous imported version (-Diff).
• Uninstall-Pog now detects if the package directory is in use before attempting to remove it.
• Added support for using multiple package repositories in a stack (configure using Set-PogRepository).
• Lots of minor bugfixes and improvements.

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run Pog/setup.cmd.

Pog v0.9.2

Full Changelog: v0.9.1...v0.9.2

• Make OpenedFilesView optional. This speeds up the first-time setup and avoids a 3rd party dependency by default.
• Minor UI improvements.

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run Pog/setup.cmd.

Pog v0.9.1

Full Changelog: v0.9.0...v0.9.1

• Add support for running Pog from DOS drives created with subst.
• Add documentation for creating packages.
• Improve documentation for many cmdlets.

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run Pog/setup.cmd.

Pog v0.9.0

Full Changelog: v0.8.3...v0.9.0

• Add a shell.ps1 script to make it easier to use Pog without adding it to PATH and PSModulePath.
• When re-running setup.ps1 on a new machine, it prompts to automatically re-enable all packages.
• Simplify uninstallation by adding support for Disable-Pog Pog.
• Better error messages when Enable-Pog fails.

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run Pog/setup.cmd.

Pog v0.8.3

Full Changelog: v0.8.2...v0.8.3

• Add filtering for remote package version autocomplete. (huh, guess I forgot about that one)

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run Pog/setup.cmd.

Pog v0.8.2

Full Changelog: v0.8.1...v0.8.2

• Get-PogRepositoryPackage was renamed to Find-PogPackage.
• Added support for relative paths in data/package_roots.txt.
• A few smaller bugfixes, PowerShell sure is fun.

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run Pog/setup.cmd.

Pog v0.8.1

Full Changelog: v0.8.0...v0.8.1

• Better compatibility checks and error messages for symlinks.
• New Set-PogRepository cmdlet, which allows switching between package repositories on the fly.
• Better documentation using built-in PowerShell help system. Check man about_Pog.

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run Pog/setup.cmd.

Pog v0.8.0

Full Changelog: v0.7.2...v0.8.0

• Breaking change: More consistent configuration cmdlet naming: New-File, New-Directory, New-Symlink instead of Assert-File, Assert-Directory and Set-SymlinkedPath.
• Much smaller executable stub (150 kB vs 6 kB).
• Slight installation script improvements.
• Added a library to simplify authoring manifest generators.
• Wildcard support for package names in some cmdlets.
• Support for parallel manifest loading in Get-PogRepositoryPackage.

Installation

1. Ensure you have enabled developer mode. Pog currently needs it for symbolic links (hopefully I can get rid of that in a future release).
2. Download and unpack the archive to your preferred directory for portable applications.
3. Run Pog/setup.cmd.

Local repository support

To use a local package repository for development, use the following script to import the Pog PowerShell module:

$env:POG_LOCAL_REPOSITORY_PATH = "..."
Import-Module Pog