#### Get-ChildItemColor (PowerShell Module)

1.2.3 | Updated: 5/18/2018

399

273

Maintainer(s):

Software Author(s):

• Joon Ro

### All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install Get-ChildItemColor (PowerShell Module), run the following command from the command line or from PowerShell:

>

To upgrade Get-ChildItemColor (PowerShell Module), run the following command from the command line or from PowerShell:

>

To uninstall Get-ChildItemColor (PowerShell Module), 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

#### 3. Enter your internal repository url

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

#### 4. Choose your deployment method:


choco upgrade get-childitemcolor -y --source="'STEP 3 URL'" [other options]


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 get-childitemcolor -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 get-childitemcolor installed win_chocolatey: name: get-childitemcolor state: present version: 1.2.3 source: STEP 3 URL  Coming early 2020! Central Managment Reporting available now! More information...  chocolatey_package 'get-childitemcolor' do action :install version '1.2.3' source 'STEP 3 URL' end   Chocolatey::Ensure-Package ( Name: get-childitemcolor, Version: 1.2.3, Source: STEP 3 URL );  Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.  cChocoPackageInstaller get-childitemcolor { Name = 'get-childitemcolor' Ensure = 'Present' Version = '1.2.3' Source = 'STEP 3 URL' }  Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.  package { 'get-childitemcolor': provider => 'chocolatey', ensure => '1.2.3', source => 'STEP 3 URL', }  Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.  salt '*' chocolatey.install get-childitemcolor version="1.2.3" source="STEP 3 URL"  #### 5. If applicable - Chocolatey configuration/installation See infrastructure management matrix for Chocolatey configuration elements and examples. This package was approved by moderator gep13 on 5/23/2018. Description Get-ChildItemColor provides colored version of Get-ChildItem Cmdlet and Get-ChildItem | Format-Wide (ls equivalent). • This adds colors to the output of Get-ChildItem Cmdlet of PowerShell. It is based on Tim Johnson’s script and another script by the PowerShell Guy. • Before version 1.0.0, the script actually had used Write-Host to write colored items on console. Now it just changes$Host.UI.RawUI.ForegroundColor and keep the item object intact. Hence, now one can use pipeline. (e.g., ~Get-ChildItemColor | grep “.git”~).
• Get-ChildItemColorFormatWide still uses Write-Host for output however. This is because Get-ChildItemColor | Format-Wide does not allow multiple colors in one line. Hence, pipeline does not work with Get-ChildItemColorFormatWide.

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

tools\.skipAutoUninstaller
tools\chocolateyBeforeModify.ps1
tools\chocolateyInstall.ps1
tools\chocolateyUninstall.ps1
tools\Get-ChildItemColor\devel\Get-ChildItemColor debug.ps1
tools\Get-ChildItemColor\devel\zcpub-Freeman_Virtual-Freeman_Virtual-CmsTempVm.rdp
tools\Get-ChildItemColor\example\config.ini
tools\Get-ChildItemColor\example\dll.dll
tools\Get-ChildItemColor\example\executable.exe
tools\Get-ChildItemColor\example\others
tools\Get-ChildItemColor\example\text.txt
tools\Get-ChildItemColor\Get-ChildItemColor.psd1
tools\Get-ChildItemColor\Get-ChildItemColor.psm1
tools\Get-ChildItemColor\PSGetModuleInfo.xml
tools\Get-ChildItemColor\screenshots\Get-ChildItemColor.png
tools\Get-ChildItemColor\screenshots\Get-ChildItemColorFormatWide.png
tools\VERIFICATION.txt

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.

Get-ChildItemColor (PowerShell Module) 2.1.0 13 Monday, July 22, 2019 Approved
Get-ChildItemColor (PowerShell Module) 2.0.0 16 Sunday, July 21, 2019 Approved
Get-ChildItemColor (PowerShell Module) 1.2.3 273 Friday, May 18, 2018 Approved

This package has no dependencies.

Discussion for the Get-ChildItemColor (PowerShell Module) Package