#### Gunner's File Type Editor (Install)

• 1
• 2
• 3

3.1.4.20170309 | Updated: 10 Mar 2017

1,347

917

Maintainer(s):

Software Author(s):

• Gunner
• 1
• 2
• 3

### All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

To install Gunner's File Type Editor (Install), run the following command from the command line or from PowerShell:

>

To upgrade Gunner's File Type Editor (Install), run the following command from the command line or from PowerShell:

>

To uninstall Gunner's File Type Editor (Install), 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

#### 3. Enter your internal repository url

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

#### 4. Choose your deployment method:


choco upgrade filetypeeditor -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 filetypeeditor -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 filetypeeditor installed win_chocolatey: name: filetypeeditor state: present version: 3.1.4.20170309 source: STEP 3 URL   chocolatey_package 'filetypeeditor' do action :install version '3.1.4.20170309' source 'STEP 3 URL' end   Chocolatey::Ensure-Package ( Name: filetypeeditor, Version: 3.1.4.20170309, Source: STEP 3 URL );  Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.  cChocoPackageInstaller filetypeeditor { Name = 'filetypeeditor' Ensure = 'Present' Version = '3.1.4.20170309' Source = 'STEP 3 URL' }  Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.  package { 'filetypeeditor': provider => 'chocolatey', ensure => '3.1.4.20170309', source => 'STEP 3 URL', }  Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.  salt '*' chocolatey.install filetypeeditor version="3.1.4.20170309" source="STEP 3 URL"  #### 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 as a trusted package on 08 Jul 2020. Description Graphical editor for modifying and protect Windows file type associations without using the registry. tools\chocolateyinstall.ps1 $ErrorActionPreference = 'Stop';

$packageName= 'filetypeeditor'$toolsDir   = "$(Split-Path -parent$MyInvocation.MyCommand.Definition)"
$url = 'http://www.gunnerinc.com/files/gfte.zip'$packageArgs = @{
packageName   = $packageName unzipLocation =$toolsDir
fileType      = 'EXE_MSI_OR_MSU'
url           = $url softwareName = 'filetypeeditor*' checksum = '0ED8A83A537ECACADB53886069FEC3B80137C33F6B8533C6158E0A6B47051AA0' checksumType = 'sha256' validExitCodes= @(0, 3010, 1641) } Install-ChocolateyZipPackage @packageArgs Write-Output "********************************************************************" Write-Output "* INSTRUCTIONS: Type "gfte.exe" to edit file type associations. *" Write-Output "* More Info: http://www.gunnerinc.com/gfte.htm *" Write-Output "********************************************************************"  tools\chocolateyuninstall.ps1 # IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file: #$f='c:\path\to\thisFile.ps1'
#   gc $f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^]#.*','$1'} | Out-File $f+".~" -en utf8; mv -fo$f+".~" $f ## NOTE: In 80-90% of the cases (95% with licensed versions due to Package Synchronizer and other enhancements), you may ## not need this file due to AutoUninstaller. See https://chocolatey.org/docs/commands-uninstall ## If this is an MSI, cleaning up comments is all you need. ## If this is an exe, change installerType and silentArgs ## Auto Uninstaller should be able to detect and handle registry uninstalls (if it is turned on, it is in preview for 0.9.9). ## - https://chocolatey.org/docs/helpers-uninstall-chocolatey-package$ErrorActionPreference = 'Stop'; # stop on all errors

$packageName = 'filetypeeditor'$softwareName = 'filetypeeditor*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
$installerType = 'MSI' #$installerType = 'EXE'

$silentArgs = '/qn /norestart' # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx$validExitCodes = @(0, 3010, 1605, 1614, 1641)
if ($installerType -ne 'MSI') { # The below is somewhat naive and built for EXE installers # Uncomment matching EXE type (sorted by most to least common) #$silentArgs = '/S'           # NSIS
#$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup #$silentArgs = '/s'           # InstallShield
#$silentArgs = '/s /v"/qn"' # InstallShield with MSI #$silentArgs = '/s'           # Wise InstallMaster
#$silentArgs = '-s' # Squirrel #$silentArgs = '-q'           # Install4j
#$silentArgs = '-s -u' # Ghost # Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence. #$silentArgs = ''             # none; make silent with input macro script like AutoHotKey (AHK)
#       https://chocolatey.org/packages/autohotkey.portable
$validExitCodes = @(0) }$uninstalled = $false # Get-UninstallRegistryKey is new to 0.9.10, if supporting 0.9.9.x and below, # take a dependency on "chocolatey-uninstall.extension" in your nuspec file. # This is only a fuzzy search if$softwareName includes '*'. Otherwise it is
# exact. In the case of versions in key names, we recommend removing the version
# and using '*'.
[array]$key = Get-UninstallRegistryKey -SoftwareName$softwareName

if ($key.Count -eq 1) {$key | % {
$file = "$($_.UninstallString)" if ($installerType -eq 'MSI') {
# The Product Code GUID is all that should be passed for MSI, and very
# FIRST, because it comes directly after /x, which is already set in the
# Uninstall-ChocolateyPackage msiargs (facepalm).
$silentArgs = "$($_.PSChildName)$silentArgs"

# Don't pass anything for file, it is ignored for msi (facepalm number 2)
# Alternatively if you need to pass a path to an msi, determine that and
# use it instead of the above in silentArgs, still very first
$file = '' } Uninstall-ChocolateyPackage -PackageName$packageName 
-FileType $installerType  -SilentArgs "$silentArgs" 
-ValidExitCodes $validExitCodes  -File "$file"
}
} elseif ($key.Count -eq 0) { Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) { Write-Warning "$key.Count matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
$key | % {Write-Warning "-$_.DisplayName"}
}

## OTHER HELPERS
## https://chocolatey.org/docs/helpers-reference
#Uninstall-ChocolateyZipPackage \$packageName # Only necessary if you did not unpack to package directory - see https://chocolatey.org/docs/helpers-uninstall-chocolatey-zip-package
#Uninstall-ChocolateyEnvironmentVariable # 0.9.10+ - https://chocolatey.org/docs/helpers-uninstall-chocolatey-environment-variable
#Uninstall-BinFile # Only needed if you used Install-BinFile - see https://chocolatey.org/docs/helpers-uninstall-bin-file
## Remove any shortcuts you added



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.

Gunner's File Type Editor 3.1.4.8 430 Tuesday, July 7, 2015 Approved

This package has no dependencies.

Discussion for the Gunner's File Type Editor (Install) Package

### Ground Rules:

• This discussion is only about Gunner's File Type Editor (Install) and the Gunner's File Type Editor (Install) 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 Gunner's File Type Editor (Install), 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.