Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

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 packages and push them to a repository
  Download Packages

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the packages:
  Download Packages
- Follow manual internalization instructions
Package Internalizer (C4B)
- Run: (additional options)
- For package and dependencies run:
- Automate package internalization

Step 5: Copy Your Script

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:

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###

#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"

#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072

#### We use this variable for future REST calls.
$RequestArguments = @{
    UseBasicParsing = $true
}

## 2. TOP LEVEL VARIABLES ##

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
#     "username",
#     ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.0.11.3.nupkg"

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    $TempDirectory = Join-Path $env:Temp "chocolateyInstall"
    if (-not (Test-Path $TempDirectory -PathType Container)) {
        $null = New-Item -Path $TempDirectory -ItemType Directory
    }
    $DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
    Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments

    #### Extract the Nupkg, and run the chocolateyInstall script
    if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
        Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
    } else {
        # PowerShell versions <4.0 do not have this function available
        try {
            $shellApplication = New-Object -ComObject Shell.Application
            $zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
            $destinationFolder = $shellApplication.NameSpace($TempDirectory)
            $destinationFolder.CopyHere($zipPackage.Items(), 0x10)
        } catch {
            Write-Warning "Unable to unzip package using built-in compression."
            throw $_
        }
    }

    & $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}

if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    refreshenv
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums

### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400

#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress

### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
    if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
        choco source remove -n $_.Name
    }
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco source disable --name chocolatey.licensed
} else {
    Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
    Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
    choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
    choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
    if ($ChocolateyCentralManagementClientSalt) {
        choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
    }
    if ($ChocolateyCentralManagementServiceSalt) {
        choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
    }
    choco feature enable --name useChocolateyCentralManagement
    choco feature enable --name useChocolateyCentralManagementDeployments
}

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

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
    nuget_repository_url: INTERNAL REPO URL

### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
#    nuget_repository_username: username
#    nuget_repository_password: password

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#    chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService

#### ii. If using a Client Salt, add it here
#    chocolatey_central_management_client_salt: clientsalt

#### iii. If using a Service Salt, add it here
#    chocolatey_central_management_service_salt: servicesalt

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

  tasks:
  - name: Install chocolatey
    win_chocolatey:
      name: chocolatey
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#   - name: Enable FIPS compliance
#     win_chocolatey_feature:
#       name: useFipsCompliantChecksums
#       state: enabled

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
  - name: Set the cache location
    win_chocolatey_config:
      name: cacheLocation
      state: present
      value: C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
  - name: Set the command execution timeout
    win_chocolatey_config:
      name: commandExecutionTimeoutSeconds
      state: present
      value: 14400

#### Turn off download progress when running choco through integrations
  - name: Disable showing download progress
    win_chocolatey_feature:
      name: showDownloadProgress
      state: disabled

### c. Sources ###
#### Remove the default community package repository source
  - name: Remove Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey
      state: absent

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
  - name: Add Internal Repository
    win_chocolatey_source:
      name: ChocolateyInternal
      state: present
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}
      priority: 1

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
  - name: Upgrade Chocolatey
    win_chocolatey:
      name: chocolatey
      state: latest

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
  - name: Install Chocolatey License
    win_chocolatey:
      name: chocolatey-license
      source: ChocolateyInternal
      state: latest

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
  - name: Disable Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey.licensed
      state: disabled

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
  - name: Install Chocolatey Extension
    win_chocolatey:
      name: chocolatey.extension
      source: ChocolateyInternal
      state: latest

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
  - name: Hide not-elevated warnings
    win_chocolatey_feature:
      name: showNonElevatedWarnings
      state: disabled

  - name: Use background mode for self-service
    win_chocolatey_feature:
      name: useBackgroundService
      state: enabled

  - name: Use background service for non-admins
    win_chocolatey_feature:
      name: useBackgroundServiceWithNonAdministratorsOnly
      state: enabled

  - name: Allow background uninstallation for user installs
    win_chocolatey_feature:
      name: allowBackgroundServiceUninstallsFromUserInstallsOnly
      state: enabled

  - name: Set allowed background service commands
    win_chocolatey_config:
      name: backgroundServiceAllowedCommands
      state: present
      value: install,upgrade,uninstall

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
  - name: Install Chocolatey Agent
    when: chocolatey_central_management_url is defined
    win_chocolatey:
      name: chocolatey-agent
      source: ChocolateyInternal
      state: latest

  - name: Set the Central Management Service URL
    when: chocolatey_central_management_url is defined
    win_chocolatey_config:
      name: CentralManagementServiceUrl
      state: present
      value: {{ chocolatey_central_management_url }}

  - name: Set the Central Management Client Salt
    when: chocolatey_central_management_client_salt is defined
    win_chocolatey_config:
      name: centralManagementClientCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_client_salt }}

  - name: Set the Central Management Service Salt
    when: chocolatey_central_management_service_salt is defined
    win_chocolatey_config:
      name: centralManagementServiceCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_service_salt }}

  - name: Use Central Management
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagement
      state: enabled

  - name: Use Central Management Deployments
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagementDeployments
      state: enabled

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

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"

## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.0.11.3.nupkg",

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
  'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
#   action :enable
# end

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
  value 'C:\ProgramData\chocolatey\cache'
end

#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
  value '14400'
end

#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
  action :disable
end

### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
  action :remove
end

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
  source "#{NugetRepositoryUrl}"
  priority 1
  action   :add
end

execute 'ChocolateyInternal' do
  command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
  only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
  action :upgrade
  source "#{NugetRepositoryUrl}"
end

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
  action :install
  source "#{NugetRepositoryUrl}"
end

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
  action            :disable
end

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
  action     install
  source     "#{NugetRepositoryUrl}"
end

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
  action :disable
end

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

chocolatey_config 'backgroundServiceAllowedCommands' do
  value 'install,upgrade,uninstall'
end

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
  action     install
  source     "#{NugetRepositoryUrl}"
  # user       "#{NugetRepositoryUsername}"
  # password   "#{NugetRepositoryPassword}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'CentralManagementServiceUrl' do
  value  "#{ChocolateyCentralManagementUrl}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementClientSalt}"
  only_if { ChocolateyCentralManagementClientSalt != nil }
end

chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementServiceSalt}"
  only_if { ChocolateyCentralManagementServiceSalt != nil }
end

chocolatey_feature 'useChocolateyCentralManagement' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_feature 'useChocolateyCentralManagementDeployments' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

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

If Applicable - Chocolatey Configuration/Installation


#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
    $null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
    }
    Install-Module -Name cChoco
    if ($PSGallery.InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
    }
}

#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1

Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
    param(
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
        $NugetRepositoryUrl      = "INTERNAL REPO URL",

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
        $ChocolateyNupkgUrl      = "INTERNAL REPO URL/package/chocolatey.0.11.3.nupkg",

### c. Internal Repository Credential ###
#### If required, add the repository access credential here
#        $NugetRepositoryCredential = [PSCredential]::new(
#            "username",
#            ("password" | ConvertTo-SecureString -AsPlainText -Force)
#        ),

### d. Install.ps1 URL
#### The path to the hosted install script:
        $ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"

### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#        $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",

#### ii. If using a Client Salt, add it here
#        $ChocolateyCentralManagementClientSalt = "clientsalt",

#### iii. If using a Service Salt, add it here
#        $ChocolateyCentralManagementServiceSalt = "servicesalt"
    )
    Import-DscResource -ModuleName PSDesiredStateConfiguration
    Import-DscResource -ModuleName cChoco

    Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
        Environment chocoDownloadUrl {
            Name  = "chocolateyDownloadUrl"
            Value = $ChocolateyNupkgUrl
        }

        cChocoInstaller installChocolatey {
            DependsOn = "[Environment]chocoDownloadUrl"
            InstallDir = Join-Path $env:ProgramData "chocolatey"
            ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
        }

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#        cChocoFeature featureFipsCompliance {
#            FeatureName = "useFipsCompliantChecksums"
#        }

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
        cChocoConfig cacheLocation {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "cacheLocation"
            Value      = "C:\ProgramData\chocolatey\cache"
        }

#### Increase timeout to at least 4 hours
        cChocoConfig commandExecutionTimeoutSeconds {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "commandExecutionTimeoutSeconds"
            Value      = 14400
        }

#### Turn off download progress when running choco through integrations
        cChocoFeature showDownloadProgress {
            DependsOn   = "[cChocoInstaller]installChocolatey"
            FeatureName = "showDownloadProgress"
            Ensure      = "Absent"
        }

