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.12.1.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.12.1.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.12.1.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.12.1.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:

38,517

Downloads of v 2021.3-EAP8:

43

Last Update:

17 Nov 2021

Package Maintainer(s):

Software Author(s):

JetBrains

Tags:

jetbrains developer admin visualstudio

JetBrains ReSharper C++

This is a prerelease version of JetBrains ReSharper C++.

2021.3-EAP8 | Updated: 17 Nov 2021

Downloads:

38,517

Downloads of v 2021.3-EAP8:

Maintainer(s):

Software Author(s):

JetBrains

Tags:

jetbrains developer admin visualstudio

1

2

3

JetBrains ReSharper C++ 2021.3-EAP8

This is a prerelease version of JetBrains ReSharper C++.

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 ReSharper C++, run the following command from the command line or from PowerShell:

To upgrade JetBrains ReSharper C++, run the following command from the command line or from PowerShell:

To uninstall JetBrains ReSharper C++, 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 resharpercpp --internalize --version=2021.3-EAP8 --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 resharpercpp -y --source="'INTERNAL REPO URL'" --version="'2021.3-EAP8'" --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 resharpercpp -y --source="'INTERNAL REPO URL'" --version="'2021.3-EAP8'" --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 resharpercpp
  win_chocolatey:
    name: resharpercpp
    version: '2021.3-EAP8'
    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 'resharpercpp' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2021.3-EAP8'
  options  '--prerelease'
end

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


cChocoPackageInstaller resharpercpp
{
    Name        = "resharpercpp"
    Version     = "2021.3-EAP8"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"
}

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


package { 'resharpercpp':
  ensure          => '2021.3-EAP8',
  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 17 Nov 2021.

Description

Visual Studio Extension for C++ Developers

Analyze code quality

ReSharper C++ highlights code issues in the editor and provides quick-fixes to improve code in one way or another. Unreachable code? Redundant statements? Suspicious object slicing or incorrect format specifier? ReSharper C++ will bring these and other kinds of problems to your attention and help you fix them.

Find usages and navigate code

You can instantly jump at any file, type, or type member in solution. You can search for usages of any code and enjoy a clear view of found usages, with grouping and preview options. Last but not least, you can go from any code symbol to its declaration or definition, its base or derived symbols.

Refactor and transform code

Code refactorings for C++ help safely change your code base, which is especially important in a language as non-trivial as C++. Context actions help switch between alternative syntax constructs and serve as shortcuts to code generation actions.

Generate common code

Code that ReSharper C++ can generate for you includes definitions, missing and overriding members, equality and relational operators, hash and swap functions. Add dozens of customizable templates, and you have the tools to deal with boilerplate code faster than ever.

Run and manage unit tests

ReSharper C++ supports running Google Test and Boost.Test based unit tests in Visual Studio. You can run and debug unit tests contextually, right from the text editor. Dedicated tool windows help you view, group, filter and run unit tests, create and manage unit test sessions.

Use a consistent code style

Configure code formatting options and naming style, share settings with your teammates, and maintaining a consistent code style should never be a problem again.

Files

tools\chocolateybeforemodify.ps1

# Stop any JetBrains ETW provider services
Get-Service | Where-Object { $_.Name -like "JetBrainsETW*" } | Stop-Service

tools\chocolateyinstall.ps1

$ErrorActionPreference = 'Stop'; # stop on all errors

$filename = 'JetBrains.dotUltimate.2021.3.EAP8.Checked.exe'

$platformPackageName = 'resharper-platform'

$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$installPath = Join-Path  (Join-Path $commonPath $platformPackageName) $filename
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  fileType      = 'exe'
  file          = $installPath
  silentArgs    = "/Silent=True /SpecificProductNames=ReSharperCpp /VsVersion=*"
  validExitCodes= @(0)
  softwareName  = 'ReSharper C++'
}
Install-ChocolateyInstallPackage @packageArgs

tools\chocolateyuninstall.ps1

$ErrorActionPreference = 'Stop'; # stop on all errors

