Downloads:

1,599

Downloads of v 2.3:

673

Last Update:

26 Jun 2015

Package Maintainer(s):

Software Author(s):

  • Anurag Saini

Tags:

admin tools environment portable

Path-Manager

2.3 | Updated: 26 Jun 2015

Downloads:

1,599

Downloads of v 2.3:

673

Maintainer(s):

Software Author(s):

  • Anurag Saini

Path-Manager 2.3

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Path-Manager, run the following command from the command line or from PowerShell:

>

To upgrade Path-Manager, run the following command from the command line or from PowerShell:

>

To uninstall Path-Manager, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade path-manager -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade path-manager -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure path-manager installed
  win_chocolatey:
    name: path-manager
    state: present
    version: 2.3
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'path-manager' do
  action    :install
  version  '2.3'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: path-manager,
    Version: 2.3,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller path-manager
{
   Name     = 'path-manager'
   Ensure   = 'Present'
   Version  = '2.3'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'path-manager':
  provider => 'chocolatey',
  ensure   => '2.3',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install path-manager version="2.3" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator ferventcoder on 26 Dec 2015.

Description

Path-Manager is a small utility for easy management of environment variables. It can add/modify/remove variables and can also save their values for backup.

Features

  • Separately view all System and User environment variables
  • Clear and splitted view of entries
  • Options to check for invalid entries
  • Import/Export support for entire environment setting

Maintainer's note

path-manager appears to be a recoded derivative of pathmanager


tools\chocolateyInstall.ps1
$packageName = 'path-manager'
$url = 'http://sourceforge.net/projects/pathtool/files/Executable/Path%20Manager_2.3.exe/download'
$checksum = '3573d956fb899c2d7f143f422cb49fc276cb33f4'
$checksumType = 'sha1'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$installFile = Join-Path $toolsDir "$($packageName).exe"
Get-ChocolateyWebFile -PackageName "$packageName" `
                      -FileFullPath "$installFile" `
                      -Url "$url" `
                      -Checksum "$checksum" `
                      -ChecksumType "$checksumType"
# create empty sidecar so shimgen creates shim for GUI rather than console
$shimGui = $installFile + ".gui"
Set-Content -Path $shimGui `
            -Value $null

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Path-Manager 2.2 206 Friday, June 26, 2015 Approved
Path-Manager 2.1 239 Friday, June 26, 2015 Approved
Path-Manager 2.0 261 Friday, June 26, 2015 Approved
Path-Manager 1.0 220 Friday, June 26, 2015 Approved

First version (v1.0) was developed with Visual Studio 2012 Express (C#, .NET 4.5)
Second version (v2.0) is developed with Lazarus IDE v1.0.8 (Pascal)
That means, from version 2.0 Path Manager is a native windows application and it no longer needs .NET framework.

This change also resulted in increased size of executable however increase in performance and speed is significant. New executable of version 2.0 is compressed with upx.

Overview of changes (v2.3):

  • Fixed problem of exception on startup
  • Added function to notify all windows that the environment variables have changed

Overview of changes (v2.2):

  • Removed shortcuts for refresh and about (were causing problem in Windows XP)
  • Added Popup-Menu for variable-list and value-list
  • Restart As Admin button now invisible when Path-Manager is run as admin
  • It seemes that environment change message in not broadcast to applications, as for now, I am looking for some proper solution. For the meantime restarting explorer.exe should do the job.

Overview of changes (v2.1):

  • Support for non-admin users
  • Fixed splitter position bug
  • Refresh environment data without relaunch

Overview of changes (v2.0):

  • Now a standalone application, no need of .NET framework
  • Reduced memory consumption
  • Takes much less time in saving changes

If you find any bugs in this program then please mail Anurag Saini.
If you find any issues with install/uninstall of this package please contact package maintainer.


This package has no dependencies.

Discussion for the Path-Manager Package

Ground Rules:

  • This discussion is only about Path-Manager and the Path-Manager package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Path-Manager, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus