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

103,351

Downloads of v 13.14.1:

11

Last Update:

12 Nov 2021

Package Maintainer(s):

rsuter

Software Author(s):

Rico Suter

Tags:

OpenAPI Swagger AspNetCore Documentation CodeGen TypeScript WebApi AspNet admin

NSwagStudio

Downloads:

103,351

Downloads of v 13.14.1:

Maintainer(s):

rsuter

Software Author(s):

Rico Suter

Tags:

OpenAPI Swagger AspNetCore Documentation CodeGen TypeScript WebApi AspNet admin

1

2

3

NSwagStudio

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Failed

Details

Scan Testing Pending

This package was rejected on 17 Dec 2021. The reviewer chocolatey-ops has listed the following reason(s):

rsuter (maintainer) on 12 Nov 2021 00:02:22 +00:00:

User 'rsuter' (maintainer) submitted package.

chocolatey-ops (reviewer) on 12 Nov 2021 00:36:58 +00:00:

NSwagStudio has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...
Title (title) matches id exactly. Please consider using something slightly more descriptive for the title in the nuspec. More...

Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
- docsUrl - points to the location of the wiki or docs of the software
- mailingListUrl - points to the forum or email list group for the software
- bugTrackerUrl - points to the location where issues and tickets can be accessed
- projectSourceUrl - points to the location of the underlying software source

Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...
Package automation scripts make use of msiexec. The reviewer will ensure there is a valid reason the package has not used the built-in helpers. More...

chocolatey-ops (reviewer) on 12 Nov 2021 00:41:11 +00:00:

NSwagStudio has failed automated package testing (verification).
Please visit https://gist.github.com/08e756cce0d9b02320bf454f58e4d197 for details.
The package status will be changed and will be waiting on your next actions.

NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
Please log in and leave a review comment if you have questions and/or comments.
If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 02 Dec 2021 00:41:16 +00:00:

We've found NSwagStudio v13.14.1 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

Log in to the site and respond to the review comments.
Resubmit fixes for this version.
If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 17 Dec 2021 00:43:21 +00:00:

Unfortunately there has not been progress to move NSwagStudio v13.14.1 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

NSwag: The OpenAPI/Swagger API toolchain for .NET and TypeScript

Files

tools\chocolateyInstall.ps1

$packageName = 'NSwagStudio'
$fileType = 'msi'
$silentArgs = '/quiet'
$scriptPath =  $(Split-Path $MyInvocation.MyCommand.Path)
$fileFullPath = Join-Path $scriptPath 'NSwagStudio.msi'

Install-ChocolateyInstallPackage $packageName $fileType $silentArgs $fileFullPath

tools\chocolateyUninstall.ps1

$packageName = "NSwagStudio";
$fileType = 'msi';
$silentArgs = '/qn /norestart'
$validExitCodes = @(0)

$packageGuid = Get-ChildItem HKLM:\SOFTWARE\Classes\Installer\Products |
	Get-ItemProperty -Name 'ProductName' |
	? { $_.ProductName -like $packageName + "*"} |
	Select -ExpandProperty PSChildName -First 1
$properties = Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\$packageGuid\InstallProperties
$file = $properties.LocalPackage

$msiArgs = "/x $file $silentArgs";
Start-ChocolateyProcessAsAdmin "$msiArgs" 'msiexec' -validExitCodes $validExitCodes

tools\LICENSE.txt

From: https://github.com/RicoSuter/NSwag/blob/master/LICENSE.md

LICENSE

The MIT License (MIT)
Copyright (c) 2017 Rico Suter
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

tools\NSwagStudio.msi

md5: E357309EE3FE5E8258D411150AAB2D8A | sha1: EFAD7F3E430C82BEF1E2506D7554E1233B0E2751 | sha256: 4B90BF8E152DDEE5C186C3C79C309E38909828D046759164C8C197322AE913EC | sha512: F32A116B1BE1D28CBFD2D7EE206820EED83C490C066D340CB049FCB727D13FCD521DE4B8F4E2A2DFE7013A8BC5B3492089F95D8E7BFF72274F71D82A60C62475

tools\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
 
The MSI installer should be built by AppVeyor from the NSwag release branch: 
https://ci.appveyor.com/project/rsuter/nswag/build/artifacts

Virus Scan Results

No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.

Version History

Version	Downloads	Last Updated	Status
NSwagStudio 13.15.5	1119	Wednesday, December 15, 2021	Approved
NSwagStudio 13.15.4	198	Tuesday, December 14, 2021	Approved
NSwagStudio 13.15.3	444	Friday, December 10, 2021	Approved
NSwagStudio 13.15.2	25	Friday, December 10, 2021	Approved
NSwagStudio 13.15.1	160	Thursday, December 9, 2021	Approved
NSwagStudio 13.15.0	272	Tuesday, December 7, 2021	Approved
NSwagStudio 13.14.8	400	Wednesday, December 1, 2021	Approved
NSwagStudio 13.14.4	740	Monday, November 15, 2021	Approved
NSwagStudio 13.14.3	225	Friday, November 12, 2021	Approved
NSwagStudio 13.14.0	173	Thursday, November 11, 2021	Approved
NSwagStudio 13.13.2	2415	Friday, August 6, 2021	Approved
NSwagStudio 13.13.1	130	Thursday, August 5, 2021	Approved
NSwagStudio 13.13.0	105	Wednesday, August 4, 2021	Approved
NSwagStudio 13.12.1	688	Thursday, July 22, 2021	Approved
NSwagStudio 13.12.0	394	Tuesday, July 20, 2021	Approved
NSwagStudio 13.11.3	1545	Friday, June 4, 2021	Approved
NSwagStudio 13.11.2	266	Wednesday, June 2, 2021	Approved
NSwagStudio 13.11.1	1036	Friday, May 7, 2021	Approved
NSwagStudio 13.11.0	55	Friday, May 7, 2021	Approved
NSwagStudio 13.10.9	1014	Friday, April 9, 2021	Approved
NSwagStudio 13.10.8	1169	Monday, March 8, 2021	Approved
NSwagStudio 13.10.7	506	Saturday, February 27, 2021	Approved
NSwagStudio 13.10.6	306	Tuesday, February 23, 2021	Approved
NSwagStudio 13.10.5	274	Sunday, February 21, 2021	Approved
NSwagStudio 13.10.4	36	Friday, February 19, 2021	Approved
NSwagStudio 13.10.3	304	Wednesday, February 17, 2021	Approved
NSwagStudio 13.10.2	549	Friday, February 5, 2021	Approved
NSwagStudio 13.10.1	858	Friday, January 15, 2021	Approved
NSwagStudio 13.10.0	69	Friday, January 15, 2021	Approved
NSwagStudio 13.9.4	1351	Thursday, November 19, 2020	Approved
NSwagStudio 13.9.3	197	Tuesday, November 17, 2020	Approved
NSwagStudio 13.9.2	305	Friday, November 13, 2020	Approved
NSwagStudio 13.9.1	61	Thursday, November 12, 2020	Approved
NSwagStudio 13.9.0	323	Wednesday, November 11, 2020	Approved
NSwagStudio 13.8.2	1516	Wednesday, September 30, 2020	Approved
NSwagStudio 13.8.1	237	Monday, September 28, 2020	Approved
NSwagStudio 13.7.4	639	Wednesday, September 16, 2020	Approved
NSwagStudio 13.7.3	300	Monday, September 14, 2020	Approved
NSwagStudio 13.7.2	133	Monday, September 14, 2020	Approved
NSwagStudio 13.7.1	189	Friday, September 11, 2020	Approved
NSwagStudio 13.7.0	1171	Monday, August 3, 2020	Approved
NSwagStudio 13.6.2	1238	Friday, June 26, 2020	Approved
NSwagStudio 13.6.1	638	Thursday, June 11, 2020	Approved
NSwagStudio 13.6.0	677	Friday, May 29, 2020	Approved
NSwagStudio 13.5.0	897	Friday, May 8, 2020	Approved
NSwagStudio 13.4.2	673	Friday, April 17, 2020	Approved
NSwagStudio 13.4.1	564	Thursday, April 16, 2020	Approved
NSwagStudio 13.4.0	238	Wednesday, April 15, 2020	Approved
NSwagStudio 13.3.0	1422	Friday, March 20, 2020	Approved
NSwagStudio 13.2.5	721	Friday, March 6, 2020	Approved
NSwagStudio 13.2.4	179	Friday, March 6, 2020	Approved
NSwagStudio 13.2.3	929	Wednesday, February 12, 2020	Approved
NSwagStudio 13.2.1	951	Monday, January 13, 2020	Approved
NSwagStudio 13.2.0	791	Wednesday, December 18, 2019	Approved
NSwagStudio 13.1.5	998	Wednesday, November 13, 2019	Approved
NSwagStudio 13.1.4	120	Wednesday, November 13, 2019	Approved
NSwagStudio 13.1.3	1006	Thursday, October 10, 2019	Approved
NSwagStudio 13.1.2	541	Friday, September 27, 2019	Approved
NSwagStudio 13.0.6	1117	Thursday, August 22, 2019	Approved
NSwagStudio 13.0.5	381	Friday, August 16, 2019	Approved
NSwagStudio 13.0.4	944	Friday, July 5, 2019	Approved
NSwagStudio 13.0.3	417	Friday, June 28, 2019	Approved
NSwagStudio 13.0.2	426	Friday, June 21, 2019	Approved
NSwagStudio 13.0.1	419	Thursday, June 13, 2019	Approved
NSwagStudio 13.0.0	298	Tuesday, June 11, 2019	Approved
NSwagStudio 12.3.1	840	Tuesday, May 21, 2019	Approved
NSwagStudio 12.3.0	221	Tuesday, May 21, 2019	Approved
NSwagStudio 12.2.5	542	Friday, May 3, 2019	Approved
NSwagStudio 12.2.4	359	Friday, April 26, 2019	Approved
NSwagStudio 12.2.3	327	Tuesday, April 23, 2019	Approved
NSwagStudio 12.2.2	145	Tuesday, April 23, 2019	Approved
NSwagStudio 12.2.1	159	Tuesday, April 23, 2019	Approved
NSwagStudio 12.2.0	261	Sunday, April 21, 2019	Approved
NSwagStudio 12.1.0	525	Tuesday, April 2, 2019	Approved
NSwagStudio 12.0.20	278	Saturday, March 30, 2019	Approved
NSwagStudio 12.0.19	147	Friday, March 29, 2019	Approved
NSwagStudio 12.0.18	365	Sunday, March 24, 2019	Approved
NSwagStudio 12.0.17	237	Wednesday, March 20, 2019	Approved
NSwagStudio 12.0.16	259	Tuesday, March 19, 2019	Approved
NSwagStudio 12.0.15	500	Monday, March 4, 2019	Approved
NSwagStudio 12.0.14	576	Thursday, February 14, 2019	Approved
NSwagStudio 12.0.13	583	Friday, January 25, 2019	Approved
NSwagStudio 12.0.12	419	Wednesday, January 16, 2019	Approved
NSwagStudio 12.0.11	405	Wednesday, January 9, 2019	Approved
NSwagStudio 12.0.10	302	Thursday, January 3, 2019	Approved
NSwagStudio 12.0.9	355	Thursday, December 20, 2018	Approved
NSwagStudio 12.0.8	226	Wednesday, December 19, 2018	Approved
NSwagStudio 12.0.7	322	Thursday, December 13, 2018	Approved
NSwagStudio 12.0.6	181	Wednesday, December 12, 2018	Approved
NSwagStudio 12.0.5	331	Friday, December 7, 2018	Approved
NSwagStudio 12.0.4	339	Friday, November 30, 2018	Approved
NSwagStudio 12.0.3	280	Tuesday, November 27, 2018	Approved
NSwagStudio 12.0.2	160	Tuesday, November 27, 2018	Approved
NSwagStudio 12.0.1	248	Monday, November 26, 2018	Approved
NSwagStudio 12.0.0	390	Friday, November 16, 2018	Approved
NSwagStudio 11.20.1	938	Wednesday, October 3, 2018	Approved
NSwagStudio 11.20.0	332	Saturday, September 29, 2018	Approved
NSwagStudio 11.19.2	438	Friday, September 14, 2018	Approved
NSwagStudio 11.19.1	749	Friday, September 7, 2018	Approved
NSwagStudio 11.19.0	257	Wednesday, September 5, 2018	Approved
NSwagStudio 11.18.7	406	Saturday, August 25, 2018	Approved
NSwagStudio 11.18.6	311	Wednesday, August 15, 2018	Approved
NSwagStudio 11.18.5	255	Friday, August 10, 2018	Approved
NSwagStudio 11.18.4	190	Thursday, August 9, 2018	Approved
NSwagStudio 11.18.3	193	Wednesday, August 8, 2018	Approved
NSwagStudio 11.18.2	247	Monday, August 6, 2018	Approved
NSwagStudio 11.18.1	212	Friday, August 3, 2018	Approved
NSwagStudio 11.18.0	258	Monday, July 30, 2018	Approved
NSwagStudio 11.17.21	415	Friday, July 13, 2018	Approved
NSwagStudio 11.17.20	248	Wednesday, July 11, 2018	Approved
NSwagStudio 11.17.19	337	Monday, July 2, 2018	Approved
NSwagStudio 11.17.18	237	Thursday, June 28, 2018	Approved
NSwagStudio 11.17.17	210	Tuesday, June 26, 2018	Approved
NSwagStudio 11.17.16	232	Friday, June 22, 2018	Approved
NSwagStudio 11.17.15	521	Thursday, June 14, 2018	Approved
NSwagStudio 11.17.14	246	Wednesday, June 13, 2018	Approved
NSwagStudio 11.17.13	346	Wednesday, June 6, 2018	Approved
NSwagStudio 11.17.12	312	Tuesday, May 29, 2018	Approved
NSwagStudio 11.17.11	237	Monday, May 28, 2018	Approved
NSwagStudio 11.17.10	294	Thursday, May 24, 2018	Approved
NSwagStudio 11.17.9	262	Friday, May 18, 2018	Approved
NSwagStudio 11.17.7	214	Friday, May 18, 2018	Approved
NSwagStudio 11.17.6	227	Wednesday, May 16, 2018	Approved
NSwagStudio 11.17.5	246	Monday, May 14, 2018	Approved
NSwagStudio 11.17.4	255	Saturday, May 12, 2018	Approved
NSwagStudio 11.17.3	1183	Friday, April 27, 2018	Approved
NSwagStudio 11.17.2	594	Friday, April 20, 2018	Approved
NSwagStudio 11.17.1	258	Thursday, April 19, 2018	Approved
NSwagStudio 11.17.0	368	Saturday, April 7, 2018	Approved
NSwagStudio 11.16.1	357	Saturday, March 24, 2018	Approved
NSwagStudio 11.16.0	280	Wednesday, March 21, 2018	Approved
NSwagStudio 11.15.4	406	Sunday, March 4, 2018	Approved
NSwagStudio 11.15.3	400	Wednesday, February 14, 2018	Approved
NSwagStudio 11.15.2	236	Tuesday, February 13, 2018	Approved
NSwagStudio 11.15.1	271	Monday, February 12, 2018	Approved
NSwagStudio 11.15.0	284	Sunday, February 11, 2018	Approved
NSwagStudio 11.14.1	310	Thursday, February 8, 2018	Approved
NSwagStudio 11.14.0	251	Wednesday, February 7, 2018	Approved
NSwagStudio 11.13.3	289	Monday, February 5, 2018	Approved
NSwagStudio 11.13.2	292	Thursday, February 1, 2018	Approved
NSwagStudio 11.13.1	335	Friday, January 26, 2018	Approved
NSwagStudio 11.13.0	248	Thursday, January 25, 2018	Approved
NSwagStudio 11.12.16	706	Friday, December 22, 2017	Approved
NSwagStudio 11.12.15	264	Thursday, December 21, 2017	Approved
NSwagStudio 11.12.14	330	Wednesday, December 20, 2017	Approved
NSwagStudio 11.12.13	394	Wednesday, December 13, 2017	Approved
NSwagStudio 11.12.12	368	Monday, December 11, 2017	Approved
NSwagStudio 11.12.11	318	Friday, December 8, 2017	Approved
NSwagStudio 11.12.10	329	Friday, December 1, 2017	Approved
NSwagStudio 11.12.9	447	Thursday, November 16, 2017	Approved
NSwagStudio 11.12.8	290	Tuesday, November 14, 2017	Approved
NSwagStudio 11.12.7	327	Wednesday, November 8, 2017	Approved
NSwagStudio 11.12.6	275	Wednesday, November 8, 2017	Approved
NSwagStudio 11.12.5	292	Wednesday, November 8, 2017	Approved
NSwagStudio 11.12.4	302	Tuesday, November 7, 2017	Approved
NSwagStudio 11.12.3	302	Tuesday, November 7, 2017	Approved
NSwagStudio 11.12.2	319	Monday, November 6, 2017	Approved
NSwagStudio 11.12.1	223	Monday, November 6, 2017	Approved
NSwagStudio 11.12.0	458	Monday, November 6, 2017	Approved
NSwagStudio 11.5.1.1	686	Wednesday, August 30, 2017	Approved
NSwagStudio 11.5.1	284	Tuesday, August 29, 2017	Approved
NSwagStudio 11.5.0	298	Tuesday, August 29, 2017	Approved
NSwagStudio 11.4.3	348	Thursday, August 24, 2017	Approved
NSwagStudio 11.4.2	301	Wednesday, August 23, 2017	Approved
NSwagStudio 11.4.1	272	Wednesday, August 23, 2017	Approved
NSwagStudio 11.3.5	338	Monday, August 14, 2017	Approved
NSwagStudio 11.3.3	501	Saturday, July 15, 2017	Approved
NSwagStudio 11.3.2	331	Friday, July 14, 2017	Approved
NSwagStudio 11.3.1	297	Thursday, July 13, 2017	Approved
NSwagStudio 11.3.0	354	Monday, July 10, 2017	Approved
NSwagStudio 11.2.0	366	Wednesday, June 28, 2017	Approved
NSwagStudio 11.1.2	359	Tuesday, June 20, 2017	Approved
NSwagStudio 11.1.1	325	Sunday, June 18, 2017	Approved
NSwagStudio 11.1.0	352	Thursday, June 15, 2017	Approved
NSwagStudio 11.0.0	315	Tuesday, June 13, 2017	Approved
NSwagStudio 10.6.0	519	Tuesday, April 25, 2017	Approved
NSwagStudio 10.5.0	358	Friday, April 21, 2017	Approved
NSwagStudio 10.4.0	344	Thursday, April 20, 2017	Approved
NSwagStudio 10.3.0	323	Wednesday, April 19, 2017	Approved
NSwagStudio 10.2.0	336	Tuesday, April 18, 2017	Approved
NSwagStudio 10.1.0	358	Monday, April 10, 2017	Approved
NSwagStudio 10.0.0	304	Friday, April 7, 2017	Approved
NSwagStudio 9.12.0	466	Thursday, March 16, 2017	Approved
NSwagStudio 9.11.0	339	Tuesday, March 14, 2017	Approved
NSwagStudio 9.10.0	363	Thursday, March 9, 2017	Approved
NSwagStudio 9.9.0	309	Tuesday, March 7, 2017	Approved
NSwagStudio 9.8.0	312	Monday, March 6, 2017	Approved
NSwagStudio 9.7.0	360	Friday, March 3, 2017	Approved
NSwagStudio 9.6.0	363	Friday, February 24, 2017	Approved
NSwagStudio 9.5.0	371	Thursday, February 16, 2017	Approved
NSwagStudio 9.4.0	341	Thursday, February 16, 2017	Approved
NSwagStudio 9.2.0	403	Thursday, February 9, 2017	Approved
NSwagStudio 9.1.0	325	Thursday, February 9, 2017	Approved
NSwagStudio 9.0.0	336	Wednesday, February 8, 2017	Approved
NSwagStudio 8.8.0	454	Sunday, January 22, 2017	Approved
NSwagStudio 8.6.0	348	Thursday, January 12, 2017	Approved
NSwagStudio 8.5.0	322	Thursday, January 5, 2017	Approved
NSwagStudio 8.4.0	378	Wednesday, January 4, 2017	Approved
NSwagStudio 8.3.0	354	Friday, December 30, 2016	Approved
NSwagStudio 8.2.0	322	Friday, December 23, 2016	Approved
NSwagStudio 8.1.0	352	Wednesday, December 14, 2016	Approved
NSwagStudio 8.0.0	333	Thursday, December 8, 2016	Approved
NSwagStudio 7.7.0	368	Friday, November 25, 2016	Approved
NSwagStudio 7.6.0	360	Wednesday, November 23, 2016	Approved
NSwagStudio 7.5.0	350	Tuesday, November 22, 2016	Approved
NSwagStudio 7.4.0	295	Tuesday, November 22, 2016	Approved
NSwagStudio 7.3.0	322	Monday, November 21, 2016	Approved
NSwagStudio 7.2.0	312	Sunday, November 20, 2016	Approved
NSwagStudio 7.1.0	374	Monday, November 14, 2016	Approved
NSwagStudio 7.0.0	345	Tuesday, November 8, 2016	Approved
NSwagStudio 6.21.0	369	Wednesday, November 2, 2016	Approved
NSwagStudio 6.20.0	316	Monday, October 31, 2016	Approved
NSwagStudio 6.19.0	271	Monday, October 31, 2016	Approved
NSwagStudio 6.18.0	346	Monday, October 31, 2016	Approved
NSwagStudio 6.17.0	300	Saturday, October 29, 2016	Approved
NSwagStudio 6.16.0	336	Tuesday, October 25, 2016	Approved
NSwagStudio 6.15.0	322	Friday, October 21, 2016	Approved
NSwagStudio 6.14.0	307	Thursday, October 20, 2016	Approved
NSwagStudio 6.13.0	332	Tuesday, October 18, 2016	Approved
NSwagStudio 6.12.0	351	Thursday, October 13, 2016	Approved
NSwagStudio 6.11.0	361	Wednesday, October 12, 2016	Approved
NSwagStudio 6.10.0	311	Tuesday, October 11, 2016	Approved
NSwagStudio 6.9.0	326	Tuesday, October 11, 2016	Approved
NSwagStudio 6.8.0	345	Tuesday, October 11, 2016	Approved
NSwagStudio 6.7.0	317	Tuesday, October 11, 2016	Approved
NSwagStudio 6.6.0	325	Friday, October 7, 2016	Approved
NSwagStudio 6.5.0	298	Wednesday, October 5, 2016	Approved
NSwagStudio 6.4.0	303	Wednesday, October 5, 2016	Approved
NSwagStudio 6.3.0	305	Tuesday, October 4, 2016	Approved
NSwagStudio 6.2.0	299	Monday, October 3, 2016	Approved
NSwagStudio 6.1.0	307	Monday, October 3, 2016	Approved
NSwagStudio 6.0.0	331	Monday, October 3, 2016	Approved
NSwagStudio 5.6.0	385	Thursday, September 8, 2016	Approved
NSwagStudio 5.5.0	338	Tuesday, September 6, 2016	Approved
NSwagStudio 5.4.0	377	Friday, September 2, 2016	Approved
NSwagStudio 5.3.0	303	Monday, August 29, 2016	Approved
NSwagStudio 5.2.0	326	Friday, August 19, 2016	Approved
NSwagStudio 5.1.0	335	Friday, August 19, 2016	Approved
NSwagStudio 5.0.0	319	Thursday, August 18, 2016	Approved
NSwagStudio 4.3.0	326	Tuesday, August 9, 2016	Approved
NSwagStudio 4.2.0	282	Thursday, August 4, 2016	Approved
NSwagStudio 4.1.0	303	Wednesday, August 3, 2016	Approved
NSwagStudio 4.0.0	327	Tuesday, August 2, 2016	Approved
NSwagStudio 3.30.0	331	Tuesday, July 26, 2016	Approved
NSwagStudio 3.29.0	310	Sunday, July 24, 2016	Approved
NSwagStudio 3.28.0	295	Tuesday, July 19, 2016	Approved

Dependencies

This package has no dependencies.

Discussion for the NSwagStudio Package

Ground Rules:

This discussion is only about NSwagStudio and the NSwagStudio 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 NSwagStudio, 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.

103,351

11

12 Nov 2021

NSwagStudio

1 2 3 NSwagStudio

Some Checks Have Failed or Are Not Yet Complete

rsuter (maintainer) on 12 Nov 2021 00:02:22 +00:00:

chocolatey-ops (reviewer) on 12 Nov 2021 00:36:58 +00:00:

Guidelines

Suggestions

Notes

chocolatey-ops (reviewer) on 12 Nov 2021 00:41:11 +00:00:

chocolatey-ops (reviewer) on 02 Dec 2021 00:41:16 +00:00:

chocolatey-ops (reviewer) on 17 Dec 2021 00:43:21 +00:00:

Ground Rules:

1

2

3

NSwagStudio