Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More
Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More
Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More
Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

14,550

Downloads of v 15.50.0200:

836

Last Update:

15 Aug 2015

Package Maintainer(s):

Software Author(s):

  • Donald Lessau

Tags:

file-manager file-management dual-panel explorer

XYplorer

This is not the latest version of XYplorer available.

  • 1
  • 2
  • 3

15.50.0200 | Updated: 15 Aug 2015

Downloads:

14,550

Downloads of v 15.50.0200:

836

Maintainer(s):

Software Author(s):

  • Donald Lessau

Tags:

file-manager file-management dual-panel explorer

XYplorer 15.50.0200

This is not the latest version of XYplorer available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks
Hide Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install XYplorer, run the following command from the command line or from PowerShell:

>

To upgrade XYplorer, run the following command from the command line or from PowerShell:

>

To uninstall XYplorer, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

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

1. Enter Your Internal Repository Url

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

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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. Copy Your Script

choco upgrade xyplorer -y --source="'INTERNAL REPO URL'" --version="'15.50.0200'" [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 xyplorer -y --source="'INTERNAL REPO URL'" --version="'15.50.0200'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install xyplorer
  win_chocolatey:
    name: xyplorer
    version: '15.50.0200'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'xyplorer' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '15.50.0200'
end

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


cChocoPackageInstaller xyplorer
{
    Name     = "xyplorer"
    Version  = "15.50.0200"
    Source   = "INTERNAL REPO URL"
}

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


package { 'xyplorer':
  ensure   => '15.50.0200',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

NOTE

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

Package Approved

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

Description

XYplorer is a file manager for Windows. It features tabbed browsing, a powerful file search, a versatile preview, a highly customizable interface, optional dual pane, and a large array of unique ways to efficiently
automate frequently recurring tasks. It's fast and light, it's innovative, and it's portable.

This is a commercial product, with a 30 day trial. For pricing go to: http://www.xyplorer.com/#buy

Please Note: This is an automatically updated package. If you find it is out of date by more than a day or two, please contact the maintainer(s) and let them know the package is no longer updating correctly.

tools\chocolateyInstall.ps1 
$packageName    = "xyplorer"
$installerType  = "EXE"
$packageVersion = "15.50.0200"
$url            = "http://www.xyplorer.com/download/xyplorer_full.zip"
$silentArgs     = "/S"
$validExitCodes = @(0)

#extract filename from source URL 
$filename       = $url.Substring($url.LastIndexOf("/") + 1)

#establish temp folder path
$tempPath       = $env:temp,"chocolatey",$packageName -join "\"

#establish full path to local copy of downloaded zip file
$pathToZip      = ($tempPath,$filename -join "\")




try { 

  # download zip package
  Get-ChocolateyWebFile "$packageName" $pathToZip "$url"

  # extract it
  Get-ChocolateyUnzip $pathToZip $tempPath

  # establish path to extracted installer (exe)
  $pathToExe =  Join-Path $tempPath (get-childitem $tempPath | where {$_.extension -eq ".exe"}).Name

  # install package
  Install-ChocolateyInstallPackage "$packageName" "$installerType" "$silentArgs" "$pathToExe" -validExitCodes $validExitCodes

  #profit
  write-host "$packageName installed successfully"

} catch {

  #cry
  throw $_.Exception.Message

}
tools\chocolateyUninstall.ps1 
. (Join-Path (Split-Path -parent $MyInvocation.MyCommand.Definition) 'helpers\helpers.ps1')

$packageTitle   = "XYplorer"
$trySilent      = 0;
$silentArgs     = '/S'



try {

    AutoUninstall `
        -programName    $packageTitle `
        -trySilent      $trySilent `
        -silentargs     $silentArgs

} catch {
    throw $_.Exception
}
tools\helpers\.git
tools\helpers\helpers.ps1 
# ====================================================
# GetMenuStartPath
# ====================================================
# Grabs Menu Start location from registry.
#
# @return   {string}    Menu Start path
# ====================================================

Function GetMenuStartPath(){
	return (Get-ItemProperty -Path "Registry::HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders")."Start Menu"
}





# ====================================================
# GetUninstallString
# ====================================================
# Searches Registry for the uninstall string
#
# @param    {string}    $programName    Regex pattern for full program name, as its referred to in registry
# @param    {bool}      $trySilent      Try checking for silent uninstall string?
# @return   {string}                    Full uninstall path (no flags)
# ====================================================

Function GetUninstallString{
  param(
    [string]  $programName, 
    [bool]    $trySilent = 0
  )

  $uninstallType = "UninstallString"

  # establish all possible locations for uninstaller to be stored
  $local_key      = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall'
  $machine_key32  = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall'
  $machine_key64  = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall'
  $reg_locations  = @()

  if(Test-Path "$local_key"){
    $reg_locations += "$local_key\*"
  }

  if(Test-Path "$machine_key32"){
    $reg_locations += "$machine_key32\*"
  }

  if( ((Get-WmiObject Win32_Processor).AddressWidth -eq 64) -and (Test-Path "$machine_key64") ) {
    $reg_locations += "$machine_key64\*"
  }
  
  if($trySilent){
    $uninstallType = "QuietUninstallString"
  }

  # find and return the actual uninstaller path
  return `
    ( `
      Get-ItemProperty -Path $reg_locations | `
      ?{ $_.DisplayName     -match  "$programName" } `
    ) | `
    ?{ $_.$uninstallType  -ne     $null} | `
    select -exp $uninstallType -unique
}





# ====================================================
# AutoUninstall
# ====================================================
# Tries to autouninstall a package
#
# @param    {string}    $programName        (required)  Full program name, as its referred to in registry
# @param    {bool}      $trySilent          (optional)  Try checking for silent uninstall string?
# @param    {string}    $silentArgs         (optional)  Additional silent uninstall arguments to 
#                                                       be added to the ones detected in registry
# @param    {object}    $ValidExitCodes     (optional)  Passing exit codes
# @return   {void}                    
# ====================================================

Function AutoUninstall {
  param(
    [string]  $programName, 
    [bool]    $trySilent      = 0,
    [string]  $silentArgs     = '',
              $validExitCodes = @(0)
  )

  try {
      $uninstallers = GetUninstallString $programName $trySilent

      # determine the name we're searching for in registry
      $uninstallerRegistryQuery = "UninstallString"
      if($trySilent -eq 1){
          $uninstallerRegistryQuery = "QuietUninstallString"
      }


      #loop through all returned strings and trigger corresponding uninstaller
      ForEach ($uninstaller in $uninstallers) {


          # define vars for MSI
          if($package -like "MsiExec.exe*"){

              $uninstaller    = ($uninstaller -replace 'MsiExec.exe /X', '')
              $installerType  = "msi"

          # define vars for EXE
          }else{

              # if there are any flags passed, extract them, otherwise PS/Chocolatey will freak out
              if($uninstaller -like '*.exe" /*'){
                  $silentArgs += ($uninstaller -replace '^.*?\.exe\"\s+(.*?)$', ' $1')
                  $uninstaller = ($uninstaller -replace '^(.*?\.exe\")\s+.*?$', ' $1')
              }

              $installerType  = "exe"
          }



          # uninstall package
          Uninstall-ChocolateyPackage `
              -PackageName    "$programName" `
              -FileType       $installerType `
              -SilentArgs     "$($silentArgs)" `
              -File           "$($uninstaller)" `
              -ValidExitCodes $validExitCodes

      }



  } catch {
    throw $_.Exception
  }



}






# ====================================================
# GetBinRoot
# ====================================================
# Negotiates BinRoot path
#
# @return   {string}    Full binroot path
# ====================================================

Function GetBinRoot(){

  $path = 'C:\tools'

  if($env:ChocolateyBinRoot -ne $null){
		$path = $env:ChocolateyBinRoot
  }

  return $path
}













# ====================================================
# Import-Certificate
# ====================================================
# Function to import security certificates.
# NOTE: To get a list of available store names, run the following command:
# dir cert: | Select -Expand StoreNames
#
# Example Usages:
# Import-Certificate -CertFile "VeriSign_Expires-2028.08.01.cer" -StoreNames AuthRoot, Root -LocalMachine
# Import-Certificate -CertFile "VeriSign_Expires-2018.05.18.p12" -StoreNames AuthRoot -LocalMachine -CurrentUser -CertPassword Password -Verbose
# dir -Path C:\Certs -Filter *.cer | Import-Certificate -CertFile $_ -StoreNames AuthRoot, Root -LocalMachine -Verbose
#
# @src      http://poshcode.org/3518
# @depends  Powershell 2+
#
# @param    {string}    $CertFile       Full path to .crt file
# @param    {list}      $StoreNames     Comma separated list of strings corresponding to Crtificate shops:
#                                       SmartCardRoot | UserDS | AuthRoot | CA | Trust | Disallowed | My | 
#                                       Root | TrustedPeople | TrustedPublisher
# @param    {bool}      $LocalMachine   Using the local machine certificate store to import the certificate
# @param    {bool}      $CurrentUser    Using the current user certificate store to import the certificate
# @param    {string}    $CertPassword   The password which may be used to protect the certificate file
# @param    {bool}      $Verbose        Spit out stuff         
# @return   {string}                    Full uninstall path (no flags)
# ====================================================

# Function to import security certificates.
# http://poshcode.org/3518
# NOTE: To get a list of available store names, run the following command:
# dir cert: | Select -Expand StoreNames
#

Function Import-Certificate{
  param
  (
    [IO.FileInfo] $CertFile = $(throw "Paramerter -CertFile [System.IO.FileInfo] is required."),
    [string[]] $StoreNames = $(throw "Paramerter -StoreNames [System.String] is required."),
    [switch] $LocalMachine,
    [switch] $CurrentUser,
    [string] $CertPassword,
    [switch] $Verbose
  )
  
  begin
  {
    [void][System.Reflection.Assembly]::LoadWithPartialName("System.Security")
  }
  
  process 
  {
        if ($Verbose)
    {
            $VerbosePreference = 'Continue'
        }
    
    if (-not $LocalMachine -and -not $CurrentUser)
    {
      Write-Warning "One or both of the following parameters are required: '-LocalMachine' '-CurrentUser'. Skipping certificate '$CertFile'."
    }

    try
    {
      if ($_)
            {
                $certfile = $_
            }
            $cert = New-Object System.Security.Cryptography.X509Certificates.X509Certificate2 $certfile,$CertPassword
    }
    catch
    {
      Write-Error ("Error importing '$certfile': $_ .") -ErrorAction:Continue
    }
      
    if ($cert -and $LocalMachine)
    {
      $StoreScope = "LocalMachine"
      $StoreNames | ForEach-Object {
        $StoreName = $_
        if (Test-Path "cert:\$StoreScope\$StoreName")
        {
          try
          {
            $store = New-Object System.Security.Cryptography.X509Certificates.X509Store $StoreName, $StoreScope
            $store.Open([System.Security.Cryptography.X509Certificates.OpenFlags]::ReadWrite)
            $store.Add($cert)
            $store.Close()
            Write-Verbose "Successfully added '$certfile' to 'cert:\$StoreScope\$StoreName'."
          }
          catch
          {
            Write-Error ("Error adding '$certfile' to 'cert:\$StoreScope\$StoreName': $_ .") -ErrorAction:Continue
          }
        }
        else
        {
          Write-Warning "Certificate store '$StoreName' does not exist. Skipping..."
        }
      }
    }
    
    if ($cert -and $CurrentUser)
    {
      $StoreScope = "CurrentUser"
      $StoreNames | ForEach-Object {
        $StoreName = $_
        if (Test-Path "cert:\$StoreScope\$StoreName")
        {
          try
          {
            $store = New-Object System.Security.Cryptography.X509Certificates.X509Store $StoreName, $StoreScope
            $store.Open([System.Security.Cryptography.X509Certificates.OpenFlags]::ReadWrite)
            $store.Add($cert)
            $store.Close()
            Write-Verbose "Successfully added '$certfile' to 'cert:\$StoreScope\$StoreName'."
          }
          catch
          {
            Write-Error ("Error adding '$certfile' to 'cert:\$StoreScope\$StoreName': $_ .") -ErrorAction:Continue
          }
        }
        else
        {
          Write-Warning "Certificate store '$StoreName' does not exist. Skipping..."
        }
      }
    }
  }
  
  end
  { }
}
tools\helpers\LICENSE
tools\helpers\README.md 
# Chocolatey Helpers

set of Powershell helpers to be used for creating [Chocolatey](https://chocolatey.org/) packages.  
To be used as submodules, rather than standalone.

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.

Add to Builder Version Downloads Last Updated Status
XYplorer (Install) 24.90.0100 461 Monday, September 11, 2023 Approved
XYplorer (Install) 22.70.0100 2465 Saturday, January 22, 2022 Approved
XYplorer (Install) 22.20.0200 543 Saturday, September 11, 2021 Approved
XYplorer (Install) 21.50.0100 754 Friday, January 29, 2021 Approved
XYplorer (Install) 21.50.0000 273 Saturday, January 16, 2021 Approved
XYplorer (Install) 20.90.0600 1032 Wednesday, July 1, 2020 Approved
XYplorer (Install) 20.90.0500 200 Tuesday, June 9, 2020 Approved
XYplorer (Install) 20.80.0100 588 Tuesday, February 25, 2020 Approved
XYplorer (Install) 20.70.0000 234 Thursday, February 6, 2020 Approved
XYplorer (Install) 20.50.0100 563 Sunday, November 3, 2019 Approved
XYplorer (Install) 20.40.0000 300 Wednesday, October 2, 2019 Approved
XYplorer (Install) 20.20.0200 558 Saturday, August 10, 2019 Approved
XYplorer (Install) 20.20.0000 587 Thursday, July 4, 2019 Approved
XYplorer (Install) 20.10.0000 315 Monday, June 3, 2019 Approved
XYplorer (Install) 19.90.0100 276 Sunday, April 28, 2019 Approved
XYplorer (Install) 19.80.0100 300 Monday, March 25, 2019 Approved
XYplorer (Install) 19.70.0100 281 Saturday, February 23, 2019 Approved
XYplorer (Install) 19.60.0100 250 Sunday, February 17, 2019 Approved
XYplorer (Install) 19.50.0200 249 Saturday, January 26, 2019 Approved
XYplorer (Install) 19.40.0100 333 Thursday, November 29, 2018 Approved
XYplorer (Install) 19.10.0100 461 Monday, July 23, 2018 Approved
XYplorer (Install) 19.10.0000 287 Thursday, July 12, 2018 Approved
XYplorer (Install) 19.00.0300 261 Saturday, July 7, 2018 Approved
XYplorer (Install) 19.00.0200 255 Thursday, June 28, 2018 Approved
XYplorer (Install) 19.00.0000 336 Monday, May 28, 2018 Approved
XYplorer (Install) 18.90.0100 303 Sunday, May 13, 2018 Approved
XYplorer 15.50.0200 836 Saturday, August 15, 2015 Approved
XYplorer 15.50.0100 412 Monday, August 3, 2015 Approved
XYplorer 15.40.0000 422 Sunday, June 28, 2015 Approved

This package has no dependencies.

Discussion for the XYplorer Package

Ground Rules:

  • This discussion is only about XYplorer and the XYplorer 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 XYplorer, 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