### c. Sources ###
#### Remove the default community package repository source
        cChocoSource removeCommunityRepository {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name       = "chocolatey"
            Ensure     = "Absent"
        }

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
        cChocoSource addInternalSource {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name        = "ChocolateyInternal"
            Source      = $NugetRepositoryUrl
            Credentials = $NugetRepositoryCredential
            Priority    = 1
        }

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
        cChocoPackageInstaller updateChocolatey {
            DependsOn   = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
            Name        = "chocolatey"
            AutoUpgrade = $true
        }

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
        cChocoPackageInstaller chocolateyLicense {
            DependsOn = "[cChocoPackageInstaller]updateChocolatey"
            Name      = "chocolatey-license"
        }

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
        Script disableLicensedSource {
            DependsOn  = "[cChocoPackageInstaller]chocolateyLicense"
            GetScript  = {
                $Source = choco source list --limitoutput | `
                    ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
                    Where-Object Name -eq "chocolatey.licensed"

                return @{
                    Result = if ($Source) {
                        [bool]::Parse($Source.Disabled)
                    } else {
                        Write-Warning "Source 'chocolatey.licensed' was not present."
                        $true  # Source does not need disabling
                    }
                }
            }
            SetScript  = {
                $null = choco source disable --name "chocolatey.licensed"
            }
            TestScript = {
                $State = [ScriptBlock]::Create($GetScript).Invoke()
                return $State.Result
            }
        }

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
        cChocoPackageInstaller chocolateyLicensedExtension {
            DependsOn = "[Script]disableLicensedSource"
            Name      = "chocolatey.extension"
        }

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
        cChocoFeature hideElevatedWarnings {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "showNonElevatedWarnings"
            Ensure      = "Absent"
        }

        cChocoFeature useBackgroundService {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundService"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceWithNonAdmins {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
            Ensure      = "Present"
        }

        cChocoConfig allowedBackgroundServiceCommands {
            DependsOn   = "[cChocoFeature]useBackgroundService"
            ConfigName = "backgroundServiceAllowedCommands"
            Value       = "install,upgrade,uninstall"
        }

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
        if ($ChocolateyCentralManagementUrl) {
            cChocoPackageInstaller chocolateyAgent {
                DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
                Name      = "chocolatey-agent"
            }

            cChocoConfig centralManagementServiceUrl {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                ConfigName = "CentralManagementServiceUrl"
                Value       = $ChocolateyCentralManagementUrl
            }

            if ($ChocolateyCentralManagementClientSalt) {
                cChocoConfig centralManagementClientSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementClientSalt
                }
            }

            if ($ChocolateyCentralManagementServiceSalt) {
                cChocoConfig centralManagementServiceSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementServiceSalt
                }
            }

            cChocoFeature useCentralManagement {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagement"
                Ensure      = "Present"
            }

            cChocoFeature useCentralManagementDeployments {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagementDeployments"
                Ensure      = "Present"
            }
        }
    }
}

# If working this into an existing configuration with a good method for 
$ConfigData = @{
    AllNodes = @(
        @{
            NodeName                    = "localhost"
            PSDscAllowPlainTextPassword = $true
        }
    )
}

try {
    Push-Location $env:Temp
    $Config = ChocolateyConfig -ConfigurationData $ConfigData
    Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
    Pop-Location
}

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

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
####  See https://forge.puppet.com/puppetlabs/chocolatey


## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.0.11.3.nupkg'

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'

#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'


## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
###  source locations. This is directly to the bare download url for the
###  chocolatey.nupkg, similar to what you see when you browse to
###  https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
  chocolatey_download_url => $_choco_download_url,
  use_7zip                => false,
}


## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations

#chocolateyfeature {'useFipsCompliantChecksums':
#  ensure => enabled,
#}

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
  value => 'C:\ProgramData\chocolatey\cache',
}

#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
  value => '14400',
}

#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
  ensure => disabled,
}

### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
  ensure   => absent,
  location => 'https://community.chocolatey.org/api/v2/',
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
  ensure             => present,
  location           => $_repository_url,
  priority           => 1,
  username           => 'optional',
  password           => 'optional,not ensured',
  bypass_proxy       => true,
  admin_only         => false,
  allow_self_service => false,
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/

package {'chocolatey':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}


## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license

# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
  ensure   => disabled,
  priority => '10',
  user     => 'customer',
  password => '1234',
  require  => Package['chocolatey-license'],
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
  require  => Package['chocolatey-license'],
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
  ensure => disabled,
}

chocolateyfeature {'useBackgroundService':
  ensure => enabled,
}

chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
  ensure => enabled,
}

chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
  ensure => enabled,
}

chocolateyconfig {'backgroundServiceAllowedCommands':
  value => 'install,upgrade,uninstall',
}

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
  package {'chocolatey-agent':
    ensure   => latest,
    provider => chocolatey,
    source   => $_repository_url,
    require  => Package['chocolatey-license'],
  }

  chocolateyconfig {'CentralManagementServiceUrl':
    value   => $_chocolatey_central_management_url,
  }

  if $_chocolatey_central_management_client_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  if $_chocolatey_central_management_service_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  chocolateyfeature {'useChocolateyCentralManagement':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }

  chocolateyfeature {'useChocolateyCentralManagementDeployments':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }
}

There is already a version of this package in your Script Builder

Current Version	New Version

Passing
Failing
Pending
Unknown / Exempted

Downloads:

197,123

Downloads of v 10.1.0.0-eap4:

367

Last Update:

29 Feb 2016

Package Maintainer(s):

Software Author(s):

JetBrains

Tags:

JetBrains dotPeek 10.1 EAP 4

This is a prerelease version of JetBrains dotPeek 10.1 EAP 4.

10.1.0.0-eap4 | Updated: 29 Feb 2016

Downloads:

197,123

Downloads of v 10.1.0.0-eap4:

367

Maintainer(s):

Software Author(s):

JetBrains

Tags:

1

2

3

JetBrains dotPeek 10.1 EAP 4 10.1.0.0-eap4

This is a prerelease version of JetBrains dotPeek 10.1 EAP 4.

This Package Contains an Exempted Check

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Exemption:

.NET 4.6.1 dependency requiring reboot

Details

Scan Testing Successful:

No detections found in any package files

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install JetBrains dotPeek 10.1 EAP 4, run the following command from the command line or from PowerShell:

To upgrade JetBrains dotPeek 10.1 EAP 4, run the following command from the command line or from PowerShell:

To uninstall JetBrains dotPeek 10.1 EAP 4, run the following command from the command line or from PowerShell:

📝 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

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

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

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions

Package Internalizer (C4B)

Run: (additional options)

choco download dotpeek --internalize --version=10.1.0.0-eap4 --pre --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

choco push --source="'INTERNAL REPO URL'"

Automate package internalization

3. Copy Your Script

choco upgrade dotpeek -y --source="'INTERNAL REPO URL'" --version="'10.1.0.0-eap4'" --prerelease [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 dotpeek -y --source="'INTERNAL REPO URL'" --version="'10.1.0.0-eap4'" --prerelease
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install dotpeek
  win_chocolatey:
    name: dotpeek
    version: '10.1.0.0-eap4'
    source: INTERNAL REPO URL
    state: present
    allow_prerelease: yes

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


chocolatey_package 'dotpeek' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '10.1.0.0-eap4'
  options  '--prerelease'
end

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


cChocoPackageInstaller dotpeek
{
    Name        = "dotpeek"
    Version     = "10.1.0.0-eap4"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"
}

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


package { 'dotpeek':
  ensure          => '10.1.0.0-eap4',
  install_options => ['--prerelease'],
  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.

This package was approved as a trusted package on 29 Feb 2016.

Description

Free .NET decompiler and assembly browser

Files

tools\chocolateyInstall.ps1

$platformPackageName = 'resharper-platform'
$packageName = 'dotPeek'
try {
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$installPath = Join-Path  (Join-Path $commonPath $platformPackageName) 'JetBrains.ReSharperUltimate.10.1.EAP4.exe'
Start-ChocolateyProcessAsAdmin '/SpecificProductNames=dotPeek /Silent=True' $installPath
Write-ChocolateySuccess "$packageName"
} catch {
throw $_.Exception
}

tools\chocolateyUninstall.ps1

$platformPackageName = 'resharper-platform'
$packageName = 'dotPeek'
try {
$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$installPath = Join-Path  (Join-Path $commonPath $platformPackageName) 'JetBrains.ReSharperUltimate.10.1.EAP4.exe'
Uninstall-ChocolateyPackage $packageName 'exe' '/SpecificProductNamesToRemove=dotPeek /Silent=True /ReSharper9PlusMsi=True' $installPath
Write-ChocolateySuccess "$packageName"
} catch {
throw $_.Exception
}

Virus Scan Results

dotPeek.10.1.0.0-eap4.nupkg (9dd76c349db6) - ## / 57

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 History

Version	Downloads	Last Updated	Status
JetBrains dotPeek 2021.3.2	2166	Saturday, December 25, 2021	Approved
JetBrains dotPeek 2021.3.1	1446	Saturday, December 11, 2021	Approved
JetBrains dotPeek 2021.3	357	Thursday, December 9, 2021	Approved
JetBrains dotPeek 2021.3-EAP9	24	Monday, November 22, 2021	Approved
JetBrains dotPeek 2021.3-EAP8	24	Wednesday, November 17, 2021	Approved
JetBrains dotPeek 2021.3-EAP7	81	Tuesday, November 9, 2021	Approved
JetBrains dotPeek 2021.3-EAP6	32	Saturday, October 30, 2021	Approved
JetBrains dotPeek 2021.3-EAP5	22	Saturday, October 23, 2021	Approved
JetBrains dotPeek 2021.3-EAP4	24	Friday, October 15, 2021	Approved
JetBrains dotPeek 2021.3-EAP3	24	Tuesday, October 12, 2021	Approved
JetBrains dotPeek 2021.3-EAP2	32	Tuesday, October 5, 2021	Approved
JetBrains dotPeek 2021.3-EAP1	26	Wednesday, September 29, 2021	Approved
JetBrains dotPeek 2021.2.2	7151	Thursday, October 14, 2021	Approved
JetBrains dotPeek 2021.2.1	7101	Saturday, August 28, 2021	Approved
JetBrains dotPeek 2021.2	2753	Wednesday, August 4, 2021	Approved
JetBrains dotPeek 2021.2-EAP9	29	Friday, July 30, 2021	Approved
JetBrains dotPeek 2021.2-EAP8	85	Friday, July 23, 2021	Approved
JetBrains dotPeek 2021.2-EAP7	122	Tuesday, July 20, 2021	Approved
JetBrains dotPeek 2021.2-EAP6	32	Saturday, July 10, 2021	Approved
JetBrains dotPeek 2021.2-EAP5	33	Friday, July 2, 2021	Approved
JetBrains dotPeek 2021.2-EAP4	37	Saturday, June 26, 2021	Approved
JetBrains dotPeek 2021.2-EAP3	49	Saturday, June 12, 2021	Approved
JetBrains dotPeek 2021.2-EAP2	42	Saturday, June 5, 2021	Approved
JetBrains dotPeek 2021.2-EAP1	35	Tuesday, June 1, 2021	Approved
JetBrains dotPeek 2021.1.5	1300	Friday, July 23, 2021	Approved
JetBrains dotPeek 2021.1.4	1069	Thursday, July 15, 2021	Approved
JetBrains dotPeek 2021.1.3	5483	Wednesday, May 26, 2021	Approved
JetBrains dotPeek 2021.1.2	3346	Saturday, April 24, 2021	Approved
JetBrains dotPeek 2021.1.1	1429	Sunday, April 11, 2021	Approved
JetBrains dotPeek 2021.1	357	Friday, April 9, 2021	Approved
JetBrains dotPeek 2021.1-EAP9	54	Friday, March 26, 2021	Approved
JetBrains dotPeek 2021.1-EAP8	51	Friday, March 19, 2021	Approved
JetBrains dotPeek 2021.1-EAP7	50	Friday, March 12, 2021	Approved
JetBrains dotPeek 2021.1-EAP6	49	Friday, March 5, 2021	Approved
JetBrains dotPeek 2021.1-EAP5	52	Saturday, February 27, 2021	Approved
JetBrains dotPeek 2021.1-EAP4	330	Sunday, February 21, 2021	Approved
JetBrains dotPeek 2021.1-EAP3	42	Wednesday, February 17, 2021	Approved
JetBrains dotPeek 2021.1-EAP2	55	Friday, February 5, 2021	Approved
JetBrains dotPeek 2021.1-EAP1	47	Tuesday, February 2, 2021	Approved
JetBrains dotPeek 2020.3.4	2309	Thursday, March 18, 2021	Approved
JetBrains dotPeek 2020.3.3	2490	Tuesday, February 23, 2021	Approved
JetBrains dotPeek 2020.3.2	5257	Thursday, December 31, 2020	Approved
JetBrains dotPeek 2020.3.1	655	Friday, December 25, 2020	Approved
JetBrains dotPeek 2020.3	1268	Tuesday, December 15, 2020	Approved
JetBrains dotPeek 2020.3-EAP9	58	Saturday, November 28, 2020	Approved
JetBrains dotPeek 2020.3-EAP8	68	Friday, November 20, 2020	Approved
JetBrains dotPeek 2020.3-EAP7	76	Saturday, November 14, 2020	Approved
JetBrains dotPeek 2020.3-EAP6	66	Friday, November 6, 2020	Approved
JetBrains dotPeek 2020.3-EAP5	59	Friday, October 30, 2020	Approved
JetBrains dotPeek 2020.3-EAP4	79	Saturday, October 17, 2020	Approved
JetBrains dotPeek 2020.3-EAP3	67	Friday, October 9, 2020	Approved
JetBrains dotPeek 2020.3-EAP2	61	Friday, October 2, 2020	Approved
JetBrains dotPeek 2020.3-EAP1	65	Friday, September 25, 2020	Approved
JetBrains dotPeek 2020.2.4	6730	Friday, October 2, 2020	Approved
JetBrains dotPeek 2020.2.3	1722	Saturday, September 19, 2020	Approved
JetBrains dotPeek 2020.2.2	1380	Friday, September 11, 2020	Approved
JetBrains dotPeek 2020.2.1	2260	Saturday, August 22, 2020	Approved
JetBrains dotPeek 2020.2	1096	Thursday, August 13, 2020	Approved
JetBrains dotPeek 2020.2-EAP9	68	Friday, August 7, 2020	Approved
JetBrains dotPeek 2020.2-EAP8	119	Saturday, July 25, 2020	Approved
JetBrains dotPeek 2020.2-EAP7	81	Saturday, July 18, 2020	Approved
JetBrains dotPeek 2020.2-EAP6	92	Saturday, July 11, 2020	Approved
JetBrains dotPeek 2020.2-EAP5	103	Saturday, July 4, 2020	Approved
JetBrains dotPeek 2020.2-EAP4	117	Friday, June 26, 2020	Approved
JetBrains dotPeek 2020.2-EAP3	112	Saturday, June 20, 2020	Approved
JetBrains dotPeek 2020.2-EAP2	119	Friday, June 12, 2020	Approved
JetBrains dotPeek 2020.2-EAP1	119	Tuesday, June 9, 2020	Approved
JetBrains dotPeek 2020.1.4	3053	Friday, July 10, 2020	Approved
JetBrains dotPeek 2020.1.3	3864	Tuesday, May 19, 2020	Approved
JetBrains dotPeek 2020.1.2	1285	Friday, May 8, 2020	Approved
JetBrains dotPeek 2020.1.1	1020	Thursday, April 30, 2020	Approved
JetBrains dotPeek 2020.1	1483	Friday, April 17, 2020	Approved
JetBrains dotPeek 2020.1-EAP8	96	Thursday, April 9, 2020	Approved
JetBrains dotPeek 2020.1-EAP7	126	Saturday, April 4, 2020	Approved
JetBrains dotPeek 2020.1-EAP6	98	Friday, March 27, 2020	Approved
JetBrains dotPeek 2020.1-EAP5	124	Friday, March 20, 2020	Approved
JetBrains dotPeek 2020.1-EAP4	110	Friday, March 13, 2020	Approved
JetBrains dotPeek 2020.1-EAP3	112	Wednesday, March 11, 2020	Approved
JetBrains dotPeek 2020.1-EAP2	103	Wednesday, March 4, 2020	Approved
JetBrains dotPeek 2020.1-EAP1	92	Friday, February 28, 2020	Approved
JetBrains dotPeek 2019.3.4	4657	Saturday, February 29, 2020	Approved
JetBrains dotPeek 2019.3.3	1006	Friday, February 21, 2020	Approved
JetBrains dotPeek 2019.3.2	1055	Thursday, February 13, 2020	Approved
JetBrains dotPeek 2019.3.1	4193	Saturday, December 21, 2019	Approved
JetBrains dotPeek 2019.3	1013	Wednesday, December 11, 2019	Approved
JetBrains dotPeek 2019.3-EAP7	157	Friday, November 29, 2019	Approved
JetBrains dotPeek 2019.3-EAP6	145	Sunday, November 24, 2019	Approved
JetBrains dotPeek 2019.3-EAP5	167	Saturday, November 23, 2019	Approved
JetBrains dotPeek 2019.3-EAP4	127	Friday, November 15, 2019	Approved
JetBrains dotPeek 2019.3-EAP3	136	Friday, November 8, 2019	Approved
JetBrains dotPeek 2019.3-EAP2	130	Tuesday, November 5, 2019	Approved
JetBrains dotPeek 2019.3-EAP1	152	Saturday, October 26, 2019	Approved
JetBrains dotPeek 2019.2.3	4323	Saturday, October 19, 2019	Approved
JetBrains dotPeek 2019.2.2	4351	Friday, August 30, 2019	Approved
JetBrains dotPeek 2019.2.1	1406	Wednesday, August 21, 2019	Approved
JetBrains dotPeek 2019.2	1666	Friday, August 9, 2019	Approved
JetBrains dotPeek 2019.2-EAP6	194	Thursday, August 1, 2019	Approved
JetBrains dotPeek 2019.2-EAP5	161	Friday, July 26, 2019	Approved
JetBrains dotPeek 2019.2-EAP4	146	Friday, July 19, 2019	Approved
JetBrains dotPeek 2019.2-EAP3	153	Tuesday, July 16, 2019	Approved
JetBrains dotPeek 2019.2-EAP2	145	Saturday, July 6, 2019	Approved
JetBrains dotPeek 2019.2-EAP1	157	Wednesday, July 3, 2019	Approved
JetBrains dotPeek 2019.1.3	2329	Thursday, July 11, 2019	Approved
JetBrains dotPeek 2019.1.2	2602	Thursday, June 6, 2019	Approved
JetBrains dotPeek 2019.1.1	3226	Friday, May 3, 2019	Approved
JetBrains dotPeek 2019.1	791	Wednesday, May 1, 2019	Approved
JetBrains dotPeek 2019.1-EAP7	142	Saturday, April 20, 2019	Approved
JetBrains dotPeek 2019.1-EAP6	144	Friday, April 12, 2019	Approved
JetBrains dotPeek 2019.1-EAP5	126	Saturday, April 6, 2019	Approved
JetBrains dotPeek 2019.1-EAP4	138	Wednesday, April 3, 2019	Approved
JetBrains dotPeek 2019.1-EAP3	139	Thursday, March 28, 2019	Approved
JetBrains dotPeek 2019.1-EAP2	149	Thursday, March 21, 2019	Approved
JetBrains dotPeek 2019.1-EAP1	185	Saturday, March 16, 2019	Approved
JetBrains dotPeek 2018.3.4	7190	Wednesday, March 6, 2019	Approved
JetBrains dotPeek 2018.3.3	2002	Tuesday, February 12, 2019	Approved
JetBrains dotPeek 2018.3.2	1129	Thursday, January 31, 2019	Approved
JetBrains dotPeek 2018.3.1	2207	Friday, December 28, 2018	Approved
JetBrains dotPeek 2018.3	711	Wednesday, December 19, 2018	Approved
JetBrains dotPeek 2018.3-EAP9	182	Thursday, December 13, 2018	Approved
JetBrains dotPeek 2018.3-EAP8	148	Sunday, December 9, 2018	Approved
JetBrains dotPeek 2018.3-EAP7	169	Wednesday, November 28, 2018	Approved
JetBrains dotPeek 2018.3-EAP6	186	Wednesday, November 21, 2018	Approved
JetBrains dotPeek 2018.3-EAP5	182	Wednesday, November 7, 2018	Approved
JetBrains dotPeek 2018.3-EAP4	203	Friday, October 26, 2018	Approved
JetBrains dotPeek 2018.3-EAP3	175	Friday, October 19, 2018	Approved
JetBrains dotPeek 2018.3-EAP2	154	Tuesday, October 16, 2018	Approved
JetBrains dotPeek 2018.3-EAP1	165	Tuesday, October 9, 2018	Approved
JetBrains dotPeek 2018.2.3	2861	Friday, September 14, 2018	Approved
JetBrains dotPeek 2018.2.2	277	Wednesday, September 12, 2018	Approved
JetBrains dotPeek 2018.2.1	507	Friday, August 31, 2018	Approved
JetBrains dotPeek 2018.2	519	Saturday, August 25, 2018	Approved
JetBrains dotPeek 2018.2-EAP8	252	Friday, August 17, 2018	Exempted
JetBrains dotPeek 2018.2-EAP7	258	Saturday, August 11, 2018	Exempted
JetBrains dotPeek 2018.2-EAP6	206	Saturday, August 4, 2018	Exempted
JetBrains dotPeek 2018.1.4	938	Friday, August 3, 2018	Approved
JetBrains dotPeek 2018.1.3	1064	Friday, July 6, 2018	Approved
JetBrains dotPeek 2018.1.2	1142	Friday, June 1, 2018	Approved
JetBrains dotPeek 2018.1.1	470	Tuesday, May 29, 2018	Approved
JetBrains dotPeek 2018.1	1139	Sunday, April 22, 2018	Approved
JetBrains dotPeek 2017.3.5 2017.3.5	860	Friday, March 23, 2018	Approved
JetBrains dotPeek 2017.3.4 2017.3.4	382	Friday, March 23, 2018	Approved
JetBrains dotPeek 2017.3.3 2017.3.3	869	Friday, March 2, 2018	Approved
JetBrains dotPeek 2017.3.2 2017.3.2	1035	Thursday, February 1, 2018	Approved
JetBrains dotPeek 2017.3.2 EAP 2017.3.2-eap	273	Thursday, January 25, 2018	Exempted
JetBrains dotPeek 2017.3.1 2017.3.1	927	Friday, December 22, 2017	Approved
JetBrains dotPeek 2017.3 2017.3.0	456	Tuesday, December 19, 2017	Approved
JetBrains dotPeek 2017.3 EAP 9 2017.3.0-eap09	291	Thursday, December 7, 2017	Exempted
JetBrains dotPeek 2017.3 EAP 8 2017.3.0-eap08	268	Friday, December 1, 2017	Exempted
JetBrains dotPeek 2017.3 EAP 7 2017.3.0-eap07	263	Friday, November 24, 2017	Exempted
JetBrains dotPeek 2017.3 EAP 6 2017.3.0-eap06	276	Friday, November 17, 2017	Exempted
JetBrains dotPeek 2017.3 EAP 5 2017.3.0-eap05	306	Sunday, November 12, 2017	Exempted
JetBrains dotPeek 2017.3 EAP 4 2017.3.0-eap04	294	Thursday, November 2, 2017	Exempted
JetBrains dotPeek 2017.3 EAP 3 2017.3.0-eap03	285	Friday, October 27, 2017	Exempted
JetBrains dotPeek 2017.3 EAP 1 2017.3.0-eap01	283	Tuesday, October 24, 2017	Exempted
JetBrains dotPeek 2017.2.2 2017.2.2	1301	Friday, October 6, 2017	Approved
JetBrains dotPeek 2017.2.1 2017.2.1	883	Thursday, September 21, 2017	Approved
JetBrains dotPeek 2017.2 2017.2.0	876	Thursday, August 24, 2017	Approved
JetBrains dotPeek 2017.2 EAP 13 2017.2.0-eap13	345	Saturday, August 19, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 12 2017.2.0-eap12	322	Monday, August 14, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 11 2017.2.0-eap11	342	Friday, August 4, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 10 2017.2.0-eap10	338	Thursday, July 27, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 9 2017.2.0-eap09	345	Thursday, July 20, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 8 2017.2.0-eap08	357	Friday, July 14, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 7 2017.2.0-eap07	317	Thursday, July 6, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 6 2017.2.0-eap06	322	Friday, June 30, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 5 2017.2.0-eap05	308	Tuesday, June 27, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 4 2017.2.0-eap04	353	Monday, June 26, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 3 2017.2.0-eap03	301	Friday, June 9, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 2 2017.2.0-eap02	333	Thursday, June 8, 2017	Exempted
JetBrains dotPeek 2017.2 EAP 1 2017.2.0-eap01	378	Thursday, June 1, 2017	Exempted
JetBrains dotPeek 2017.1.3 2017.1.3.0	1699	Wednesday, June 14, 2017	Approved
JetBrains dotPeek 2017.1.2 2017.1.2.0	1218	Friday, April 28, 2017	Approved
JetBrains dotPeek 2017.1.1 2017.1.1.0	858	Friday, April 7, 2017	Approved
JetBrains dotPeek 2017.1 2017.1.0.0	536	Monday, April 3, 2017	Approved
JetBrains dotPeek 2017.1 EAP 8 2017.1.0.0-eap08	379	Thursday, March 30, 2017	Exempted
JetBrains dotPeek 2017.1 EAP 7 2017.1.0.0-eap07	313	Tuesday, March 28, 2017	Exempted
JetBrains dotPeek 2017.1 EAP 6 2017.1.0.0-eap06	337	Thursday, March 23, 2017	Exempted
JetBrains dotPeek 2017.1 EAP 5 2017.1.0.0-eap05	367	Thursday, March 16, 2017	Exempted
JetBrains dotPeek 2017.1 EAP 4 2017.1.0.0-eap04	319	Thursday, March 9, 2017	Exempted
JetBrains dotPeek 2017.1 EAP 3 2017.1.0.0-eap03	384	Tuesday, February 28, 2017	Exempted
JetBrains dotPeek 2017.1 EAP 2 2017.1.0.0-eap02	337	Friday, February 17, 2017	Exempted
JetBrains dotPeek 2017.1 EAP 1 2017.1.0.0-eap01	363	Thursday, February 9, 2017	Exempted
JetBrains dotPeek 2016.3.2 2016.3.2.0	1675	Thursday, January 26, 2017	Approved
JetBrains dotPeek 2016.3.1 2016.3.1.0	977	Friday, December 23, 2016	Approved
JetBrains dotPeek 2016.3 2016.3.0.0	561	Thursday, December 15, 2016	Approved
JetBrains dotPeek 2016.3 RC 2016.3.0.0-rc	345	Thursday, December 8, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 9 2016.3.0.0-eap9	353	Wednesday, November 16, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 8 2016.3.0.0-eap8	387	Thursday, November 10, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 7 2016.3.0.0-eap7	354	Friday, November 4, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 6 2016.3.0.0-eap6	332	Thursday, October 27, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 5 2016.3.0.0-eap5	317	Thursday, October 20, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 4 2016.3.0.0-eap4	418	Thursday, October 13, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 3 2016.3.0.0-eap3	409	Thursday, October 6, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 2 2016.3.0.0-eap2	373	Thursday, September 29, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 11 2016.3.0.0-eap11	342	Thursday, December 1, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 10 2016.3.0.0-eap10	314	Thursday, November 24, 2016	Exempted
JetBrains dotPeek 2016.3 EAP 1 2016.3.0.0-eap1	381	Thursday, September 22, 2016	Exempted
JetBrains dotPeek 2016.2.2 2016.2.2.0	2225	Tuesday, September 13, 2016	Approved
JetBrains dotPeek 2016.2.1 2016.2.1.0	402	Monday, September 12, 2016	Approved
JetBrains dotPeek 2016.2 2016.2.0.0	839	Thursday, August 18, 2016	Approved
JetBrains dotPeek 2016.2 RC 2016.2.0.0-rc	376	Thursday, August 11, 2016	Approved
JetBrains dotPeek 2016.2 EAP 9 2016.2.0.0-eap9	373	Thursday, July 21, 2016	Approved
JetBrains dotPeek 2016.2 EAP 8 2016.2.0.0-eap8	366	Thursday, July 14, 2016	Approved
JetBrains dotPeek 2016.2 EAP 7 2016.2.0.0-eap7	410	Thursday, July 7, 2016	Approved
JetBrains dotPeek 2016.2 EAP 6 2016.2.0.0-eap6	397	Thursday, June 30, 2016	Approved
JetBrains dotPeek 2016.2 EAP 5 2016.2.0.0-eap5	424	Thursday, June 23, 2016	Approved
JetBrains dotPeek 2016.2 EAP 4 2016.2.0.0-eap4	406	Thursday, June 16, 2016	Approved
JetBrains dotPeek 2016.2 EAP 3 2016.2.0.0-eap3	390	Thursday, June 9, 2016	Approved
JetBrains dotPeek 2016.2 EAP 2 2016.2.0.0-eap2	305	Thursday, June 2, 2016	Approved
JetBrains dotPeek 2016.2 EAP 11 2016.2.0.0-eap11	374	Thursday, August 4, 2016	Approved
JetBrains dotPeek 2016.2 EAP 10 2016.2.0.0-eap10	325	Thursday, July 28, 2016	Approved
JetBrains dotPeek 2016.2 EAP 1 2016.2.0.0-eap1	427	Thursday, May 26, 2016	Approved
JetBrains dotPeek 2016.1.2 2016.1.2.0	743	Monday, May 23, 2016	Approved
JetBrains dotPeek 2016.1.1 2016.1.1.0	300	Wednesday, May 4, 2016	Approved
JetBrains dotPeek 2016.1 2016.1.0.0	747	Thursday, April 14, 2016	Approved
JetBrains dotPeek 2016.1 EAP 9 2016.1.0.0-eap9	351	Friday, April 8, 2016	Approved
JetBrains dotPeek 2016.1 EAP 8 2016.1.0.0-eap8	336	Thursday, March 31, 2016	Approved
JetBrains dotPeek 2016.1 EAP 7 2016.1.0.0-eap7	293	Sunday, March 20, 2016	Approved
JetBrains dotPeek 2016.1 EAP 10 2016.1.0.0-eap10	388	Sunday, April 10, 2016	Approved
JetBrains dotPeek 10.1 EAP 6 10.1.0.0-eap6	354	Sunday, March 13, 2016	Approved
JetBrains dotPeek 10.1 EAP 5 10.1.0.0-eap5	365	Monday, March 7, 2016	Approved
JetBrains dotPeek 10.1 EAP 4 10.1.0.0-eap4	367	Monday, February 29, 2016	Approved
JetBrains dotPeek 10.0.2 10.0.2.0	2046	Wednesday, December 30, 2015	Approved
dotPeek 10.0.1	1066	Tuesday, November 17, 2015	Approved
JetBrains dotPeek 10.0.1 10.0.1.0	338	Wednesday, November 18, 2015	Approved
JetBrains dotPeek 10 10.0.0.0	663	Tuesday, November 3, 2015	Approved
JetBrains dotPeek 2.0 EAP 2 2.0.0.0-EAP2	415	Thursday, September 24, 2015	Approved
dotPeek 1.5	1636	Thursday, August 20, 2015	Approved
JetBrains dotPeek 1.5 1.5.0.0	361	Thursday, August 27, 2015	Approved
dotPeek 1.4.3	597	Saturday, July 25, 2015	Approved
dotPeek 1.4.2	364	Wednesday, July 22, 2015	Approved
dotPeek 1.4.1	398	Saturday, June 27, 2015	Approved
dotPeek 1.3	5035	Friday, December 5, 2014	Approved
dotPeek 1.2.1.226	2842	Friday, July 18, 2014	Approved
dotPeek 1.1.1.33	3292	Thursday, October 3, 2013	Approved
dotPeek 1.0.0.8644	1906	Saturday, October 27, 2012	Approved
dotPeek 1.0.0.7001	912	Thursday, January 26, 2012	Approved

JetBrains s.r.o.

Dependencies

- resharper-platform (= 105.0.20160229.164303-eap4)

Discussion for the JetBrains dotPeek 10.1 EAP 4 Package

Ground Rules:

This discussion is only about JetBrains dotPeek 10.1 EAP 4 and the JetBrains dotPeek 10.1 EAP 4 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 JetBrains dotPeek 10.1 EAP 4, 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.

197,123

367

29 Feb 2016

JetBrains dotPeek 10.1 EAP 4

1 2 3 JetBrains dotPeek 10.1 EAP 4 10.1.0.0-eap4

This Package Contains an Exempted Check

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Ground Rules:

1

2

3

JetBrains dotPeek 10.1 EAP 4 10.1.0.0-eap4