Chocolatey Package: MultiMonitorTool

Install

Install Chocolatey, and run the following command to install the latest approved stable version from the Chocolatey Community Repository:

choco install multimonitortool --source="'https://community.chocolatey.org/api/v2'"

Alternatively, the packages as published on the Chocolatey Community Repository (starting with v1.96) will also be mirrored on this repository's Releases page. The nupkg can be installed from the current directory as follows:

choco install multimonitortool --source="'.'"

Build

Install Chocolatey, and the Chocolatey Automatic Package Updater Module, then clone this repository.

Once cloned, simply run build.ps1. The ZIP archives are intentionally untracked to avoid bloating the repository, so the script will download the MultiMonitorTool portable ZIP archives from the mirror created by this package (to ensure reproducibility in case of an older version), then packs everything together.

A successful build will create multimonitortool.x.y.nupkg, where x.y should be the Nuspec's version value at build time.

Note that Chocolatey package builds are non-deterministic. Consequently, an independently built package will fail a checksum validation against officially published packages.

Update

This package should be automatically updated by the Chocolatey Automatic Package Updater Module. If it is outdated by more than a few days, please open an issue.

AU expects the parent directory that contains this repository to share a name with the Nuspec (multimonitortool). Your local repository should therefore be cloned accordingly:

git clone git@github.com:brogers5/chocolatey-package-multimonitortool.git multimonitortool

Alternatively, a junction point can be created that points to the local repository (preferably within a repository adopting the AU packages template):

mklink /J multimonitortool ..\chocolatey-package-multimonitortool

Once created, simply run update.ps1 from within the created directory/junction point. Assuming all goes well, all relevant files should change to reflect the latest version available. This will also build a new package version using the modified files.

Before submitting a pull request, please test the package using the Chocolatey Testing Environment first.