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.2.4.3.nupkg"

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

If Applicable - Chocolatey Configuration/Installation


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

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

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

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


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

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

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

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

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


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


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

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

### b. Apply Recommended Configuration ###

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Need Help? View our docs or file an issue.

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

Current Version	New Version

Downloads:

346,995

Downloads of v 4.0.0-beta001:

1

Last Update:

27 Jun 2025

Published Date:

27 Jun 2025

Package Maintainer(s):

Software Author(s):

Charlie Poole
Rob Prouse

Tags:

NUnit Console Runner V4

(Waiting on dependencies)

This is a prerelease version of NUnit Console Runner V4.

The package has been suspended from automatic moderation due to unsatisfied dependencies. Moderation for this package will continue once all dependencies that satisfy the version range have been approved or exempted.

4.0.0-beta001 | Updated: 27 Jun 2025

Downloads:

346,995

Downloads of v 4.0.0-beta001:

Published:

27 Jun 2025

Maintainer(s):

Software Author(s):

Charlie Poole
Rob Prouse

Tags:

nunit console runner test testing tdd

NUnit Console Runner V4 4.0.0-beta001

(Waiting on dependencies)

This is a prerelease version of NUnit Console Runner V4.

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Charlie Poole, Rob Prouse. The inclusion of Charlie Poole, Rob Prouse trademark(s), if any, upon this webpage is solely to identify Charlie Poole, Rob Prouse goods or services and not for commercial purposes.

All Checks are Pending

3 Pending Tests

Hide Checks

Validation Testing Pending

Verification Testing Pending

Scan Testing Pending

WARNING

IMPORTANT

This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.

Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
There are also no guarantees that it will be approved.

WARNING

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

charliepoole (maintainer) on 27 Jun 2025 23:46:14 +00:00:

User 'charliepoole' (maintainer) submitted package.

Description

This package includes version 4 of the NUnit Console Runner and test engine.

Files

tools\LICENSE.txt

Copyright (c) 2021 Charlie Poole, Rob Prouse

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\NOTICES.txt

NUnit 3.0 is based on earlier versions of NUnit, with Portions

Copyright (c) 2002-2014 Charlie Poole or 
Copyright (c) 2002-2004 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov or 
Copyright (c) 2000-2002 Philip A. Craig

tools\nunit-console.exe

md5: CE932D3DED0DC80D74B435CBE8B685B0 | sha1: 52A453BA432C18748A94507C6216EBD0D8FA6B76 | sha256: 2ED9425963B5AEB326E8EFCECD7287A47098B6667549817687511C5EDAF79361 | sha512: 85648A4CBDF31F4C9C2C9CAE321CCB117004D3BA19B50D2C072B36FAEEDEB9382059052DEFDDE826106769D66AA9292D6719C1F51957FF016E8F2011F1652E9F

tools\nunit-console.exe.config

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <!--
   The console runner runs under .NET 2.0 or higher. 
   The setting useLegacyV2RuntimeActivationPolicy only applies 
   under .NET 4.0 and permits use of mixed mode assemblies, 
   which would otherwise not load correctly.
  -->
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0.30319" />
    <supportedRuntime version="v2.0.50727" />
  </startup>
  <runtime>
    <!-- Ensure that test exceptions don't crash NUnit -->
    <legacyUnhandledExceptionPolicy enabled="1" />
    <!--
     Since legacyUnhandledExceptionPolicy keeps the console from being killed even though an NUnit framework
     test worker thread is killed, this is needed to prevent a hang. NUnit framework can only handle these
     exceptions when this config element is present. (Or if future versions of NUnit framework drop support
     for partial trust which would enable it to use [HandleProcessCorruptedStateExceptions].)
    -->
    <legacyCorruptedStateExceptionsPolicy enabled="true" />
    <!-- Run partial trust V2 assemblies in full trust under .NET 4.0 -->
    <loadFromRemoteSources enabled="true" />
    <!-- Enable reading source information from Portable and Embedded PDBs when running applications -->
    <!-- built against previous .NET Framework versions on .NET Framework 4.7.2 -->
    <AppContextSwitchOverrides value="Switch.System.Diagnostics.IgnorePortablePDBsInStackTraces=false" />
  </runtime>
</configuration>

tools\nunit.choco.addins

tools\nunit.common.dll

md5: DF14A6C398516DDBAC94F6110C816C06 | sha1: E8A9E668B69163CAE50962648DC0FFED8C01320A | sha256: 7755F5B43485C83C5649744E244562E79DB640EDD4A14F270885BD76493BAC66 | sha512: 1D2F33E7B2B300DCF40966381B097A990F3F01DF106F5D5C885CD50E614828A24FD25C92DADBBF7CB02A633D21A785BF4F535D970BE976E83C54833FB6ED5A07

tools\nunit.engine.api.dll

md5: 8C6BDEDEB139CC9B553AE74247795FF5 | sha1: 9309E11E24A8D106746F959D2DDC8E5A16989B41 | sha256: 44F710D622833E3C3C0FCC4D2FC3FB831FB2523B440E0673389CFE4BF5300B95 | sha512: 27D4EC2BABC0BB4C83029A7B9373ACCC3C6703A6B415B9235A6D9F70FACC8C8A12A2D7FB2B17CB8C1CE4101E8131BA51F934648D29B4C0D18501DF1A5131FFDD

tools\nunit.engine.api.xml

