Downloads:

243,320

Downloads of v 0.0.4:

58,326

Last Update:

09 Nov 2016

Package Maintainer(s):

Software Author(s):

  • Miodrag Milic

Tags:

choco-extension

Chocolatey Extensions by majkinetor

This is not the latest version of Chocolatey Extensions by majkinetor available.

  • 1
  • 2
  • 3

0.0.4 | Updated: 09 Nov 2016

Downloads:

243,320

Downloads of v 0.0.4:

58,326

Maintainer(s):

Software Author(s):

  • Miodrag Milic

  • 1
  • 2
  • 3
Chocolatey Extensions by majkinetor 0.0.4

This is not the latest version of Chocolatey Extensions by majkinetor available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Pending


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

To install Chocolatey Extensions by majkinetor, run the following command from the command line or from PowerShell:

>

To upgrade Chocolatey Extensions by majkinetor, run the following command from the command line or from PowerShell:

>

To uninstall Chocolatey Extensions by majkinetor, 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://community.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://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade mm-choco.extension -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 mm-choco.extension -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 mm-choco.extension installed
  win_chocolatey:
    name: mm-choco.extension
    state: present
    version: 0.0.4
    source: STEP 3 URL

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


chocolatey_package 'mm-choco.extension' do
  action    :install
  version  '0.0.4'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: mm-choco.extension,
    Version: 0.0.4,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller mm-choco.extension
{
   Name     = 'mm-choco.extension'
   Ensure   = 'Present'
   Version  = '0.0.4'
   Source   = 'STEP 3 URL'
}

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


package { 'mm-choco.extension':
  provider => 'chocolatey',
  ensure   => '0.0.4',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install mm-choco.extension version="0.0.4" 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.

This package was approved by moderator gep13 on 09 Nov 2016.

Description

Package contains a helper functions installed as Chocolatey extensions


extensions\Get-AppInstallLocation.psm1
<#
    Last Change: 12-Aug-2016.
    Author: M. Milic <[email protected]>

.SYNOPSIS
    Get application install location

.DESCRIPTION
    Function tries to find install location in multiple places. It returns $null if all fail. The following
    locations are tried:
      - local and machine (x32 & x64) various Uninstall keys
      - x32 & x64 Program Files up to the 2nd level of depth
      - native commands available via PATH
      - locale and machine registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths

.EXAMPLE
    Get-AppInstallLocation choco

    Return the install location of the application 'choco'.
.OUTPUTS
    [String] or $null
#>
function Get-AppInstallLocation {
    [CmdletBinding()]
    param(
        # Regular expression pattern
        [ValidateNotNullOrEmpty()]
        [string] $AppNamePattern
    )

    function strip($path) { if ($path.EndsWith('\')) { return $path -replace '.$' } else { $path } }

    $ErrorActionPreference = "SilentlyContinue"

    Write-Verbose "Trying local and machine (x32 & x64) Uninstall keys"
    [array] $key = Get-UninstallRegistryKey $AppNamePattern
    if ($key.Count -eq 1) {
        Write-Verbose "Trying Uninstall key property 'InstallLocation'"
        $location = $key.InstallLocation
        if ($location -and (Test-Path $location))  { return strip $location }

        Write-Verbose "Trying Uninstall key property 'UninstallString'"
        $location = $key.UninstallString.Replace('"', '')
        if ($location) { $location = Split-Path $location }
        if ($location -and (Test-Path $location))  { return strip $location }

        Write-Verbose "Trying Uninstall key property 'DisplayIcon'"
        $location = $key.DisplayIcon
        if ($location) { $location = Split-Path $location }
        if ($location -and (Test-Path $location))  { return strip $location }
    } else { Write-Verbose "Found $($key.Count) keys, aborting this method" }

    $dirs = $Env:ProgramFiles, "$Env:ProgramFiles\*\*"
    if (Get-ProcessorBits 64) { $dirs += ${ENV:ProgramFiles(x86)}, "${ENV:ProgramFiles(x86)}\*\*" }
    Write-Verbose "Trying Program Files with 2 levels depth: $dirs"
    $location = (ls $dirs | ? {$_.PsIsContainer}) -match $AppNamePattern | select -First 1 | % {$_.FullName}
    if ($location -and (Test-Path $location))  { return strip $location }

    Write-Verbose "Trying native commands on PATH"
    $location = (Get-Command -CommandType Application) -match $AppNamePattern | select -First 1 | % { Split-Path $_.Source }
    if ($location -and (Test-Path $location))  { return strip $location }

    $appPaths =  "\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths"
    Write-Verbose "Trying Registry: $appPaths"
    $location = (ls "HKCU:\$appPaths", "HKLM:\$appPaths") -match $AppNamePattern | select -First 1
    if ($location) { $location = Split-Path $location }
    if ($location -and (Test-Path $location))  { return strip $location }

    Write-Verbose "No location found"
}
extensions\Get-PackageParameters.psm1
<#
    Last Change: 09-Nov-2016.
    Author: M. Milic <[email protected]>

.SYNOPSIS
    Parses parameters of the package

.EXAMPLE
    Get-PackageParameters "/Shortcut /InstallDir:'c:\program files\xyz' /NoStartup" | set r
    if ($r.Shortcut) {... }
    Write-Host $r.InstallDir

.OUTPUTS
    [HashTable]
#>
function Get-PackageParameters([string] $Parameters = $Env:ChocolateyPackageParameters) {
    $res = @{}
    $re = "\/([a-zA-Z]+)(:([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)?"
    $results = $Parameters | sls $re -AllMatches | % Matches
    foreach ($m in $results) {
        $a = $m.Value -split ':'
        $opt = $a[0].Substring(1); $val = $a[1..100]
        if ($val -match '^(".+")|(''.+'')$') {$val = $val -replace '^.|.$'}
        $res[ $opt ] = if ($val) { $val } else { $true }
    }
    $res
}
extensions\Register-Application.psm1
<#
    Last Change: 08-Nov-2016.
    Author: M. Milic <[email protected]>

.SYNOPSIS
    Register application in the system

.EXAMPLE
    Register-Application 'c:\windows\notepad.exe'

    Register application using name derived from its file name. Test via Win + R dialog.

.EXAMPLE
    Register-Application 'c:\windows\notepad.exe' -Name ntp

    Register application using explicit name.

.NOTES
    See topic 'Application Registration' at https://msdn.microsoft.com/en-us/library/windows/desktop/ee872121(v=vs.85).aspx
#>

function Register-Application{
    [CmdletBinding()]
    param(
        # Full path of the executable to register
        [Parameter(Mandatory=$true)]
        [string]$ExePath,
        [string]$Name,
        # Register application only for the current user. By default registration is for the machine
        [switch]$User
    )

    if (!(Test-Path $ExePath)) { throw "Path doesn't exist: $ExePath" }
    if (!$Name) { $Name = Split-Path $ExePath -Leaf } else { $Name = $Name + '.exe' }

    $appPathKey = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\$Name"
    if ($User) { $appPathKey = "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\$Name" }

    If (!(Test-Path $AppPathKey)) { New-Item "$AppPathKey" | Out-Null }
    Set-ItemProperty -Path $AppPathKey -Name "(Default)" -Value $ExePath
}

Log in or click on link to see number of positives.

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
Chocolatey Extensions by majkinetor 0.0.4 58326 Wednesday, November 9, 2016 Approved

  • 0.0.4
    • Get-PackageParameters
    • Register-Application new parameter Name
  • 0.0.3
    • Bugfix Get-AppInstallLocation on x32 systems
    • Register-Application added
  • 0.0.2
    • Now works with bad registry keys.
  • 0.0.1
    • Get-AppInstallLocation implementation.

This package has no dependencies.

Discussion for the Chocolatey Extensions by majkinetor Package

Ground Rules:

  • This discussion is only about Chocolatey Extensions by majkinetor and the Chocolatey Extensions by majkinetor 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 Chocolatey Extensions by majkinetor, 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