$filename = 'JetBrains.dotUltimate.2021.3.EAP8.Checked.exe'

$platformPackageName = 'resharper-platform'

$scriptPath = $(Split-Path -parent $MyInvocation.MyCommand.Definition)
$commonPath = $(Split-Path -parent $(Split-Path -parent $scriptPath))
$installPath = Join-Path  (Join-Path $commonPath $platformPackageName) $filename
Uninstall-ChocolateyPackage $env:ChocolateyPackageName 'exe' '/Silent=True /SpecificProductNamesToRemove=ReSharperCpp /VsVersion=*' $installPath

Virus Scan Results

ReSharperCpp.2021.3-EAP8.nupkg (c4a977397f16) - ## / 59

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 ReSharper C++ 2021.3.2	31	Saturday, December 25, 2021	Approved
JetBrains ReSharper C++ 2021.3.1	29	Saturday, December 11, 2021	Approved
JetBrains ReSharper C++ 2021.3	55	Thursday, December 9, 2021	Approved
JetBrains ReSharper C++ 2021.3-EAP9	17	Monday, November 22, 2021	Approved
JetBrains ReSharper C++ 2021.3-EAP8	43	Wednesday, November 17, 2021	Approved
JetBrains ReSharper C++ 2021.3-EAP7	83	Tuesday, November 9, 2021	Approved
JetBrains ReSharper C++ 2021.3-EAP6	34	Saturday, October 30, 2021	Approved
JetBrains ReSharper C++ 2021.3-EAP5	19	Saturday, October 23, 2021	Approved
JetBrains ReSharper C++ 2021.3-EAP4	43	Friday, October 15, 2021	Approved
JetBrains ReSharper C++ 2021.3-EAP3	20	Tuesday, October 12, 2021	Approved
JetBrains ReSharper C++ 2021.3-EAP2	26	Tuesday, October 5, 2021	Approved
JetBrains ReSharper C++ 2021.3-EAP1	35	Wednesday, September 29, 2021	Approved
JetBrains ReSharper C++ 2021.2.2	39	Thursday, October 14, 2021	Approved
JetBrains ReSharper C++ 2021.2.1	47	Saturday, August 28, 2021	Approved
JetBrains ReSharper C++ 2021.2	140	Wednesday, August 4, 2021	Approved
JetBrains ReSharper C++ 2021.2-EAP9	49	Friday, July 30, 2021	Approved
JetBrains ReSharper C++ 2021.2-EAP8	64	Friday, July 23, 2021	Approved
JetBrains ReSharper C++ 2021.2-EAP7	28	Tuesday, July 20, 2021	Approved
JetBrains ReSharper C++ 2021.2-EAP6	35	Saturday, July 10, 2021	Approved
JetBrains ReSharper C++ 2021.2-EAP5	29	Friday, July 2, 2021	Approved
JetBrains ReSharper C++ 2021.2-EAP4	30	Saturday, June 26, 2021	Approved
JetBrains ReSharper C++ 2021.2-EAP3	31	Saturday, June 12, 2021	Approved
JetBrains ReSharper C++ 2021.2-EAP2	40	Saturday, June 5, 2021	Approved
JetBrains ReSharper C++ 2021.2-EAP1	30	Tuesday, June 1, 2021	Approved
JetBrains ReSharper C++ 2021.1.5	90	Friday, July 23, 2021	Approved
JetBrains ReSharper C++ 2021.1.4	37	Thursday, July 15, 2021	Approved
JetBrains ReSharper C++ 2021.1.3	70	Wednesday, May 26, 2021	Approved
JetBrains ReSharper C++ 2021.1.2	56	Saturday, April 24, 2021	Approved
JetBrains ReSharper C++ 2021.1.1	53	Sunday, April 11, 2021	Approved
JetBrains ReSharper C++ 2021.1	41	Friday, April 9, 2021	Approved
JetBrains ReSharper C++ 2021.1-EAP9	34	Friday, March 26, 2021	Approved
JetBrains ReSharper C++ 2021.1-EAP8	30	Friday, March 19, 2021	Approved
JetBrains ReSharper C++ 2021.1-EAP7	46	Friday, March 12, 2021	Approved
JetBrains ReSharper C++ 2021.1-EAP6	37	Friday, March 5, 2021	Approved
JetBrains ReSharper C++ 2021.1-EAP5	40	Saturday, February 27, 2021	Approved
JetBrains ReSharper C++ 2021.1-EAP4	113	Sunday, February 21, 2021	Approved
JetBrains ReSharper C++ 2021.1-EAP3	32	Wednesday, February 17, 2021	Approved
JetBrains ReSharper C++ 2021.1-EAP2	45	Friday, February 5, 2021	Approved
JetBrains ReSharper C++ 2021.1-EAP1	51	Tuesday, February 2, 2021	Approved
JetBrains ReSharper C++ 2020.3.4	51	Thursday, March 18, 2021	Approved
JetBrains ReSharper C++ 2020.3.3	51	Tuesday, February 23, 2021	Approved
JetBrains ReSharper C++ 2020.3.2	99	Thursday, December 31, 2020	Approved
JetBrains ReSharper C++ 2020.3.1	64	Friday, December 25, 2020	Approved
JetBrains ReSharper C++ 2020.3	61	Tuesday, December 15, 2020	Approved
JetBrains ReSharper C++ 2020.3-EAP9	55	Saturday, November 28, 2020	Approved
JetBrains ReSharper C++ 2020.3-EAP8	44	Friday, November 20, 2020	Approved
JetBrains ReSharper C++ 2020.3-EAP7	66	Saturday, November 14, 2020	Approved
JetBrains ReSharper C++ 2020.3-EAP6	65	Friday, November 6, 2020	Approved
JetBrains ReSharper C++ 2020.3-EAP5	60	Friday, October 30, 2020	Approved
JetBrains ReSharper C++ 2020.3-EAP4	73	Saturday, October 17, 2020	Approved
JetBrains ReSharper C++ 2020.3-EAP3	61	Friday, October 9, 2020	Approved
JetBrains ReSharper C++ 2020.3-EAP2	55	Friday, October 2, 2020	Approved
JetBrains ReSharper C++ 2020.3-EAP1	75	Friday, September 25, 2020	Approved
JetBrains ReSharper C++ 2020.2.4	99	Friday, October 2, 2020	Approved
JetBrains ReSharper C++ 2020.2.3	76	Saturday, September 19, 2020	Approved
JetBrains ReSharper C++ 2020.2.2	80	Friday, September 11, 2020	Approved
JetBrains ReSharper C++ 2020.2.1	100	Saturday, August 22, 2020	Approved
JetBrains ReSharper C++ 2020.2	86	Thursday, August 13, 2020	Approved
JetBrains ReSharper C++ 2020.2-EAP9	77	Friday, August 7, 2020	Approved
JetBrains ReSharper C++ 2020.2-EAP8	84	Saturday, July 25, 2020	Approved
JetBrains ReSharper C++ 2020.2-EAP7	67	Saturday, July 18, 2020	Approved
JetBrains ReSharper C++ 2020.2-EAP6	84	Saturday, July 11, 2020	Approved
JetBrains ReSharper C++ 2020.2-EAP5	72	Saturday, July 4, 2020	Approved
JetBrains ReSharper C++ 2020.2-EAP4	79	Friday, June 26, 2020	Approved
JetBrains ReSharper C++ 2020.2-EAP3	66	Saturday, June 20, 2020	Approved
JetBrains ReSharper C++ 2020.2-EAP2	67	Friday, June 12, 2020	Approved
JetBrains ReSharper C++ 2020.2-EAP1	68	Tuesday, June 9, 2020	Approved
JetBrains ReSharper C++ 2020.1.4	120	Friday, July 10, 2020	Approved
JetBrains ReSharper C++ 2020.1.3	101	Tuesday, May 19, 2020	Approved
JetBrains ReSharper C++ 2020.1.2	106	Friday, May 8, 2020	Approved
JetBrains ReSharper C++ 2020.1.1	113	Thursday, April 30, 2020	Approved
JetBrains ReSharper C++ 2020.1	103	Friday, April 17, 2020	Approved
JetBrains ReSharper C++ 2020.1-EAP8	74	Thursday, April 9, 2020	Approved
JetBrains ReSharper C++ 2020.1-EAP7	79	Saturday, April 4, 2020	Approved
JetBrains ReSharper C++ 2020.1-EAP6	75	Friday, March 27, 2020	Exempted
JetBrains ReSharper C++ 2020.1-EAP5	82	Friday, March 20, 2020	Exempted
JetBrains ReSharper C++ 2020.1-EAP4	86	Friday, March 13, 2020	Exempted
JetBrains ReSharper C++ 2020.1-EAP3	104	Wednesday, March 11, 2020	Exempted
JetBrains ReSharper C++ 2020.1-EAP2	119	Wednesday, March 4, 2020	Exempted
JetBrains ReSharper C++ 2020.1-EAP1	85	Friday, February 28, 2020	Exempted
JetBrains ReSharper C++ 2019.3.4	117	Monday, March 30, 2020	Approved
JetBrains ReSharper C++ 2019.3.3	120	Monday, March 30, 2020	Approved
JetBrains ReSharper C++ 2019.3.2	101	Monday, March 30, 2020	Approved
JetBrains ReSharper C++ 2019.3.1	231	Saturday, December 21, 2019	Approved
JetBrains ReSharper C++ 2019.3	109	Wednesday, December 11, 2019	Approved
JetBrains ReSharper C++ 2019.3-EAP7	86	Friday, November 29, 2019	Approved
JetBrains ReSharper C++ 2019.3-EAP6	82	Sunday, November 24, 2019	Approved
JetBrains ReSharper C++ 2019.3-EAP5	80	Saturday, November 23, 2019	Approved
JetBrains ReSharper C++ 2019.3-EAP4	84	Friday, November 15, 2019	Approved
JetBrains ReSharper C++ 2019.3-EAP3	91	Friday, November 8, 2019	Approved
JetBrains ReSharper C++ 2019.3-EAP2	83	Tuesday, November 5, 2019	Approved
JetBrains ReSharper C++ 2019.3-EAP1	106	Saturday, October 26, 2019	Approved
JetBrains ReSharper C++ 2019.2.3	113	Saturday, October 19, 2019	Approved
JetBrains ReSharper C++ 2019.2.2	163	Friday, August 30, 2019	Approved
JetBrains ReSharper C++ 2019.2.1	127	Wednesday, August 21, 2019	Approved
JetBrains ReSharper C++ 2019.2	137	Friday, August 9, 2019	Approved
JetBrains ReSharper C++ 2019.2-EAP6	116	Thursday, August 1, 2019	Approved
JetBrains ReSharper C++ 2019.2-EAP5	87	Friday, July 26, 2019	Approved
JetBrains ReSharper C++ 2019.2-EAP4	118	Friday, July 19, 2019	Approved
JetBrains ReSharper C++ 2019.2-EAP3	131	Tuesday, July 16, 2019	Approved
JetBrains ReSharper C++ 2019.2-EAP2	103	Saturday, July 6, 2019	Approved
JetBrains ReSharper C++ 2019.2-EAP1	113	Wednesday, July 3, 2019	Approved
JetBrains ReSharper C++ 2019.1.3	147	Thursday, July 11, 2019	Approved
JetBrains ReSharper C++ 2019.1.2	157	Thursday, June 6, 2019	Approved
JetBrains ReSharper C++ 2019.1.1	148	Friday, May 3, 2019	Approved
JetBrains ReSharper C++ 2019.1	132	Wednesday, May 1, 2019	Approved
JetBrains ReSharper C++ 2019.1-EAP7	113	Saturday, April 20, 2019	Approved
JetBrains ReSharper C++ 2019.1-EAP6	169	Friday, April 12, 2019	Approved
JetBrains ReSharper C++ 2019.1-EAP5	102	Saturday, April 6, 2019	Approved
JetBrains ReSharper C++ 2019.1-EAP4	137	Wednesday, April 3, 2019	Approved
JetBrains ReSharper C++ 2019.1-EAP3	132	Thursday, March 28, 2019	Approved
JetBrains ReSharper C++ 2019.1-EAP2	142	Thursday, March 21, 2019	Approved
JetBrains ReSharper C++ 2019.1-EAP1	123	Saturday, March 16, 2019	Approved
JetBrains ReSharper C++ 2018.3.4	166	Wednesday, March 6, 2019	Approved
JetBrains ReSharper C++ 2018.3.3	170	Tuesday, February 12, 2019	Approved
JetBrains ReSharper C++ 2018.3.2	142	Thursday, January 31, 2019	Approved
JetBrains ReSharper C++ 2018.3.1	176	Friday, December 28, 2018	Approved
JetBrains ReSharper C++ 2018.3	180	Wednesday, December 19, 2018	Approved
JetBrains ReSharper C++ 2018.3-EAP9	124	Thursday, December 13, 2018	Approved
JetBrains ReSharper C++ 2018.3-EAP8	154	Sunday, December 9, 2018	Approved
JetBrains ReSharper C++ 2018.3-EAP7	150	Wednesday, November 28, 2018	Approved
JetBrains ReSharper C++ 2018.3-EAP6	164	Wednesday, November 21, 2018	Approved
JetBrains ReSharper C++ 2018.3-EAP5	145	Wednesday, November 7, 2018	Approved
JetBrains ReSharper C++ 2018.3-EAP4	147	Friday, October 26, 2018	Approved
JetBrains ReSharper C++ 2018.3-EAP3	163	Friday, October 19, 2018	Approved
JetBrains ReSharper C++ 2018.3-EAP2	157	Tuesday, October 16, 2018	Approved
JetBrains ReSharper C++ 2018.3-EAP1	155	Tuesday, October 9, 2018	Approved
JetBrains ReSharper C++ 2018.2.3	215	Friday, September 14, 2018	Approved
JetBrains ReSharper C++ 2018.2.2	160	Wednesday, September 12, 2018	Approved
JetBrains ReSharper C++ 2018.2.1	143	Friday, August 31, 2018	Approved
JetBrains ReSharper C++ 2018.2	173	Saturday, August 25, 2018	Approved
JetBrains ReSharper C++ 2018.2-EAP8	173	Friday, August 17, 2018	Exempted
JetBrains ReSharper C++ 2018.2-EAP7	165	Saturday, August 11, 2018	Exempted
JetBrains ReSharper C++ 2018.2-EAP6	177	Saturday, August 4, 2018	Exempted
JetBrains ReSharper C++ 2018.1.4	203	Friday, August 3, 2018	Approved
JetBrains ReSharper C++ 2018.1.3	187	Sunday, July 29, 2018	Approved
JetBrains ReSharper C++ 2017.3.5 2017.3.5	309	Friday, March 23, 2018	Approved
JetBrains ReSharper C++ 2017.3.4 2017.3.4	295	Friday, March 23, 2018	Approved
JetBrains ReSharper C++ 2017.3.3 2017.3.3	298	Friday, March 2, 2018	Approved
JetBrains ReSharper C++ 2017.3.2 2017.3.2	274	Thursday, February 1, 2018	Approved
JetBrains ReSharper C++ 2017.3.2 EAP 2017.3.2-eap	292	Thursday, January 25, 2018	Exempted
JetBrains ReSharper C++ 2017.3.1 2017.3.1	275	Friday, December 22, 2017	Approved
JetBrains ReSharper C++ 2017.3 2017.3.0	268	Tuesday, December 19, 2017	Approved
JetBrains ReSharper C++ 2017.3 EAP 9 2017.3.0-eap09	247	Thursday, December 7, 2017	Exempted
JetBrains ReSharper C++ 2017.3 EAP 8 2017.3.0-eap08	241	Friday, December 1, 2017	Exempted
JetBrains ReSharper C++ 2017.3 EAP 7 2017.3.0-eap07	239	Friday, November 24, 2017	Exempted
JetBrains ReSharper C++ 2017.3 EAP 6 2017.3.0-eap06	259	Friday, November 17, 2017	Exempted
JetBrains ReSharper C++ 2017.3 EAP 5 2017.3.0-eap05	245	Sunday, November 12, 2017	Exempted
JetBrains ReSharper C++ 2017.3 EAP 4 2017.3.0-eap04	256	Thursday, November 2, 2017	Exempted
JetBrains ReSharper C++ 2017.3 EAP 3 2017.3.0-eap03	287	Friday, October 27, 2017	Exempted
JetBrains ReSharper C++ 2017.3 EAP 1 2017.3.0-eap01	267	Tuesday, October 24, 2017	Exempted
JetBrains ReSharper C++ 2017.2.2 2017.2.2	322	Friday, October 6, 2017	Approved
JetBrains ReSharper C++ 2017.2.1 2017.2.1	280	Thursday, September 21, 2017	Approved
JetBrains ReSharper C++ 2017.2 2017.2.0	304	Thursday, August 24, 2017	Approved
JetBrains ReSharper C++ 2017.2 EAP 13 2017.2.0-eap13	308	Saturday, August 19, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 12 2017.2.0-eap12	307	Monday, August 14, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 11 2017.2.0-eap11	306	Friday, August 4, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 10 2017.2.0-eap10	310	Thursday, July 27, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 9 2017.2.0-eap09	313	Thursday, July 20, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 8 2017.2.0-eap08	318	Friday, July 14, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 7 2017.2.0-eap07	274	Thursday, July 6, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 6 2017.2.0-eap06	348	Friday, June 30, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 5 2017.2.0-eap05	339	Tuesday, June 27, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 4 2017.2.0-eap04	310	Monday, June 26, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 3 2017.2.0-eap03	305	Friday, June 9, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 2 2017.2.0-eap02	288	Thursday, June 8, 2017	Exempted
JetBrains ReSharper C++ 2017.2 EAP 1 2017.2.0-eap01	287	Thursday, June 1, 2017	Exempted
JetBrains ReSharper C++ 2017.1.3 2017.1.3.0	308	Wednesday, June 14, 2017	Approved
JetBrains ReSharper C++ 2017.1.2 2017.1.2.0	310	Friday, April 28, 2017	Approved
JetBrains ReSharper C++ 2016.3.2 2016.3.2.0	367	Thursday, January 26, 2017	Approved
JetBrains ReSharper C++ 2016.3.1 2016.3.1.0	329	Friday, December 23, 2016	Approved
JetBrains ReSharper C++ 2016.3 2016.3.0.0	292	Thursday, December 15, 2016	Approved
JetBrains ReSharper C++ 2016.3 RC 2016.3.0.0-rc	337	Thursday, December 8, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 9 2016.3.0.0-eap9	317	Wednesday, November 16, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 8 2016.3.0.0-eap8	317	Thursday, November 10, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 7 2016.3.0.0-eap7	319	Friday, November 4, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 6 2016.3.0.0-eap6	347	Thursday, October 27, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 5 2016.3.0.0-eap5	324	Thursday, October 20, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 4 2016.3.0.0-eap4	350	Thursday, October 13, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 3 2016.3.0.0-eap3	340	Thursday, October 6, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 2 2016.3.0.0-eap2	317	Thursday, September 29, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 11 2016.3.0.0-eap11	317	Thursday, December 1, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 10 2016.3.0.0-eap10	326	Thursday, November 24, 2016	Exempted
JetBrains ReSharper C++ 2016.3 EAP 1 2016.3.0.0-eap1	324	Thursday, September 22, 2016	Exempted
JetBrains ReSharper C++ 2016.2.2 2016.2.2.0	386	Tuesday, September 13, 2016	Approved
JetBrains ReSharper C++ 2016.2.1 2016.2.1.0	293	Monday, September 12, 2016	Approved
JetBrains ReSharper C++ 2016.2 2016.2.0.0	345	Thursday, August 18, 2016	Approved
JetBrains ReSharper C++ 2016.2 RC 2016.2.0.0-rc	337	Thursday, August 11, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 9 2016.2.0.0-eap9	397	Thursday, July 21, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 8 2016.2.0.0-eap8	235	Thursday, July 14, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 7 2016.2.0.0-eap7	275	Thursday, July 7, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 6 2016.2.0.0-eap6	326	Thursday, June 30, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 5 2016.2.0.0-eap5	295	Thursday, June 23, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 4 2016.2.0.0-eap4	315	Thursday, June 16, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 3 2016.2.0.0-eap3	358	Thursday, June 9, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 2 2016.2.0.0-eap2	278	Thursday, June 2, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 11 2016.2.0.0-eap11	334	Thursday, August 4, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 10 2016.2.0.0-eap10	324	Thursday, July 28, 2016	Approved
JetBrains ReSharper C++ 2016.2 EAP 1 2016.2.0.0-eap1	313	Thursday, May 26, 2016	Approved
JetBrains ReSharper C++ 2016.1.2 2016.1.2.0	308	Monday, May 23, 2016	Approved
JetBrains ReSharper C++ 2016.1.1 2016.1.1.0	303	Wednesday, May 4, 2016	Approved
JetBrains ReSharper C++ 2016.1 2016.1.0.0	346	Thursday, April 14, 2016	Approved
JetBrains ReSharper C++ 2016.1 EAP 9 2016.1.0.0-eap9	361	Friday, April 8, 2016	Approved
JetBrains ReSharper C++ 2016.1 EAP 8 2016.1.0.0-eap8	314	Thursday, March 31, 2016	Approved
JetBrains ReSharper C++ 2016.1 EAP 7 2016.1.0.0-eap7	327	Sunday, March 20, 2016	Approved
JetBrains ReSharper C++ 2016.1 EAP 10 2016.1.0.0-eap10	338	Sunday, April 10, 2016	Approved
JetBrains ReSharper C++ 10.1 EAP 6 10.1.0.0-eap6	303	Sunday, March 13, 2016	Approved
JetBrains ReSharper C++ 10.1 EAP 5 10.1.0.0-eap5	318	Monday, March 7, 2016	Approved
JetBrains ReSharper C++ 10.1 EAP 4 10.1.0.0-eap4	328	Monday, February 29, 2016	Approved
JetBrains ReSharper C++ 10.0.2 10.0.2.0	354	Wednesday, December 30, 2015	Approved
JetBrains ReSharper C++ 10.0.1 10.0.1.0	405	Wednesday, November 18, 2015	Approved
JetBrains ReSharper C++ 10 10.0.0.0	316	Tuesday, November 3, 2015	Approved
JetBrains ReSharper C++ 1.2 EAP 2 1.2.0.0-EAP2	336	Thursday, September 24, 2015	Exempted
JetBrains ReSharper C++ 1.1 1.1.0.0	341	Thursday, August 27, 2015	Approved

JetBrains s.r.o.

Release Notes

https://www.jetbrains.com/resharper-cpp/whatsnew/

Dependencies

- resharper-platform (= 213.0.20211113.74016-eap08)
- dotnet4.6.1 (≥ 4.6.01055.20170308)

Discussion for the JetBrains ReSharper C++ Package

Ground Rules:

This discussion is only about JetBrains ReSharper C++ and the JetBrains ReSharper C++ 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 ReSharper C++, 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.

38,517

43

17 Nov 2021

JetBrains ReSharper C++

1 2 3 JetBrains ReSharper C++ 2021.3-EAP8

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

Analyze code quality

Find usages and navigate code

Refactor and transform code

Generate common code

Run and manage unit tests

Use a consistent code style

Ground Rules:

1

2

3

JetBrains ReSharper C++ 2021.3-EAP8