<?xml version="1.0"?>
<doc>
    <assembly>
        <name>nunit.engine.api</name>
    </assembly>
    <members>
        <member name="T:System.Runtime.CompilerServices.IsExternalInit">
            <summary>
                Reserved to be used by the compiler for tracking metadata.
                This class should not be used by developers in source code.
            </summary>
            <remarks>
                This definition is provided by the <i>IsExternalInit</i> NuGet package (https://www.nuget.org/packages/IsExternalInit).
                Please see https://github.com/manuelroemer/IsExternalInit for more information.
            </remarks>
        </member>
        <member name="T:NUnit.Engine.AsyncTestEngineResult">
            <summary>
            The TestRun class encapsulates an ongoing test run.
            </summary>
        </member>
        <member name="P:NUnit.Engine.AsyncTestEngineResult.EngineResult">
            <summary>
            Get the result of this run.
            </summary>
            <exception cref="T:System.InvalidOperationException">Cannot retrieve Result from an incomplete or cancelled TestRun.</exception>
        </member>
        <member name="P:NUnit.Engine.AsyncTestEngineResult.WaitHandle">
            <summary>
            TODO: Can we remove this?
            </summary>
        </member>
        <member name="M:NUnit.Engine.AsyncTestEngineResult.SetResult(NUnit.Engine.TestEngineResult)">
            <summary>
            Used by tests
            </summary>
        </member>
        <member name="M:NUnit.Engine.AsyncTestEngineResult.Wait(System.Int32)">
            <summary>
            Blocks the current thread until the current test run completes
            or the timeout is reached
            </summary>
            <param name="timeout">A <see cref="T:System.Int32"/> that represents the number of milliseconds to wait, or -1 milliseconds to wait indefinitely. </param>
            <returns>True if the run completed</returns>
        </member>
        <member name="P:NUnit.Engine.AsyncTestEngineResult.IsComplete">
            <summary>
            True if the test run has completed
            </summary>
        </member>
        <member name="T:NUnit.Engine.NUnitEngineException">
            <summary>
            NUnitEngineException is thrown when the engine has been
            called with improper values or when a particular facility
            is not available.
            </summary>
        </member>
        <member name="M:NUnit.Engine.NUnitEngineException.#ctor(System.String)">
            <summary>
            Construct with a message
            </summary>
        </member>
        <member name="M:NUnit.Engine.NUnitEngineException.#ctor(System.String,System.Exception)">
            <summary>
            Construct with a message and inner exception
            </summary>
        </member>
        <member name="M:NUnit.Engine.NUnitEngineException.#ctor(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext)">
            <summary>
            Serialization constructor
            </summary>
        </member>
        <member name="T:NUnit.Engine.NUnitEngineNotFoundException">
            <summary>
            The exception that is thrown if a valid test engine is not found
            </summary>
        </member>
        <member name="M:NUnit.Engine.NUnitEngineNotFoundException.#ctor">
            <summary>
            Initializes a new instance of the <see cref="T:NUnit.Engine.NUnitEngineNotFoundException"/> class.
            </summary>
        </member>
        <member name="T:NUnit.Engine.NUnitEngineUnloadException">
            <summary>
            NUnitEngineUnloadException is thrown when a test run has completed successfully
            but one or more errors were encountered when attempting to unload
            and shut down the test run cleanly.
            </summary>
        </member>
        <member name="M:NUnit.Engine.NUnitEngineUnloadException.#ctor(System.String)">
            <summary>
            Construct with a message
            </summary>
        </member>
        <member name="M:NUnit.Engine.NUnitEngineUnloadException.#ctor(System.String,System.Exception)">
            <summary>
            Construct with a message and inner exception
            </summary>
        </member>
        <member name="M:NUnit.Engine.NUnitEngineUnloadException.#ctor(System.Collections.Generic.ICollection{System.Exception})">
            <summary>
            Construct with a message and a collection of exceptions.
            </summary>
        </member>
        <member name="M:NUnit.Engine.NUnitEngineUnloadException.#ctor(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext)">
            <summary>
            Serialization constructor.
            </summary>
        </member>
        <member name="P:NUnit.Engine.NUnitEngineUnloadException.AggregatedExceptions">
            <summary>
            Gets the collection of exceptions .
            </summary>
        </member>
        <member name="T:NUnit.Engine.Extensibility.IAgentLauncher">
            <summary>
            Interface implemented by an agent launcher, which is able to examine
            a test package, evaluate whether it can create an agent for it and
            create the agent itself on request.
            </summary>
        </member>
        <member name="P:NUnit.Engine.Extensibility.IAgentLauncher.AgentInfo">
            <summary>
            Gets a TestAgentInfo describing this agent
            </summary>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IAgentLauncher.CanCreateAgent(NUnit.Engine.TestPackage)">
            <summary>
            Returns true if the launcher can create an agent for the supplied package, otherwise false.
            </summary>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IAgentLauncher.CreateAgent(System.Guid,System.String,NUnit.Engine.TestPackage)">
            <summary>
            Returns an agent capable of running the specified package.
            </summary>
        </member>
        <member name="T:NUnit.Engine.Extensibility.IDriverFactory">
            <summary>
            Interface implemented by a Type that knows how to create a driver for a test assembly.
            </summary>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IDriverFactory.IsSupportedTestFramework(System.Reflection.AssemblyName)">
            <summary>
            Gets a flag indicating whether a given AssemblyName
            represents a test framework supported by this factory.
            </summary>
            <param name="reference">An AssemblyName referring to the possible test framework.</param>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IDriverFactory.GetDriver(System.AppDomain,System.String,System.Reflection.AssemblyName)">
            <summary>
            Gets a driver for a given test assembly and a framework
            which the assembly is already known to reference.
            </summary>
            <param name="domain">The domain in which the assembly will be loaded</param>
            <param name="id">The driver id.</param>
            <param name="reference">An AssemblyName referring to the test framework.</param>
        </member>
        <member name="T:NUnit.Engine.Extensibility.IFrameworkDriver">
            <summary>
            The IFrameworkDriver interface is implemented by a class that
            is able to use an external framework to explore or run tests
            under the engine.
            </summary>
        </member>
        <member name="P:NUnit.Engine.Extensibility.IFrameworkDriver.ID">
            <summary>
            Gets and sets the unique identifier for this driver,
            used to ensure that test ids are unique across drivers.
            </summary>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IFrameworkDriver.Load(System.String,System.Collections.Generic.IDictionary{System.String,System.Object})">
            <summary>
            Loads the tests in an assembly.
            </summary>
            <returns>An Xml string representing the loaded test</returns>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IFrameworkDriver.CountTestCases(System.String)">
            <summary>
            Count the test cases that would be executed.
            </summary>
            <param name="filter">An XML string representing the TestFilter to use in counting the tests</param>
            <returns>The number of test cases counted</returns>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IFrameworkDriver.Run(NUnit.Engine.ITestEventListener,System.String)">
            <summary>
            Executes the tests in an assembly.
            </summary>
            <param name="listener">An ITestEventHandler that receives progress notices</param>
            <param name="filter">A XML string representing the filter that controls which tests are executed</param>
            <returns>An Xml string representing the result</returns>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IFrameworkDriver.Explore(System.String)">
            <summary>
            Returns information about the tests in an assembly.
            </summary>
            <param name="filter">An XML string representing the filter that controls which tests are included</param>
            <returns>An Xml string representing the tests</returns>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IFrameworkDriver.StopRun(System.Boolean)">
            <summary>
            Cancel the ongoing test run. If no  test is running, the call is ignored.
            </summary>
            <param name="force">If true, cancel any ongoing test threads, otherwise wait for them to complete.</param>
        </member>
        <member name="T:NUnit.Engine.Extensibility.IProject">
            <summary>
            Interface for the various project types that the engine can load.
            </summary>
        </member>
        <member name="P:NUnit.Engine.Extensibility.IProject.ProjectPath">
            <summary>
            Gets the path to the file storing this project, if any.
            If the project has not been saved, this is null.
            </summary>
        </member>
        <member name="P:NUnit.Engine.Extensibility.IProject.ActiveConfigName">
            <summary>
            Gets the active configuration, as defined
            by the particular project.
            </summary>
        </member>
        <member name="P:NUnit.Engine.Extensibility.IProject.ConfigNames">
            <summary>
            Gets a list of the configs for this project
            </summary>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IProject.GetTestPackage">
            <summary>
            Gets a test package for the primary or active
            configuration within the project. The package
            includes all the assemblies and any settings
            specified in the project format.
            </summary>
            <returns>A TestPackage</returns>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IProject.GetTestPackage(System.String)">
            <summary>
            Gets a TestPackage for a specific configuration
            within the project. The package includes all the
            assemblies and any settings specified in the
            project format.
            </summary>
            <param name="configName">The name of the config to use</param>
            <returns>A TestPackage for the named configuration.</returns>
        </member>
        <member name="T:NUnit.Engine.Extensibility.IProjectLoader">
            <summary>
            The IProjectLoader interface is implemented by any class
            that knows how to load projects in a specific format.
            </summary>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IProjectLoader.CanLoadFrom(System.String)">
            <summary>
            Returns true if the file indicated is one that this
            loader knows how to load.
            </summary>
            <param name="path">The path of the project file</param>
            <returns>True if the loader knows how to load this file, otherwise false</returns>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IProjectLoader.LoadFrom(System.String)">
            <summary>
            Loads a project of a known format.
            </summary>
            <param name="path">The path of the project file</param>
            <returns>An IProject interface to the loaded project or null if the project cannot be loaded</returns>
        </member>
        <member name="T:NUnit.Engine.Extensibility.IResultWriter">
            <summary>
            Common interface for objects that process and write out test results
            </summary>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IResultWriter.CheckWritability(System.String)">
            <summary>
            Checks if the output path is writable. If the output is not
            writable, this method should throw an exception.
            </summary>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IResultWriter.WriteResultFile(System.Xml.XmlNode,System.String)">
            <summary>
            Writes result to the specified output path.
            </summary>
            <param name="resultNode">XmlNode for the result</param>
            <param name="outputPath">Path to which it should be written</param>
        </member>
        <member name="M:NUnit.Engine.Extensibility.IResultWriter.WriteResultFile(System.Xml.XmlNode,System.IO.TextWriter)">
            <summary>
            Writes result to a TextWriter.
            </summary>
            <param name="resultNode">XmlNode for the result</param>
            <param name="writer">TextWriter to which it should be written</param>
        </member>
        <member name="T:NUnit.Engine.Services.IAgentInfoProvider">
            <summary>
            Objects implementing IAgentInfoProvider can return information about
            available agents. The interface is used by runners in order to provide
            to the user or to allow selecting agents.
            </summary>
        </member>
        <member name="P:NUnit.Engine.Services.IAgentInfoProvider.AvailableAgents">
            <summary>
            Gets a list containing <see cref="T:NUnit.Engine.TestAgentInfo"/> for all available agents.
            </summary>
        </member>
        <member name="M:NUnit.Engine.Services.IAgentInfoProvider.GetAgentsForPackage(NUnit.Engine.TestPackage)">
            <summary>
            Gets a list containing <see cref="T:NUnit.Engine.TestAgentInfo"/> for any available agents,
            which are able to handle the specified package.
            </summary>
            <param name="package">A TestPackage</param>
            <returns>
            A list of suitable agents for running the package or an empty
            list if no agent is available for the package.
            </returns>
        </member>
        <member name="T:NUnit.Engine.IAvailableRuntimes">
            <summary>
            Interface that returns a list of available runtime frameworks.
            </summary>
        </member>
        <member name="P:NUnit.Engine.IAvailableRuntimes.AvailableRuntimes">
            <summary>
            Gets a list of available runtime frameworks for X64.
            </summary>
        </member>
        <member name="P:NUnit.Engine.IAvailableRuntimes.AvailableX86Runtimes">
            <summary>
            Gets a list of available runtime frameworks for X86.
            </summary>
        </member>
        <member name="T:NUnit.Engine.IExtensionService">
            <summary>
            The IExtensionService interface allows a runner to manage extensions.
            </summary>
        </member>
        <member name="P:NUnit.Engine.IExtensionService.ExtensionPoints">
            <summary>
            Gets an enumeration of all extension points in the engine.
            </summary>
            <returns>An enumeration of IExtensionPoints. </returns>
        </member>
        <member name="P:NUnit.Engine.IExtensionService.Extensions">
            <summary>
            Gets an enumeration of all installed Extensions.
            </summary>
            <returns>An enumeration of IExtensionNodes</returns>
        </member>
        <member name="M:NUnit.Engine.IExtensionService.FindExtensionAssemblies(System.String)">
            <summary>
            Find candidate extension assemblies starting from a given base directory,
            and using the contained '.addins' files to direct the search.
            </summary>
            <param name="initialDirectory">Path to the initial directory.</param>
        </member>
        <member name="M:NUnit.Engine.IExtensionService.GetExtensionPoint(System.String)">
            <summary>
            Get an IExtensionPoint based on its unique identifying path.
            </summary>
            <returns>A single IExtensionPoint with the specified path if it exists. Otherwise null.</returns>
        </member>
        <member name="M:NUnit.Engine.IExtensionService.GetExtensionNodes(System.String)">
            <summary>
            Get an enumeration of IExtensionNodes based on their identifying path.
            </summary>
            <returns>An enumeration of IExtensionNodes.</returns>
        </member>
        <member name="M:NUnit.Engine.IExtensionService.EnableExtension(System.String,System.Boolean)">
            <summary>
            Enable or disable an extension
            </summary>
        </member>
        <member name="M:NUnit.Engine.IExtensionService.LoadExtensions">
            <summary>
            If extensions have not yet been loaded, examine all candidate assemblies
            and load them. Subsequent calls are ignored.
            </summary>
            <remarks>
            We can only load extensions after all candidate assemblies are identified.
            This method may be called by the user after all "Find" calls are complete.
            If the user fails to call it and subsequently tries to examine extensions
            using other ExtensionManager properties or methods, it will be called
            but calls not going through ExtensionManager may fail.
            </remarks>
        </member>
        <member name="M:NUnit.Engine.IExtensionService.GetExtensions``1">
            <summary>
            Get extension objects for all nodes of a given type
            </summary>
            <returns>An enumeration of T</returns>
        </member>
        <member name="M:NUnit.Engine.IExtensionService.GetExtensionNodes``1">
            <summary>
            Get all extension nodes of a given Type.
            </summary>
            An enumeration of IExtensionNodes for Type T.
        </member>
        <member name="T:NUnit.Engine.InternalTraceLevel">
            <summary>
            InternalTraceLevel is an enumeration controlling the
            level of detailed presented in the internal log.
            </summary>
        </member>
        <member name="F:NUnit.Engine.InternalTraceLevel.Default">
            <summary>
            Use the default settings as specified by the user.
            </summary>
        </member>
        <member name="F:NUnit.Engine.InternalTraceLevel.Off">
            <summary>
            Do not display any trace messages
            </summary>
        </member>
        <member name="F:NUnit.Engine.InternalTraceLevel.Error">
            <summary>
            Display Error messages only
            </summary>
        </member>
        <member name="F:NUnit.Engine.InternalTraceLevel.Warning">
            <summary>
            Display Warning level and higher messages
            </summary>
        </member>
        <member name="F:NUnit.Engine.InternalTraceLevel.Info">
            <summary>
            Display informational and higher messages
            </summary>
        </member>
        <member name="F:NUnit.Engine.InternalTraceLevel.Debug">
            <summary>
            Display debug messages and higher - i.e. all messages
            </summary>
        </member>
        <member name="F:NUnit.Engine.InternalTraceLevel.Verbose">
            <summary>
            Display debug messages and higher - i.e. all messages
            </summary>
        </member>
        <member name="T:NUnit.Engine.IResultService">
            <summary>
            IResultWriterService provides result writers for a specified
            well-known format.
            </summary>
        </member>
        <member name="P:NUnit.Engine.IResultService.Formats">
            <summary>
            Gets an array of the available formats
            </summary>
        </member>
        <member name="M:NUnit.Engine.IResultService.GetResultWriter(System.String,System.Object[])">
            <summary>
            Gets a ResultWriter for a given format and set of arguments.
            </summary>
            <param name="format">The name of the format to be used</param>
            <param name="args">A set of arguments to be used in constructing the writer or null if non arguments are needed</param>
            <returns>An IResultWriter</returns>
        </member>
        <member name="T:NUnit.Engine.IRuntimeFramework">
            <summary>
            Interface implemented by objects representing a runtime framework.
            </summary>
        </member>
        <member name="P:NUnit.Engine.IRuntimeFramework.Id">
            <summary>
            Gets the inique Id for this runtime, such as "net-4.5"
            </summary>
        </member>
        <member name="P:NUnit.Engine.IRuntimeFramework.DisplayName">
            <summary>
            Gets the display name of the framework, such as ".NET 4.5"
            </summary>
        </member>
        <member name="P:NUnit.Engine.IRuntimeFramework.FrameworkVersion">
            <summary>
            Gets the framework version: usually contains two components, Major
            and Minor, which match the corresponding CLR components, but not always.
            </summary>
        </member>
        <member name="P:NUnit.Engine.IRuntimeFramework.Profile">
            <summary>
            Gets a string representing the particular profile installed,
            or null if there is no profile. Currently. the only defined
            values are Full and Client.
            </summary>
        </member>
        <member name="T:NUnit.Engine.IRuntimeFrameworkService">
            <summary>
            Implemented by a type that provides information about the
            current and other available runtimes.
            </summary>
        </member>
        <member name="P:NUnit.Engine.IRuntimeFrameworkService.CurrentFramework">
            <summary>
            Gets a RuntimeFramework instance representing the runtime under
            which the code is currently running.
            </summary>
        </member>
        <member name="M:NUnit.Engine.IRuntimeFrameworkService.IsAvailable(System.String,System.Boolean)">
            <summary>
            Returns true if the runtime framework represented by
            the string passed as an argument is available.
            </summary>
            <param name="framework">A string representing a framework, like 'net-4.0'</param>
            <param name="runAsX86">A flag indicating whether X86 support is needed.</param>
            <returns>True if the framework is available, false if unavailable or nonexistent</returns>
        </member>
        <member name="M:NUnit.Engine.IRuntimeFrameworkService.SelectRuntimeFramework(NUnit.Engine.TestPackage)">
             <summary>
             Selects a target runtime framework for a TestPackage based on
             the settings in the package and the assemblies themselves.
             The package RuntimeFramework setting may be updated as a
             result and the selected runtime is returned.
            
             Note that if a package has subpackages, the subpackages may run on a different
             framework to the top-level package. In future, this method should
             probably not return a simple string, and instead require runners
             to inspect the test package structure, to find all desired frameworks.
             </summary>
             <param name="package">A TestPackage</param>
             <returns>The selected RuntimeFramework</returns>
        </member>
        <member name="T:NUnit.Engine.ServiceStatus">
            <summary>
            Enumeration representing the status of a service
            </summary>
        </member>
        <member name="F:NUnit.Engine.ServiceStatus.Stopped">
            <summary>Service was never started or has been stopped</summary>
        </member>
        <member name="F:NUnit.Engine.ServiceStatus.Started">
            <summary>Started successfully</summary>
        </member>
        <member name="F:NUnit.Engine.ServiceStatus.Error">
            <summary>Service failed to start and is unavailable</summary>
        </member>
        <member name="T:NUnit.Engine.IService">
            <summary>
            The IService interface is implemented by all Services. Although it
            is extensible, it does not reside in the Extensibility namespace
            because it is so widely used by the engine.
            </summary>
        </member>
        <member name="P:NUnit.Engine.IService.ServiceContext">
            <summary>
            The ServiceContext
            </summary>
        </member>
        <member name="P:NUnit.Engine.IService.Status">
            <summary>
            Gets the ServiceStatus of this service
            </summary>
        </member>
        <member name="M:NUnit.Engine.IService.StartService">
            <summary>
            Initialize the Service
            </summary>
        </member>
        <member name="M:NUnit.Engine.IService.StopService">
            <summary>
            Do any cleanup needed before terminating the service
            </summary>
        </member>
        <member name="T:NUnit.Engine.IServiceLocator">
            <summary>
            IServiceLocator allows clients to locate any NUnit services
            for which the interface is referenced. In normal use, this
            linits it to those services using interfaces defined in the
            nunit.engine.api assembly.
            </summary>
        </member>
        <member name="M:NUnit.Engine.IServiceLocator.GetService``1">
            <summary>
            Return a specified type of service
            </summary>
        </member>
        <member name="M:NUnit.Engine.IServiceLocator.GetService(System.Type)">
            <summary>
            Return a specified type of service
            </summary>
        </member>
        <member name="T:NUnit.Engine.ITestAgency">
            <summary>
            The ITestAgency interface is implemented by a TestAgency in
            order to allow TestAgents to register with it.
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestAgency.Register(NUnit.Engine.ITestAgent)">
            <summary>
            Registers an agent with an agency
            </summary>
        </member>
        <member name="T:NUnit.Engine.ITestAgent">
            <summary>
            The ITestAgent interface is implemented by remote test agents.
            </summary>
        </member>
        <member name="P:NUnit.Engine.ITestAgent.Id">
            <summary>
            Gets a Guid that uniquely identifies this agent.
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestAgent.Start">
            <summary>
            Starts the agent, performing any required initialization
            </summary>
            <returns>True if successful, otherwise false</returns>
        </member>
        <member name="M:NUnit.Engine.ITestAgent.Stop">
            <summary>
            Stops the agent, releasing any resources
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestAgent.CreateRunner(NUnit.Engine.TestPackage)">
            <summary>
             Creates a test runner
            </summary>
        </member>
        <member name="T:NUnit.Engine.ITestEngine">
            <summary>
            ITestEngine represents an instance of the test engine.
            Clients wanting to discover, explore or run tests start
            require an instance of the engine, which is generally
            acquired from the TestEngineActivator class.
            </summary>
        </member>
        <member name="P:NUnit.Engine.ITestEngine.Services">
            <summary>
            Gets the IServiceLocator interface, which gives access to
            certain services provided by the engine.
            </summary>
        </member>
        <member name="P:NUnit.Engine.ITestEngine.WorkDirectory">
            <summary>
            Gets and sets the directory path used by the engine for saving files.
            Some services may ignore changes to this path made after initialization.
            The default value is the current directory.
            </summary>
        </member>
        <member name="P:NUnit.Engine.ITestEngine.InternalTraceLevel">
            <summary>
            Gets and sets the InternalTraceLevel used by the engine. Changing this
            setting after initialization will have no effect. The default value
            is the value saved in the NUnit settings.
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestEngine.Initialize">
             <summary>
             Initialize the engine. This includes initializing mono addins,
             setting the trace level and creating the standard set of services
             used in the Engine.
            
             This interface is not normally called by user code. Programs linking
             only to the nunit.engine.api assembly are given a
             pre-initialized instance of TestEngine. Programs
             that link directly to nunit.engine usually do so
             in order to perform custom initialization.
             </summary>
        </member>
        <member name="M:NUnit.Engine.ITestEngine.GetRunner(NUnit.Engine.TestPackage)">
            <summary>
            Returns a test runner instance for use by clients in discovering,
            exploring and executing tests.
            </summary>
            <param name="package">The TestPackage for which the runner is intended.</param>
            <returns>An ITestRunner.</returns>
        </member>
        <member name="T:NUnit.Engine.ITestEngineRunner">
            <summary>
            Interface implemented by all internal test runners in
            the engine, allowing them to pass back TestEngineResults
            to any higher-level runner that calls them.
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestEngineRunner.Load">
            <summary>
            Load a TestPackage for possible execution
            </summary>
            <returns>A TestEngineResult.</returns>
        </member>
        <member name="M:NUnit.Engine.ITestEngineRunner.Unload">
            <summary>
            Unload any loaded TestPackage. If none is loaded,
            the call is ignored.
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestEngineRunner.Reload">
            <summary>
            Reload the loaded test package.
            </summary>
            <returns>A TestEngineResult.</returns>
            <exception cref="T:System.InvalidOperationException">If no package is loaded.</exception>
        </member>
        <member name="M:NUnit.Engine.ITestEngineRunner.CountTestCases(NUnit.Engine.TestFilter)">
            <summary>
            Count the test cases that would be run under
            the specified filter.
            </summary>
            <param name="filter">A TestFilter</param>
            <returns>The count of test cases</returns>
        </member>
        <member name="M:NUnit.Engine.ITestEngineRunner.Run(NUnit.Engine.ITestEventListener,NUnit.Engine.TestFilter)">
            <summary>
            Run the tests in the loaded TestPackage and return a test result. The tests
            are run synchronously and the listener interface is notified as it progresses.
            </summary>
            <param name="listener">An ITestEventHandler to receive events</param>
            <param name="filter">A TestFilter used to select tests</param>
            <returns>A TestEngineResult giving the result of the test execution</returns>
        </member>
        <member name="M:NUnit.Engine.ITestEngineRunner.RunAsync(NUnit.Engine.ITestEventListener,NUnit.Engine.TestFilter)">
            <summary>
            Start a run of the tests in the loaded TestPackage. The tests are run
            asynchronously and the listener interface is notified as it progresses.
            </summary>
            <param name="listener">An ITestEventHandler to receive events</param>
            <param name="filter">A TestFilter used to select tests</param>
            <returns>An <see cref="T:NUnit.Engine.AsyncTestEngineResult"/> that will provide the result of the test execution</returns>
        </member>
        <member name="M:NUnit.Engine.ITestEngineRunner.RequestStop">
            <summary>
            Request the current test run to stop. If no tests are running,
            the call is ignored.
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestEngineRunner.ForcedStop">
            <summary>
            Force the current test run to stop, killing threads or processes if necessary.
            If no tests are running, the call is ignored.
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestEngineRunner.Explore(NUnit.Engine.TestFilter)">
            <summary>
            Explore a loaded TestPackage and return information about
            the tests found.
            </summary>
            <param name="filter">Criteria used to filter the search results</param>
            <returns>A TestEngineResult.</returns>
        </member>
        <member name="T:NUnit.Engine.ITestEventListener">
            <summary>
            The ITestListener interface is used to receive notices of significant
            events while a test is running. Its single method accepts an Xml string,
            which may represent any event generated by the test framework, the driver
            or any of the runners internal to the engine. Use of Xml means that
            any driver and framework may add additional events and the engine will
            simply pass them on through this interface.
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestEventListener.OnTestEvent(System.String)">
            <summary>
            Handle a progress report or other event.
            </summary>
            <param name="report">An XML progress report.</param>
        </member>
        <member name="T:NUnit.Engine.ITestFilterBuilder">
            <summary>
            Interface to a TestFilterBuilder, which is used to create TestFilters
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestFilterBuilder.AddTest(System.String)">
            <summary>
            Add a test to be selected
            </summary>
            <param name="fullName">The full name of the test, as created by NUnit</param>
        </member>
        <member name="M:NUnit.Engine.ITestFilterBuilder.SelectWhere(System.String)">
            <summary>
            Specify what is to be included by the filter using a where clause.
            </summary>
            <param name="whereClause">A where clause that will be parsed by NUnit to create the filter.</param>
        </member>
        <member name="M:NUnit.Engine.ITestFilterBuilder.GetFilter">
            <summary>
            Get a TestFilter constructed according to the criteria specified by the other calls.
            </summary>
            <returns>A TestFilter.</returns>
        </member>
        <member name="T:NUnit.Engine.ITestFilterService">
            <summary>
            The TestFilterService provides builders that can create TestFilters
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestFilterService.GetTestFilterBuilder">
            <summary>
            Get an uninitialized TestFilterBuilder
            </summary>
        </member>
        <member name="T:NUnit.Engine.ITestRun">
            <summary>
            The ITestRun class represents an ongoing test run.
            </summary>
        </member>
        <member name="P:NUnit.Engine.ITestRun.Result">
            <summary>
            Get the result of the test.
            </summary>
            <returns>An XmlNode representing the test run result</returns>
        </member>
        <member name="M:NUnit.Engine.ITestRun.Wait(System.Int32)">
            <summary>
            Blocks the current thread until the current test run completes
            or the timeout is reached
            </summary>
            <param name="timeout">A <see cref="T:System.Int32"/> that represents the number of milliseconds to wait or -1 milliseconds to wait indefinitely. </param>
            <returns>True if the run completed</returns>
        </member>
        <member name="T:NUnit.Engine.ITestRunner">
            <summary>
            Interface implemented by all test runners.
            </summary>
        </member>
        <member name="P:NUnit.Engine.ITestRunner.IsTestRunning">
            <summary>
            Get a flag indicating whether a test is running
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestRunner.Load">
            <summary>
            Load a TestPackage for possible execution
            </summary>
            <returns>An XmlNode representing the loaded package.</returns>
            <remarks>
            This method is normally optional, since Explore and Run call
            it automatically when necessary. The method is kept in order
            to make it easier to convert older programs that use it.
            </remarks>
        </member>
        <member name="M:NUnit.Engine.ITestRunner.Unload">
            <summary>
            Unload any loaded TestPackage. If none is loaded,
            the call is ignored.
            </summary>
        </member>
        <member name="M:NUnit.Engine.ITestRunner.Reload">
            <summary>
            Reload the current TestPackage
            </summary>
            <returns>An XmlNode representing the loaded package.</returns>
        </member>
        <member name="M:NUnit.Engine.ITestRunner.CountTestCases(NUnit.Engine.TestFilter)">
            <summary>
            Count the test cases that would be run under
            the specified filter.
            </summary>
            <param name="filter">A TestFilter</param>
            <returns>The count of test cases</returns>
        </member>
        <member name="M:NUnit.Engine.ITestRunner.Run(NUnit.Engine.ITestEventListener,NUnit.Engine.TestFilter)">
            <summary>
            Run the tests in the loaded TestPackage and return a test result. The tests
            are run synchronously and the listener interface is notified as it progresses.
            </summary>
            <param name="listener">The listener that is notified as the run progresses</param>
            <param name="filter">A TestFilter used to select tests</param>
            <returns>An XmlNode giving the result of the test execution</returns>
        </member>
        <member name="M:NUnit.Engine.ITestRunner.RunAsync(NUnit.Engine.ITestEventListener,NUnit.Engine.TestFilter)">
            <summary>
            Start a run of the tests in the loaded TestPackage. The tests are run
            asynchronously and the listener interface is notified as it progresses.
            </summary>
            <param name="listener">The listener that is notified as the run progresses</param>
            <param name="filter">A TestFilter used to select tests</param>
        </member>
        <member name="M:NUnit.Engine.ITestRunner.StopRun(System.Boolean)">
            <summary>
            Cancel the ongoing test run. If no  test is running, the call is ignored.
            </summary>
            <param name="force">If true, cancel any ongoing test threads, otherwise wait for them to complete.</param>
        </member>
        <member name="M:NUnit.Engine.ITestRunner.Explore(NUnit.Engine.TestFilter)">
            <summary>
            Explore a loaded TestPackage and return information about the tests found.
            </summary>
            <param name="filter">The TestFilter to be used in selecting tests to explore.</param>
            <returns>An XmlNode representing the tests found.</returns>
        </member>
        <member name="T:NUnit.Engine.PackageSetting">
            <summary>
            Abstract base for all generic package Settings
            </summary>
        </member>
        <member name="M:NUnit.Engine.PackageSetting.#ctor(System.String,System.Object)">
            <summary>
            Construct a PackageSetting
            </summary>
            <param name="name">The name of this setting.</param>
            <param name="value">The value of the setting</param>
        </member>
        <member name="P:NUnit.Engine.PackageSetting.Name">
            <summary>
            Gets the name of this setting.
            </summary>
        </member>
        <member name="P:NUnit.Engine.PackageSetting.Value">
            <summary>
            Gets the value of this setting as an object.
            </summary>
        </member>
        <member name="T:NUnit.Engine.PackageSetting`1">
            <summary>
            The PackageSetting class represents one setting value contained in a
            TestPackage. Instances of PackageSetting are immutable.
            </summary>
        </member>
        <member name="M:NUnit.Engine.PackageSetting`1.#ctor(System.String,`0)">
            <summary>
            Construct a PackageSetting
            </summary>
            <param name="name">The setting name.</param>
            <param name="value">The value of this setting instance.</param>
        </member>
        <member name="P:NUnit.Engine.PackageSetting`1.Value">
            <summary>
            Get the setting value
            </summary>
        </member>
        <member name="T:NUnit.Engine.PackageSettings">
            <summary>
            PackageSettingList contains all the PackageSettings for a TestPackage.
            It supports enumeration of the settings and various operations on
            individual settings in the list.
            </summary>
        </member>
        <member name="P:NUnit.Engine.PackageSettings.Count">
            <summary>
            Gets the number of settings in the list
            </summary>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.HasSetting(System.String)">
            <summary>
            Returns true if a setting with the specified name is present
            </summary>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.HasSetting(NUnit.Engine.SettingDefinition)">
            <summary>
            Returns true if a setting with the specified definition is present
            </summary>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.GetSetting(System.String)">
            <summary>
            Return the value of a setting if present, otherwise null.
            </summary>
            <param name="name">The name of the setting</param>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.GetValueOrDefault``1(NUnit.Engine.SettingDefinition{``0})">
            <summary>
            Return the value of a setting or its defined default value.
            </summary>
            <param name="definition">The name and type of the setting</param>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.GetEnumerator">
            <inheritdoc />
        </member>
        <member name="M:NUnit.Engine.PackageSettings.System#Collections#IEnumerable#GetEnumerator">
            <inheritdoc />
        </member>
        <member name="M:NUnit.Engine.PackageSettings.Add(NUnit.Engine.PackageSetting)">
            <summary>
            Adds a setting to the list directly.
            </summary>
            <param name="setting">A PackageSetting instance</param>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.Add(System.String,System.String)">
            <summary>
            Creates and adds a custom string setting to the list, specifying the name and value.
            </summary>
            <param name="name">The name of the setting.</param>
            <param name="value">The corresponding value to set.</param>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.Add(System.String,System.Boolean)">
            <summary>
            Creates and adds a custom boolean setting to the list, specifying the name and value.
            </summary>
            <param name="name">The name of the setting.</param>
            <param name="value">The corresponding value to set.</param>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.Add(System.String,System.Int32)">
            <summary>
            Creates and adds a custom int setting to the list, specifying the name and value.
            </summary>
            <param name="name">The name of the setting.</param>
            <param name="value">The corresponding value to set.</param>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.Set(NUnit.Engine.PackageSetting)">
            <summary>
            Adds or replaces a setting to the list.
            </summary>
        </member>
        <member name="M:NUnit.Engine.PackageSettings.Set``1(System.String,``0)">
            <summary>
            Adds or replaces a setting to the list.
            </summary>
            <param name="name">The name of the setting.</param>
            <param name="value">The corresponding value to set.</param>
        </member>
        <member name="T:NUnit.Engine.SettingDefinition">
             <summary>
            
             </summary>
        </member>
        <member name="M:NUnit.Engine.SettingDefinition.#ctor(System.String,System.Type)">
            <summary>
            Initializes a new instance of the <see cref="T:NUnit.Engine.SettingDefinition"/> class.
            </summary>
        </member>
        <member name="P:NUnit.Engine.SettingDefinition.Name">
            <summary>
            Gets the name of this setting.
            </summary>
        </member>
        <member name="P:NUnit.Engine.SettingDefinition.ValueType">
            <summary>
            Overridden in each derived definition to return the Type
            required for the value of the setting.
            </summary>
        </member>
        <member name="M:NUnit.Engine.SettingDefinition.WithValue``1(``0)">
            <summary>
            Create a PackageSetting based on this definition.
            </summary>
            <param name="value">The value to assign the setting.</param>
            <returns>A PackageSetting.</returns>
        </member>
        <member name="T:NUnit.Engine.SettingDefinition`1">
            <summary>
            SettingDefinition class is used as a sort of template for creating settings.
            It specifies the name of the setting and the Type required for its value but not
            the value itself. Its WithValue method is used to generate an actual PackageSetting.
            </summary>
        </member>
        <member name="M:NUnit.Engine.SettingDefinition`1.#ctor(System.String,`0)">
            <summary>
            Construct a SettingDefinition
            </summary>
            <param name="name">Name of this setting</param>
            <param name="defaultValue">The default value used when the setting is not provided</param>
        </member>
        <member name="P:NUnit.Engine.SettingDefinition`1.DefaultValue">
            <summary>
            The Default value used if the setting is not present
            </summary>
        </member>
        <member name="M:NUnit.Engine.SettingDefinition`1.WithValue(`0)">
            <summary>
            Create a PackageSetting based on this definition.
            </summary>
            <param name="value">The value to assign the setting.</param>
            <returns>A PackageSetting.</returns>
        </member>
        <member name="T:NUnit.Engine.TestAgentInfo">
            <summary>
            The TestAgentInfo struct provides information about an
            available agent for use by a runner.
            </summary>
        </member>
        <member name="F:NUnit.Engine.TestAgentInfo.AgentName">
            <summary>
            The name of this agent
            </summary>
        </member>
        <member name="F:NUnit.Engine.TestAgentInfo.AgentType">
            <summary>
            The agent type: InProcess, LocalProcess or RemoteProcess
            </summary>
        </member>
        <member name="F:NUnit.Engine.TestAgentInfo.TargetRuntime">
            <summary>
            The target runtime used by this agent
            </summary>
        </member>
        <member name="M:NUnit.Engine.TestAgentInfo.#ctor(System.String,NUnit.Engine.TestAgentType,System.Runtime.Versioning.FrameworkName)">
            <summary>
            Construct a TestAgent Info
            </summary>
            <param name="agentName">The agent name</param>
            <param name="agentType">The AgentType</param>
            <param name="targetRuntime">The target runtime</param>
        </member>
        <member name="T:NUnit.Engine.TestAgentType">
            <summary>
            <para>TestAgentType is an enumeration of the types
            of agents, which may be available. Currently, three
            types are defined, of which one is implemented.</para>
            </summary>
            <remarks>
            A user requests a particular agent type by including a
            "TestAgentType" setting in the test package. The setting
            is optional and the runner will select an agent of any
            type available if it isn't specified.
            </remarks>
        </member>
        <member name="F:NUnit.Engine.TestAgentType.Any">
            <summary>
            Any agent type is acceptable. This is the default value,
            so it never needs to be specified by the user. This
            setting is not valid in the TestAgentInfo struct, since
            each agent must be of some particular type.
            </summary>
        </member>
        <member name="F:NUnit.Engine.TestAgentType.InProcess">
            <summary>
            An in-process agent. This type is not directly supported
            by the engine but may be provided by an extension.
            </summary>
        </member>
        <member name="F:NUnit.Engine.TestAgentType.LocalProcess">
            <summary>
            An agent running as a separate local process.
            A supplier for this type is built into the engine.
            </summary>
        </member>
        <member name="F:NUnit.Engine.TestAgentType.RemoteProcess">
            <summary>
            An agent running on a server, that is a separate
            machine, which may be specified in the request or
            left up to the agent supplier to determine. A supplier
            for this type may be developed in the future.
            </summary>
        </member>
        <member name="T:NUnit.Engine.TestEngineResult">
             <summary>
             Wrapper class for the xml-formatted results produced
             by the test engine for most operations. The XML is
             stored as a string in order to allow serialization
             and actual XmlNodes are created on demand.
            
             In principal, there should only be one XmlNode in
             a result. However, as work progresses, there may
             temporarily be multiple nodes, which have not yet
             been aggregated under a higher level suite. For
             that reason, TestEngineResult maintains a list
             of XmlNodes and another of the corresponding text.
            
             Static methods are provided for aggregating the
             internal XmlNodes into a single node as well as
             for combining multiple TestEngineResults into one.
            
             </summary>
        </member>
        <member name="M:NUnit.Engine.TestEngineResult.#ctor(System.Xml.XmlNode)">
            <summary>
            Construct a TestResult from an XmlNode
            </summary>
            <param name="xml">An XmlNode representing the result</param>
        </member>
        <member name="M:NUnit.Engine.TestEngineResult.#ctor(System.String)">
            <summary>
            Construct a test from a string holding xml
            </summary>
            <param name="xml">A string containing the xml result</param>
        </member>
        <member name="M:NUnit.Engine.TestEngineResult.#ctor">
            <summary>
            Default constructor used when adding multiple results
            </summary>
        </member>
        <member name="P:NUnit.Engine.TestEngineResult.IsSingle">
            <summary>
            Gets a flag indicating whether this is a single result
            having only one XmlNode associated with it.
            </summary>
        </member>
        <member name="P:NUnit.Engine.TestEngineResult.XmlNodes">
            <summary>
            Gets the xml representing a test result as an XmlNode
            </summary>
        </member>
        <member name="P:NUnit.Engine.TestEngineResult.Xml">
            <summary>
            Gets the XML representing a single test result.
            </summary>
            <exception cref="T:System.InvalidOperationException">
            If the result is empty or has multiple XML nodes.
            </exception>
        </member>
        <member name="M:NUnit.Engine.TestEngineResult.Add(System.Xml.XmlNode)">
            <summary>
            Add an XmlNode to the TestEngineResult
            </summary>
        </member>
        <member name="T:NUnit.Engine.TestFilter">
            <summary>
            Abstract base for all test filters. A filter is represented
            by an XmlNode with &lt;filter&gt; as its topmost element.
            In the console runner, filters serve only to carry this
            XML representation, as all filtering is done by the engine.
            </summary>
        </member>
        <member name="M:NUnit.Engine.TestFilter.#ctor(System.String)">
            <summary>
            Initializes a new instance of the <see cref="T:NUnit.Engine.TestFilter"/> class.
            </summary>
            <param name="xmlText">The XML text that specifies the filter.</param>
        </member>
        <member name="F:NUnit.Engine.TestFilter.Empty">
            <summary>
            The empty filter - one that always passes.
            </summary>
        </member>
        <member name="P:NUnit.Engine.TestFilter.Text">
            <summary>
            Gets the XML representation of this filter as a string.
            </summary>
        </member>
        <member name="T:NUnit.Engine.TestPackage">
             <summary>
             TestPackage holds information about a set of test files to
             be loaded by a TestRunner. Each TestPackage represents
             tests for one or more test files. TestPackages may be named
             or anonymous, depending on the constructor used.
            
             Upon construction, a package is given an ID (string), which
             remains unchanged for the lifetime of the TestPackage instance.
             The package ID is passed to the test framework for use in generating
             test IDs.
            
             A runner that reloads test assemblies and wants the ids to remain stable
             should avoid creating a new package but should instead use the original
             package, changing settings as needed. This gives the best chance for the
             tests in the reloaded assembly to match those originally loaded.
             </summary>
        </member>
        <member name="M:NUnit.Engine.TestPackage.#ctor(System.String[])">
            <summary>
            Construct a top-level TestPackage that wraps one or more
            test files, contained as subpackages.
            </summary>
            <param name="testFiles">Names of all the test files</param>
            <remarks>
            Semantically equivalent to the IList constructor.
            </remarks>
        </member>
        <member name="M:NUnit.Engine.TestPackage.#ctor(System.Collections.Generic.IList{System.String})">
            <summary>
            Construct a top-level TestPackage that wraps one or more
            test files, contained as subpackages.
            </summary>
            <param name="testFiles">Names of all the test files.</param>
            <remarks>
            Semantically equivalent to the array constructor.
            </remarks>
        </member>
        <member name="M:NUnit.Engine.TestPackage.#ctor">
            <summary>
             Construct an empty TestPackage
            </summary>
            <remarks>Used in deserializing a package from xml.</remarks>
        </member>
        <member name="P:NUnit.Engine.TestPackage.ID">
            <summary>
            Every test package gets a unique ID used to prefix test IDs within that package.
            </summary>
            <remarks>
            The generated ID is only unique for packages created within the same application domain.
            For that reason, NUnit pre-creates all test packages that will be needed.
            </remarks>
        </member>
        <member name="P:NUnit.Engine.TestPackage.Name">
            <summary>
            Gets the name of the package
            </summary>
        </member>
        <member name="P:NUnit.Engine.TestPackage.FullName">
            <summary>
            Gets the path to the file containing tests. It may be
            an assembly or a recognized project type.
            </summary>
        </member>
        <member name="P:NUnit.Engine.TestPackage.SubPackages">
            <summary>
            Gets the list of SubPackages contained in this package
            </summary>
        </member>
        <member name="P:NUnit.Engine.TestPackage.Settings">
            <summary>
            Gets the settings dictionary for this package.
            </summary>
        </member>
        <member name="M:NUnit.Engine.TestPackage.AddSubPackage(NUnit.Engine.TestPackage)">
            <summary>
            Add a subpackage to the package.
            </summary>
            <param name="subPackage">The subpackage to be added</param>
        </member>
        <member name="M:NUnit.Engine.TestPackage.AddSubPackage(System.String)">
            <summary>
            Add a subpackage to the package, specifying its name. This is
            the only way to add a named subpackage to the top-level package.
            </summary>
            <param name="packageName">The name of the subpackage to be added</param>
        </member>
        <member name="M:NUnit.Engine.TestPackage.AddSetting(NUnit.Engine.PackageSetting)">
            <summary>
            Add a setting to a package and all of its subpackages.
            </summary>
            <param name="setting">The setting to be added</param>
            <remarks>
            Once a package is created, subpackages may have been created
            as well. If you add a setting directly to the Settings dictionary
            of the package, the subpackages are not updated. This method is
            used when the settings are intended to be reflected to all the
            subpackages under the package.
            </remarks>
        </member>
        <member name="M:NUnit.Engine.TestPackage.AddSetting(System.String,System.String)">
            <summary>
            Create and add a custom string setting to a package and all of its subpackages.
            </summary>
            <param name="name">The name of the setting.</param>
            <param name="value">The corresponding value to set.</param>
            <remarks>
            Once a package is created, subpackages may have been created
            as well. If you add a setting directly to the Settings dictionary
            of the package, the subpackages are not updated. This method is
            used when the settings are intended to be reflected to all the
            subpackages under the package.
            </remarks>
        </member>
        <member name="M:NUnit.Engine.TestPackage.AddSetting(System.String,System.Boolean)">
            <summary>
            Create and add a custom boolean setting to a package and all of its subpackages.
            </summary>
            <param name="name">The name of the setting.</param>
            <param name="value">The corresponding value to set.</param>
            <remarks>
            Once a package is created, subpackages may have been created
            as well. If you add a setting directly to the Settings dictionary
            of the package, the subpackages are not updated. This method is
            used when the settings are intended to be reflected to all the
            subpackages under the package.
            </remarks>
        </member>
        <member name="M:NUnit.Engine.TestPackage.AddSetting(System.String,System.Int32)">
            <summary>
            Create and add a custom int setting to a package and all of its subpackages.
            </summary>
            <param name="name">The name of the setting.</param>
            <param name="value">The corresponding value to set.</param>
            <remarks>
            Once a package is created, subpackages may have been created
            as well. If you add a setting directly to the Settings dictionary
            of the package, the subpackages are not updated. This method is
            used when the settings are intended to be reflected to all the
            subpackages under the package.
            </remarks>
        </member>
        <member name="T:NUnit.Engine.TestSelectionParserException">
            <summary>
            TestSelectionParserException is thrown when an error
            is found while parsing the selection expression.
            </summary>
        </member>
        <member name="M:NUnit.Engine.TestSelectionParserException.#ctor(System.String)">
            <summary>
            Construct with a message
            </summary>
        </member>
        <member name="M:NUnit.Engine.TestSelectionParserException.#ctor(System.String,System.Exception)">
            <summary>
            Construct with a message and inner exception
            </summary>
        </member>
        <member name="M:NUnit.Engine.TestSelectionParserException.#ctor(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext)">
            <summary>
            Serialization constructor
            </summary>
        </member>
        <member name="T:NUnit.Common.SettingDefinitions">
            <summary>
            Static class holding SettingDefinitions for all standard package settings
            known to the runner and engine. Except for internal settings with names
            starting "Image...", the runner creates the settings. Some settings are
            used by the engine, some by the framework and some by both.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.ActiveConfig">
            <summary>
            The name of the config to use in loading a project.
            If not specified, the first config found is used.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.AutoBinPath">
            <summary>
            Bool indicating whether the engine should determine the private
            bin path by examining the paths to all the tests. Defaults to
            true unless PrivateBinPath is specified.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.BasePath">
            <summary>
            The ApplicationBase to use in loading the tests. If not
            specified, and each assembly has its own process, then the
            location of the assembly is used. For multiple  assemblies
            in a single process, the closest common root directory is used.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.ConfigurationFile">
            <summary>
            Path to the config file to use in running the tests.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.DebugAgent">
            <summary>
            Bool flag indicating whether a debugger should be launched at agent
            startup. Used only for debugging NUnit itself.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.PrivateBinPath">
            <summary>
            The private binpath used to locate assemblies. Directory paths
            is separated by a semicolon. It's an error to specify this and
            also set AutoBinPath to true.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.MaxAgents">
            <summary>
            The maximum number of test agents permitted to run simultaneously.
            Ignored if the ProcessModel is not set or defaulted to Multiple.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.RequestedRuntimeFramework">
            <summary>
            Indicates the desired runtime to use for the tests. Values
            are strings like "net-4.5", "mono-4.0", etc. Default is to
            use the target framework for which an assembly was built.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.RequestedFrameworkName">
            <summary>
            Indicates the desired runtime to use for the tests. Values
            are strings like "net-4.5", "mono-4.0", etc. Default is to
            use the target framework for which an assembly was built.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.TargetFrameworkName">
            <summary>
            Indicates the Target runtime selected for use by the engine,
            based on the requested runtime and assembly metadata.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.RequestedAgentName">
            <summary>
            Indicates the name of the agent requested by the user.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.SelectedAgentName">
            <summary>
            Indicates the name of the agent that was actually used.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.RunAsX86">
            <summary>
            Bool flag indicating that the test should be run in a 32-bit process
            on a 64-bit system. By default, NUNit runs in a 64-bit process on
            a 64-bit system. Ignored if set on a 32-bit system.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.DisposeRunners">
            <summary>
            Indicates that test runners should be disposed after the tests are executed
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.ShadowCopyFiles">
            <summary>
            Bool flag indicating that the test assemblies should be shadow copied.
            Defaults to false.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.LoadUserProfile">
            <summary>
            Bool flag indicating that user profile should be loaded on test runner processes
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.SkipNonTestAssemblies">
            <summary>
            Bool flag indicating that non-test assemblies should be skipped without error.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.PrincipalPolicy">
            <summary>
            The PrincipalPolicy to set on the test application domain. Values are:
            "UnauthenticatedPrincipal", "NoPrincipal" and "WindowsPrincipal".
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.DebugTests">
            <summary>
            Flag (bool) indicating whether tests are being debugged.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.PauseBeforeRun">
            <summary>
            Flag (bool) indicating whether to pause execution of tests to allow
            the user to attach a debugger.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.InternalTraceLevel">
            <summary>
            The InternalTraceLevel for this run. Values are: "Default",
            "Off", "Error", "Warning", "Info", "Debug", "Verbose".
            Default is "Off". "Debug" and "Verbose" are synonyms.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.WorkDirectory">
            <summary>
            Full path of the directory to be used for work and result files.
            This path is provided to tests by the framework TestContext.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.ImageRuntimeVersion">
            <summary>
            If the package represents an assembly, then this is the CLR version
            stored in the assembly image. If it represents a project or other
            group of assemblies, it is the maximum version for all the assemblies.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.ImageRequiresX86">
            <summary>
            True if any assembly in the package requires running as a 32-bit
            process when on a 64-bit system.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.ImageRequiresDefaultAppDomainAssemblyResolver">
            <summary>
            True if any assembly in the package requires a special assembly resolution hook
            in the default application domain in order to find dependent assemblies.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.ImageTargetFrameworkName">
            <summary>
            The FrameworkName specified on a TargetFrameworkAttribute for the assembly
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.DefaultTimeout">
            <summary>
            Integer value in milliseconds for the default timeout value
            for test cases. If not specified, there is no timeout except
            as specified by attributes on the tests themselves.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.DefaultCulture">
            <summary>
            A string representing the default thread culture to be used for
            running tests. String should be a valid BCP-47 culture name. If
            culture is unset, tests run on the machine's default culture.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.DefaultUICulture">
            <summary>
            A string representing the default thread UI culture to be used for
            running tests. String should be a valid BCP-47 culture name. If
            culture is unset, tests run on the machine's default culture.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.InternalTraceWriter">
            <summary>
            A TextWriter to which the internal trace will be sent.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.LOAD">
            <summary>
            A list of tests to be loaded.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.NumberOfTestWorkers">
            <summary>
            The number of test threads to run for the assembly. If set to
            1, a single queue is used. If set to 0, tests are executed
            directly, without queuing.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.RandomSeed">
            <summary>
            The random seed to be used for this assembly. If specified
            as the value reported from a prior run, the framework should
            generate identical random values for tests as were used for
            that run, provided that no change has been made to the test
            assembly. Default is a random value itself.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.StopOnError">
            <summary>
            If true, execution stops after the first error or failure.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.ThrowOnEachFailureUnderDebugger">
            <summary>
            If true, asserts in multiple asserts block will throw first-chance exception on failure.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.SynchronousEvents">
            <summary>
            If true, use of the event queue is suppressed and test events are synchronous.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.DefaultTestNamePattern">
            <summary>
            The default naming pattern used in generating test names
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.TestParameters">
            <summary>
            Parameters to be passed on to the tests, serialized to a single string which needs parsing.
            Obsoleted by <see cref="P:NUnit.Common.SettingDefinitions.TestParametersDictionary"/>; kept for backward compatibility.
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.RunOnMainThread">
            <summary>
            If true, the tests will run on the same thread as the NUnit runner itself
            </summary>
        </member>
        <member name="P:NUnit.Common.SettingDefinitions.TestParametersDictionary">
            <summary>
            Parameters to be passed on to the tests, already parsed into an IDictionary&lt;string, string>. Replaces <see cref="P:NUnit.Common.SettingDefinitions.TestParameters"/>.
            </summary>
        </member>
    </members>
</doc>

tools\nunit.engine.dll

md5: 73777B2B41B36FC54816EE0BFBB20FA6 | sha1: 95970E1DA8E6917CE633559FF6763A8E65EEB0A6 | sha256: 65181ACA8EE79BB5DFEBA1A311C8D5F6D3EE63220654934DA817FB771B5D434B | sha512: 63B97434112D8FB9776800D0735E07304DCCB42B95E0403C74ACBE0269B4BC99433C8294ACD234B87DD1776D151BEA931ADCE44AA2A72775568D379FBC103E35

tools\nunit.extensibility.api.dll

md5: 84C2A681F9D7B46EF3F4F942DC413578 | sha1: 68DF42C6BA1F21CF7AC15B6B2C0F2259B536C394 | sha256: 74B05D4D0FF4784EFCAC464CB9C5328B67FF1084F2DD7DFA6C8B3455ECEB006C | sha512: 99E0E004D3E8D7897DB03177B7B9FB05C4AE58621B6D63748521C47916FA6B77E32282EBCA488C43C1EEA51B5A4C5620EF543DBF6F50F931B1B44DB571441DB7

tools\nunit.extensibility.dll

md5: 1CDB25A14258366324ACC10A95C4EB78 | sha1: 25D675652D3AAC3270FBAE6D7236616347B5D623 | sha256: 8877B005A996A0EFF3AEFB8C0943AFBC265AEF078178049BD917392ABCFB9792 | sha512: 7C00E529954CC823C766B6D14B809A29EA28FD08A5AF5221555674AFF62B7CE59CCB6D0A096F9F17070266E323550449D079032894B373A0F69FB9D14510C8A9

tools\TestCentric.Metadata.dll

md5: 2735AF1D5446C560048F3D2450F40F28 | sha1: 40BF9897E93F553EA6A69B39AD50E65D92A822B1 | sha256: 958AA33031E73D350798D41D960C0A32082A16B65DE92F96C1991A74DB229FF2 | sha512: B0C24BA82D4B82270FF510AA44D05F1F9D9580A0BDAAE596B2494D6E2FCED246DEBACA0B28CE4B3D4E2D1CC8315081690A5EE69BF168C5597E87151B8AEFDBFF

tools\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

This package is published by the NUnit Project itself. Any binaries will be 
identical to other package types published by the project, in particular
the NUnit.ConsoleRunner and NUnit.Console NuGet packages.

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
NUnit Console Runner V4 4.0.0-beta001	1	Friday, June 27, 2025	Waiting on dependencies
NUnit 3 Console Runner 3.20.1	4995	Tuesday, May 27, 2025	Approved
NUnit 3 Console Runner 3.20.0	6639	Friday, April 4, 2025	Approved
NUnit 3 Console Runner 3.19.2	9267	Friday, January 31, 2025	Approved
NUnit 3 Console Runner 3.19.1	2336	Sunday, January 19, 2025	Approved
NUnit 3 Console Runner 3.19.0	2982	Friday, December 27, 2024	Approved
NUnit 3 Console Runner 3.18.3	14348	Tuesday, October 8, 2024	Approved
NUnit 3 Console Runner 3.18.2	3479	Thursday, September 19, 2024	Approved
NUnit 3 Console Runner 3.18.1	10246	Thursday, July 18, 2024	Approved
NUnit 3 Console Runner 3.18.0	368	Wednesday, July 17, 2024	Approved
NUnit 3 Console Runner 3.17.0	44907	Wednesday, January 24, 2024	Approved
NUnit 3 Console Runner 3.15.2	14127	Wednesday, June 29, 2022	Approved
NUnit 3 Console Runner 3.15.1	150	Wednesday, June 29, 2022	Approved
NUnit 3 Console Runner 3.15.0	14742	Thursday, February 10, 2022	Approved
NUnit 3 Console Runner 3.15.0-beta1	124	Monday, February 7, 2022	Approved
NUnit 3 Console Runner 3.14.0	3935	Saturday, January 15, 2022	Approved
NUnit 3 Console Runner 3.13.2	1765	Thursday, January 6, 2022	Approved
NUnit 3 Console Runner 3.13.1	334	Tuesday, January 4, 2022	Approved
NUnit 3 Console Runner 3.13.0	3256	Wednesday, December 1, 2021	Approved
NUnit 3 Console Runner 3.12.0	33226	Sunday, January 17, 2021	Approved
NUnit 3 Console Runner 3.12.0-beta1	641	Saturday, August 1, 2020	Approved
NUnit 3 Console Runner 3.11.1	25288	Monday, February 17, 2020	Approved
NUnit 3 Console Runner 3.10.0	39854	Sunday, March 24, 2019	Approved
NUnit 3 Console Runner 3.9.0	11609	Thursday, September 6, 2018	Approved
NUnit 3 Console Runner 3.8.0	31194	Tuesday, January 30, 2018	Approved
NUnit 3 Console Runner 3.7.0	2033	Friday, July 14, 2017	Approved
NUnit 3 Console Runner 3.6.1	8143	Friday, July 7, 2017	Approved

Release Notes

https://docs.nunit.org/articles/nunit/release-notes/console-and-engine.html

Dependencies

- nunit-extension-net462-pluggable-agent (≥ 4.0.0)
- nunit-extension-net80-pluggable-agent (≥ 4.0.0)
- nunit-extension-net90-pluggable-agent (≥ 4.0.0)

Discussion for the NUnit Console Runner V4 Package

Ground Rules:

This discussion is only about NUnit Console Runner V4 and the NUnit Console Runner V4 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 NUnit Console Runner V4, 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.

Resources

Events

Courses

346,995

1

27 Jun 2025

27 Jun 2025

NUnit Console Runner V4

NUnit Console Runner V4 4.0.0-beta001

(Waiting on dependencies)

All Checks are Pending

charliepoole (maintainer) on 27 Jun 2025 23:46:14 +00:00:

Ground Rules: