Downloads of v 0.6.0:


Last Update:

29 Apr 2016

Package Maintainer(s):

Software Author(s):

  • Tommy Parnell


MSI creation IIS

QuikPak (Install)

This is not the latest version of QuikPak (Install) available.

  • 1
  • 2
  • 3

0.6.0 | Updated: 29 Apr 2016



Downloads of v 0.6.0:



Software Author(s):

  • Tommy Parnell


MSI creation IIS

  • 1
  • 2
  • 3
QuikPak (Install) 0.6.0

This is not the latest version of QuikPak (Install) available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


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.


To install QuikPak (Install), run the following command from the command line or from PowerShell:


To upgrade QuikPak (Install), run the following command from the command line or from PowerShell:


To uninstall QuikPak (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 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

4. Choose your deployment method:

choco upgrade quikpak -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 quikpak -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure quikpak installed
    name: quikpak
    state: present
    version: 0.6.0
    source: STEP 3 URL

See docs at

chocolatey_package 'quikpak' do
  action    :install
  version  '0.6.0'
  source   'STEP 3 URL'

See docs at

    Name: quikpak,
    Version: 0.6.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller quikpak
   Name     = 'quikpak'
   Ensure   = 'Present'
   Version  = '0.6.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'quikpak':
  provider => 'chocolatey',
  ensure   => '0.6.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install quikpak version="0.6.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator doc on 29 Apr 2016.


quickly pack directory's as IIS websites

md5: DB5527F6160889F322FF354DD76C60B3 | sha1: 537A78FC9F730854DBB36EF6333EDE397E8FCAD6 | sha256: 1404BE200B556FBE0A74F933658BF3224DF1BE863D4F633A06748BE222CC29F4 | sha512: 40BAEA552F545CBF60E2C06EAAD7098F176C894B3B759AC55B655CCE10EAD4E0F5066B14382BA72D58911636BB6DD1B73FF67EBFFF4544B30CCAEB9BBC03B75D
md5: EC0E2DD54144D6F6A317B7DAA715D418 | sha1: 62C2E04BBA8436912D9BCEC1EC4D4C7AFC843A47 | sha256: 4923528D3D18689D58FA30B3D822AB72A13BE21A57F13E0BC59B55B864424F7A | sha512: CCAF01F89FAB001EF2DED15B352E1DD2AB3967584A8720ACB7C6B7203240F9C896F7D46600B12E0E86B25B30779B1E5ED59CE97FB3F295AFB11D6391670265EF
md5: 233CA870E2530DA48897DB8FA6F1E3CF | sha1: 1E4B4964978858C787F2A898B20F36E1FA805717 | sha256: CA420FEF4909C10E2E95C8C899FA7D009892DDDF0B2424870236F1D0676E9165 | sha512: 25544EE4113FE4DC2B54F8A5A068F340BBB3B30BD444FF18DCDC789C573D2C24F3019601C3C9E8EEC4A61FBB5540867930B99A3696358EB587F64D3A70E1B9A6
md5: C3C04754418382F505CAFC18D64427F5 | sha1: CAC5E36DC498D6BB16170020BE021FF5BD18A9E2 | sha256: DF8EC2E0245829DDEC5B79F1918C3AE3A3FA540A5A0E3C410E2B6EF0BEBC7927 | sha512: BDA5EFD0F69A9C7198841E5D31744FA2BEBB05CEDB1E2846A0D2DBCE6C3193DA69C181BE1116F38CD5F3D61B441567B1DA2C844522184323E3D429294AA91AB5
md5: 75EC1FC4B80485712A745D3F57E96E6D | sha1: 5408D09DC3BF1B0890000C5FE9C5882C57E72A32 | sha256: CD93830C8F2C271862AB3AE3D12737FAA1A27180B05AB3E41238638746436178 | sha512: C9E948D584B8BD387982B4ECF111B14C6395296E166055C5EC2163FD73B139FF78CF7F6EB8A24C9A2081EC89369227CD303936FC21E734A1CDDBB4B0D6192489
<?xml version="1.0" encoding="utf-8" ?>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
## Summary
How do I create packages? See

If you are submitting packages to the community feed (
always try to ensure you have read, understood and adhere to the create
packages wiki link above.

## Automatic Packages?
Consider making this package an automatic package, for the best 
maintainability over time. Read up at

## Shim Generation
Any executables you include in the package or download (but don't call 
install against using the built-in functions) will be automatically shimmed.

This means those executables will automatically be included on the path.
Shim generation runs whether the package is self-contained or uses automation 

By default, these are considered console applications. 

If the application is a GUI, you should create an empty file next to the exe 
named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'.

If you want to ignore the executable, create an empty file next to the exe 
named 'name.exe.ignore' e.g. 'bob.exe' would need a file named 

## Self-Contained? 
If you have a self-contained package, you can remove the automation scripts 
entirely and just include the executables, they will automatically get shimmed, 
which puts them on the path. Ensure you have the legal right to distribute 
the application though. See 

You should read up on the Shim Generation section to familiarize yourself 
on what to do with GUI applications and/or ignoring shims.

## Automation Scripts
You have a powerful use of Chocolatey, as you are using PowerShell. So you
can do just about anything you need. Choco has some very handy built-in 
functions that you can use, these are sometimes called the helpers.

### Built-In Functions

A note about a couple:
* Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder. 
* Install-BinFile - used for non-exe files - executables are automatically shimmed...
* Uninstall-BinFile - used for non-exe files - executables are automatically shimmed

### Getting package specific information
Use the package parameters pattern - see

### Need to mount an ISO?

### Environment Variables
Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow):

 * TEMP = Overridden to the CacheLocation, but may be the same as the original TEMP folder
 * ChocolateyInstall = Top level folder where Chocolatey is installed
 * chocolateyPackageName = The name of the package, equivalent to the id in the nuspec (0.9.9+)
 * chocolateyPackageVersion = The version of the package, equivalent to the version in the nuspec (0.9.9+)
 * chocolateyPackageFolder = The top level location of the package folder

#### Advanced Environment Variables
The following are more advanced settings:

 * chocolateyPackageParameters = (
 * CHOCOLATEY_VERSION = The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+)
    - Otherwise take a dependency on the specific version you need. 
 * chocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+)
    - Automatically handled in built in Choco functions. 
 * OS_PLATFORM = Like Windows, OSX, Linux. (0.9.9+)
 * OS_VERSION = The version of OS, like 6.1 something something for Windows. (0.9.9+)
 * OS_NAME = The reported name of the OS. (0.9.9+)
 * IS_PROCESSELEVATED = Is the process elevated? (0.9.9+)
#### Experimental Environment Variables
The following are experimental or use not recommended:

 * OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under (0.9.9+)
 * CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+)
    - it's based on git describe
 * IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+)
 * chocolateyInstallOverride = Not for use in package automation scripts. (0.9.9+)
 * chocolateyInstallArguments = the installer arguments meant for the native installer. You should use chocolateyPackageParameters intead. (0.9.9+)

md5: 55DBBB4A2FB677C4D846AA4C5BB62F85 | sha1: B137A643B5BAAE8FFAB9B25933A0BA480846BBE7 | sha256: 6A7C8259155BC60DA99A458C2E483E525629FE8DE5BF2AE89A2BF66D69E65265 | sha512: C69735CEE4EF8B3034B9C0B2C2D4889111C2393445706ABBC9FEA8EE702877D5B6D16678FFC703FB21265320B1B93E07BA9C34CDB63A442E128358B3D811A58B
md5: CAD514EF7E1F5C579BA3B60C23CF510F | sha1: 20EEB1153B99022197BA2F137155552231E748D7 | sha256: 1179544798906E867D5B0A16CC86BB9B47B532E327726FA8A77EABA3B5B05F0B | sha512: C23A624E3FDF33460E3F077D056D8969C907B979D2AB2752481311D3686C39E2FE779E2BC7EEAF8AFCFA9332D3B469F1DF2355516C5CC712DDB0110337C59752
md5: 7B76A20AC9B68D9111E9507B9DC38F60 | sha1: EC8614CAFA5B0C34D5109D2E0D2FAC8C87C93635 | sha256: 3B11300CCBCF2EB688505396CDDF9551119163B419F4EA412EFB0C0A2AF1D4CD | sha512: 8D940621D0A42F907C11691592D72DAAA3092275BC501FFC37DB5BE3774A7B2F3B0B4287E11BEDC1984431B080C81E6F33BCE010F61CB33F89E178A5705EFD4B

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
QuikPak (Install) 0.7.0 280 Friday, April 29, 2016 Approved
QuikPak (Install) 0.6.0 325 Friday, April 29, 2016 Approved
Discussion for the QuikPak (Install) Package

Ground Rules:

  • This discussion is only about QuikPak (Install) and the QuikPak (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 QuikPak (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.
comments powered by Disqus