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

19,501

Downloads of v 1.39.3:

144

Last Update:

22 Jan 2023

Package Maintainer(s):

Starz0r

Software Author(s):

OmniSharp & .NET Foundation

Tags:

lsp ls .net dotnet dotnetcore asp.net mono foss ide

OmniSharp - Roslyn-based C# Language Server

This is not the latest version of OmniSharp - Roslyn-based C# Language Server available.

1.39.3 | Updated: 22 Jan 2023

Downloads:

19,501

Downloads of v 1.39.3:

144

Maintainer(s):

Starz0r

Software Author(s):

OmniSharp & .NET Foundation

Tags:

lsp ls .net dotnet dotnetcore asp.net mono foss ide

OmniSharp - Roslyn-based C# Language Server 1.39.3

This is not the latest version of OmniSharp - Roslyn-based C# Language Server available.

Some Checks Are Exempted or Have Failed

Not All Tests Have Passed

Hide Checks

Validation Testing Passed

Verification Testing Exemption:

.NET Dependency requires restart.

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install OmniSharp - Roslyn-based C# Language Server, run the following command from the command line or from PowerShell:

To upgrade OmniSharp - Roslyn-based C# Language Server, run the following command from the command line or from PowerShell:

To uninstall OmniSharp - Roslyn-based C# Language Server, run the following command from the command line or from PowerShell:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

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

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download

Option 2: Internalized Package (Reliable, Scalable)

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

Package Internalizer (C4B)

Run: (additional options)

choco download omnisharp --internalize --version=1.39.3 --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

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

Automate package internalization

3. Copy Your Script

choco upgrade omnisharp -y --source="'INTERNAL REPO URL'" --version="'1.39.3'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade omnisharp -y --source="'INTERNAL REPO URL'" --version="'1.39.3'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode


- name: Install omnisharp
  win_chocolatey:
    name: omnisharp
    version: '1.39.3'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'omnisharp' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.39.3'
end

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


cChocoPackageInstaller omnisharp
{
    Name     = "omnisharp"
    Version  = "1.39.3"
    Source   = "INTERNAL REPO URL"
}

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


package { 'omnisharp':
  ensure   => '1.39.3',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 22 Jan 2023.

Description

Introduction

OmniSharp is a .NET development platform based on Roslyn workspaces. It provides project dependencies and C# language services to various IDEs and plugins.

OmniSharp is built with the .NET Core SDK on Windows and Mono on OSX/Linux. It targets the net472 target framework. For platforms other than Windows, OmniSharp ships with an embedded Mono which is based on version 5.18.0, includes MSBuild 16.3.0 and is provisioned during the build script. If Mono is globally installed on the system, OmniSharp will prefer it over the embedded version, however version >=6.4.0 is required (the lowest version with at least MSBuild 16.3.0).

Configuration

OmniSharp provides a rich set of hierarchical configuration options, controlled via startup arguments, environment variables and omnisharp.json file. For more details please visit the Configuration Options section of the wiki.

License

OmniSharp is provided as-is under the MIT license. For more information see LICENSE.

.NET Foundation

This project is supported by the .NET Foundation.

Files

legal\LICENSE.txt

MIT License

Copyright (c) .NET Foundation and Contributors All Rights Reserved

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.

legal\VERIFICATION.txt

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

Package can be verified like this:

1. Go to https://github.com/OmniSharp/omnisharp-roslyn, enter to releases and download from there.

   x32: https://github.com/OmniSharp/omnisharp-roslyn/releases/download/v1.39.3/omnisharp-win-x86.zip
   x64: https://github.com/OmniSharp/omnisharp-roslyn/releases/download/v1.39.3/omnisharp-win-x64.zip

   to download the zip files. You may wish to rename one of the files.

2. You can use one of the following methods to obtain the SHA512 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum: f37ff40599a54a799e8c2eec0770cd2cd069c1cd36f2ef716b48ec69ed25be6d7a0a5832df58b09da9853f1ac0f103013f4879e4048f70b9102f1d36ff6dd2ba
   checksum64: 7b3be1d80476c99d82f5f32c0cf2610fb947c61a348ba363fe0a1a53e15213d1d58b26b9a0a20c87ce0a232a3b1e1af7afeba3bab575b1066612ce49b1b07717

File 'LICENSE.txt' obtained from:
   https://github.com/OmniSharp/omnisharp-roslyn/blob/v1.39.3/license.md

tools\chocolateyinstall.ps1

$ToolsPath = Split-Path $MyInvocation.MyCommand.Definition

$PackageArgs = @{
	PackageName = "omnisharp"
	FileFullPath = Get-Item $ToolsPath\*-win-x86*.zip
	FileFullPath64 = Get-Item $ToolsPath\*-win-x64*.zip
	Destination = $ToolsPath
}
Get-ChildItem $ToolsPath\* | Where-Object { $_.PSISContainer } | Remove-Item -Recurse -Force #remove older package dirs

New-Item -Type Directory $ToolsPath\.msbuild\Current\Bin\ -EA 0
New-Item -ItemType file $ToolsPath\.msbuild\Current\Bin\MSBuild.exe.ignore -EA 0

New-Item -Type Directory $ToolsPath\.msbuild\Current\Bin\Roslyn\ -EA 0
New-Item -ItemType file $ToolsPath\.msbuild\Current\Bin\Roslyn\csc.exe.ignore -EA 0
New-Item -ItemType file $ToolsPath\.msbuild\Current\Bin\Roslyn\csi.exe.ignore -EA 0

Get-ChocolateyUnzip @PackageArgs
Remove-Item $ToolsPath\*.zip -ea 0

tools\omnisharp-win-x64.zip

md5: 2915882015CF48BAD197BE7A9C16276C | sha1: 2E32590E3C3FEE684A176A93DA60A122917A3157 | sha256: DD676997EA60069BB00A68E46C06D5373880F679D26544488DC0540B39605C30 | sha512: 7B3BE1D80476C99D82F5F32C0CF2610FB947C61A348BA363FE0A1A53E15213D1D58B26B9A0A20C87CE0A232A3B1E1AF7AFEBA3BAB575B1066612CE49B1B07717

tools\omnisharp-win-x86.zip

md5: 2E3DB5A0FB62576A796E994D2271417F | sha1: 909E61FB8618B0817D5FC7807033AD2513DE43BE | sha256: 54B9E3E025A2BB939C75ECAE3ED86EB3C512D47A20A734F0325123D6C7A38CE5 | sha512: F37FF40599A54A799E8C2EEC0770CD2CD069C1CD36F2EF716B48EC69ED25BE6D7A0A5832DF58B09DA9853F1AC0F103013F4879E4048F70B9102F1D36FF6DD2BA

Virus Scan Results

System.ValueTuple.dll (e905d102585b) - ## / 70
System.Numerics.Vectors.dll (1d3ef8698281) - ## / 71
System.Buffers.dll (accccfbe45d9) - ## / 71
System.Threading.Tasks.Extensions.dll (4f81ffd0dc72) - ## / 70
Microsoft.CSharp.dll (6cfe772d861e) - ## / 68
Microsoft.Win32.Primitives.dll (422c576324c2) - ## / 70
mscorlib.dll (a69849cf0b43) - ## / 68
netstandard.dll (9f12554ddf1f) - ## / 65
System.AppContext.dll (aeb0c192ded6) - ## / 66
System.Collections.Concurrent.dll (43bc5789c568) - ## / 66
System.Collections.dll (af67ff988166) - ## / 68
System.Collections.NonGeneric.dll (254652680321) - ## / 68
System.Collections.Specialized.dll (de59d3145e4d) - ## / 54
System.ComponentModel.Annotations.dll (86e28bb43126) - ## / 68
System.ComponentModel.Composition.dll (cbc118a76197) - ## / 68
System.ComponentModel.DataAnnotations.dll (4137ddf6ad96) - ## / 68
System.ComponentModel.dll (19d1af8356a7) - ## / 69
System.ComponentModel.EventBasedAsync.dll (9b4b2b4e51cb) - ## / 69
System.ComponentModel.Primitives.dll (bdba04268274) - ## / 68
System.ComponentModel.TypeConverter.dll (24772d08a1c9) - ## / 68
System.Configuration.dll (86f992e4e5e2) - ## / 69
System.Console.dll (64175d5a1d37) - ## / 68
System.Core.dll (f9c65f2d44f2) - ## / 66
System.Data.Common.dll (7f465aa7f039) - ## / 60
System.Data.dll (05e52f112998) - ## / 67
System.Diagnostics.Contracts.dll (0e78fc6d67c6) - ## / 68
System.Diagnostics.Debug.dll (3c3f7cab9a0a) - ## / 66
System.Diagnostics.FileVersionInfo.dll (14acb343dc7e) - ## / 67
System.Diagnostics.Process.dll (03d2951dc644) - ## / 69
System.Diagnostics.StackTrace.dll (9397e515df95) - ## / 67
System.Diagnostics.TextWriterTraceListener.dll (8329f22ca6dd) - ## / 69
System.Diagnostics.Tools.dll (adf05606fb26) - ## / 67
System.Diagnostics.TraceSource.dll (c3546409e08a) - ## / 67
System.dll (541c6067cc69) - ## / 69
System.Drawing.dll (3952f3c019ef) - ## / 68
System.Drawing.Primitives.dll (101204d45b0d) - ## / 68
System.Dynamic.Runtime.dll (a71056ef924b) - ## / 66
System.Globalization.Calendars.dll (8b83df271fe2) - ## / 69
System.Globalization.dll (a7748f2e16a3) - ## / 68
System.Globalization.Extensions.dll (ced974159ed1) - ## / 62
System.IdentityModel.dll (718709147fd4) - ## / 69
System.IO.Compression.dll (e9c71ebf6531) - ## / 68
System.IO.Compression.FileSystem.dll (06f159db143a) - ## / 69
System.IO.Compression.ZipFile.dll (8815553168d0) - ## / 66
System.IO.dll (c7c68eb6d9cb) - ## / 70
System.IO.FileSystem.dll (f768c4b1ca93) - ## / 67
System.IO.FileSystem.DriveInfo.dll (874d314eb22b) - ## / 69
System.IO.FileSystem.Primitives.dll (d2a465c68c92) - ## / 62
System.IO.FileSystem.Watcher.dll (b4218f8eecdd) - ## / 62
System.IO.IsolatedStorage.dll (f985ea228254) - ## / 69
System.IO.MemoryMappedFiles.dll (953378edb624) - ## / 68
System.IO.Pipes.dll (0117d5612c93) - ## / 63
System.IO.UnmanagedMemoryStream.dll (7afce03561a1) - ## / 64
System.Linq.dll (4248987837af) - ## / 69
System.Linq.Expressions.dll (db69a2784660) - ## / 71
System.Linq.Parallel.dll (b096ba2ff76d) - ## / 69
System.Linq.Queryable.dll (c93ebbbdeb5f) - ## / 69
System.Net.Http.dll (cb1b1ac1c1a4) - ## / 68
System.Net.Http.Rtc.dll (851f30aa79eb) - ## / 69
System.Net.Http.WebRequest.dll (d298f0538281) - ## / 68
System.Net.NameResolution.dll (112bfd417f73) - ## / 67
System.Net.NetworkInformation.dll (e53192390660) - ## / 69
System.Net.Ping.dll (a2a2f93d4b1d) - ## / 68
System.Net.Primitives.dll (6555340a9cfb) - ## / 66
System.Net.Requests.dll (bd6788ca971b) - ## / 64
System.Net.Security.dll (de8cb7fb3510) - ## / 68
System.Net.Sockets.dll (0d8990dce312) - ## / 63
System.Net.WebHeaderCollection.dll (254ccb0ba11d) - ## / 68
System.Net.WebSockets.Client.dll (44cf0814b0a9) - ## / 67
System.Net.WebSockets.dll (97e5b0209267) - ## / 68
System.Numerics.dll (716c1be731f8) - ## / 66
System.ObjectModel.dll (eb2632388987) - ## / 65
System.Reflection.dll (9aae49d6e062) - ## / 67
System.Reflection.Emit.dll (7bbe588e2d57) - ## / 68
System.Reflection.Emit.ILGeneration.dll (4c41c9fae4fc) - ## / 68
System.Reflection.Emit.Lightweight.dll (c8f5efcdec7e) - ## / 68
System.Reflection.Extensions.dll (d0e5a644966d) - ## / 68
System.Reflection.Primitives.dll (75a03e5d42c8) - ## / 68
System.Resources.Reader.dll (abc4e7b9fbcc) - ## / 68
System.Resources.ResourceManager.dll (727d30b0ce76) - ## / 69
System.Resources.Writer.dll (40d22d96ef4c) - ## / 68
System.Runtime.CompilerServices.VisualC.dll (6aa86e132362) - ## / 69
System.Runtime.dll (0db3fd1a1a59) - ## / 70
System.Runtime.Extensions.dll (3df76ee0abf0) - ## / 66
System.Runtime.Handles.dll (0399d09b1723) - ## / 68
System.Runtime.InteropServices.dll (ef477238e988) - ## / 68
System.Runtime.InteropServices.RuntimeInformation.dll (7ec6a13884bc) - ## / 66
System.Runtime.InteropServices.WindowsRuntime.dll (813551bb988b) - ## / 67
System.Runtime.Numerics.dll (79b7cc597a35) - ## / 63
System.Runtime.Serialization.dll (a8a8240fc53a) - ## / 68
System.Runtime.Serialization.Formatters.dll (8627878266f3) - ## / 68
System.Runtime.Serialization.Json.dll (f5f266facdf6) - ## / 67
System.Runtime.Serialization.Primitives.dll (075d45612936) - ## / 69
System.Runtime.Serialization.Xml.dll (0a63bcd65f5f) - ## / 69
System.Security.Claims.dll (7489b9245f16) - ## / 67
System.Security.Cryptography.Algorithms.dll (06a395bbb252) - ## / 69
System.Security.Cryptography.Csp.dll (1040ebda9719) - ## / 68
System.Security.Cryptography.Encoding.dll (b17c3690aaa9) - ## / 70
System.Security.Cryptography.Primitives.dll (3a170e6e7a7a) - ## / 70
System.Security.Cryptography.X509Certificates.dll (029ef4afa7d7) - ## / 70
System.Security.dll (ecfea3a2db50) - ## / 67
System.Security.Principal.dll (e41d1edd0986) - ## / 69
System.Security.SecureString.dll (cb849ac7393b) - ## / 70
System.ServiceModel.dll (e2b3edd57520) - ## / 69
System.ServiceModel.Duplex.dll (6cb33155f94f) - ## / 67
System.ServiceModel.Http.dll (0c1f0ae577ab) - ## / 66
System.ServiceModel.NetTcp.dll (12ec3c846465) - ## / 66
System.ServiceModel.Primitives.dll (22fd62fd58a3) - ## / 68
System.ServiceModel.Security.dll (b886672774bb) - ## / 70
System.Text.Encoding.dll (c4c7bc45dd19) - ## / 68
System.Text.Encoding.Extensions.dll (5f5c2af78d0b) - ## / 61
System.Text.RegularExpressions.dll (1f826d4a5a9b) - ## / 69
System.Threading.dll (3ad700ed8700) - ## / 59
System.Threading.Overlapped.dll (e2358e2da77e) - ## / 68
System.Threading.Tasks.dll (ef502fc69295) - ## / 69
System.Threading.Tasks.Parallel.dll (09ba8778e164) - ## / 70
System.Threading.Thread.dll (180903fc274d) - ## / 66
System.Threading.ThreadPool.dll (f75192d385d1) - ## / 66
System.Threading.Timer.dll (aee0eecb6d12) - ## / 66
System.Windows.dll (558919bc043c) - ## / 70
System.Windows.Forms.dll (dce07962d75e) - ## / 69
System.Xml.dll (a01c28f804dc) - ## / 67
System.Xml.Linq.dll (d37cb2217485) - ## / 69
System.Xml.ReaderWriter.dll (9fe8f881db36) - ## / 68
System.Xml.XDocument.dll (60df9e02969c) - ## / 69
System.Xml.XmlDocument.dll (e21ee61844b7) - ## / 68
System.Xml.XmlSerializer.dll (0763eb17035c) - ## / 70
System.Xml.XPath.dll (57a33c14b59d) - ## / 48
System.Xml.XPath.XDocument.dll (16c19ca6e0b4) - ## / 65
WindowsBase.dll (c7c11b809630) - ## / 69
System.Reflection.DispatchProxy.dll (7d2e56e0dad6) - ## / 68
System.Reflection.DispatchProxy.dll (b2542ac196fc) - ## / 66
MediatR.dll (21513425c042) - ## / 67
Microsoft.CodeAnalysis.AnalyzerUtilities.dll (27300b349ae0) - ## / 70
System.Buffers.dll (6f80d131c025) - ## / 70
System.Numerics.Vectors.dll (6ade595b1b09) - ## / 70
System.ValueTuple.dll (48f394668836) - ## / 69
Microsoft.DotNet.PlatformAbstractions.dll (f0f60c925729) - ## / 70
System.Reflection.Metadata.dll (46451e1168dd) - ## / 71
Microsoft.Win32.Registry.dll (e9a9d281c1a7) - ## / 70
System.Security.AccessControl.dll (1fda491eebdb) - ## / 69
System.Security.Principal.Windows.dll (b4d8e15adc23) - ## / 71
Newtonsoft.Json.dll (b624949df8b0) - ## / 70
Microsoft.Build.Locator.dll (8f223d6c9436) - ## / 70
McMaster.Extensions.CommandLineUtils.dll (9e20c3457fd6) - ## / 67
Microsoft.Bcl.AsyncInterfaces.dll (295af2142d92) - ## / 71
Microsoft.Extensions.Configuration.Abstractions.dll (4891b08c0157) - ## / 71
Microsoft.Extensions.Configuration.Binder.dll (ae8a3884e65a) - ## / 69
Microsoft.Extensions.Configuration.CommandLine.dll (f6c70d449e1f) - ## / 71
Microsoft.Extensions.Configuration.dll (28c12f7523fe) - ## / 67
Microsoft.Extensions.Configuration.FileExtensions.dll (f8c75555c27e) - ## / 69
Microsoft.Extensions.Configuration.Json.dll (aaa1112f9547) - ## / 70
Microsoft.Extensions.FileProviders.Abstractions.dll (090b71568672) - ## / 71
Microsoft.Extensions.FileProviders.Physical.dll (b00b024aed95) - ## / 71
Microsoft.Extensions.FileSystemGlobbing.dll (fc4c05b3c4fe) - ## / 71
Microsoft.Extensions.Primitives.dll (60df37bef5b4) - ## / 69
System.Runtime.CompilerServices.Unsafe.dll (37768488e8ef) - ## / 71
System.Text.Encodings.Web.dll (78eb5b4fee58) - ## / 70
System.Text.Json.dll (d125f0f7e2ec) - ## / 68
Microsoft.Extensions.DependencyInjection.Abstractions.dll (95a7c66abd60) - ## / 69
Microsoft.Extensions.DependencyInjection.dll (d6de20035b25) - ## / 69
ICSharpCode.Decompiler.dll (1a912e396b14) - ## / 69
System.Text.Encoding.CodePages.dll (87f7f43626ca) - ## / 69
System.Composition.AttributedModel.dll (9e2ddd309d78) - ## / 71
System.Composition.Convention.dll (655876e3b227) - ## / 71
System.Composition.Hosting.dll (9942f2e01bc8) - ## / 71
System.Composition.Runtime.dll (51eb1d16ac34) - ## / 70
System.Composition.TypedParts.dll (7b0bec6c7628) - ## / 71
Microsoft.Extensions.Caching.Abstractions.dll (ac340b9d4966) - ## / 69
Microsoft.Extensions.Logging.Abstractions.dll (050405babe52) - ## / 69
Microsoft.Extensions.Logging.dll (4d1ca57435ba) - ## / 69
Microsoft.Extensions.Options.dll (ac83168b7316) - ## / 69
System.Diagnostics.DiagnosticSource.dll (81e664880042) - ## / 69
System.Collections.Immutable.dll (69e57ac41220) - ## / 62
System.Memory.dll (bf3fb84664f4) - ## / 70
omnisharp.1.39.3.nupkg (281eace5f1c8) - ## / 62
omnisharp-win-x64.zip (dd676997ea60) - ## / 64
omnisharp-win-x86.zip (54b9e3e025a2) - ## / 63
Cake.Scripting.Abstractions.dll (1129f7facddf) - ## / 67
Cake.Scripting.Transport.dll (97cd42bb6c88) - ## / 69
Dotnet.Script.DependencyModel.dll (fcc3651106cd) - ## / 69
Dotnet.Script.DependencyModel.NuGet.dll (383b61b05ba1) - ## / 68
Humanizer.dll (2c522cd285de) - ## / 69
Microsoft.CodeAnalysis.CSharp.dll (5edbe28ca2f5) - ## / 69
Microsoft.CodeAnalysis.CSharp.Features.dll (3b06d4f6bc06) - ## / 68
Microsoft.CodeAnalysis.CSharp.Scripting.dll (c45f599c2d08) - ## / 67
Microsoft.CodeAnalysis.CSharp.Workspaces.dll (7219548e9aab) - ## / 69
Microsoft.CodeAnalysis.dll (ba60a23516dd) - ## / 69
Microsoft.CodeAnalysis.Elfie.dll (d97647105e6e) - ## / 69
Microsoft.CodeAnalysis.ExternalAccess.OmniSharp.CSharp.dll (0048729c3183) - ## / 66
Microsoft.CodeAnalysis.ExternalAccess.OmniSharp.dll (80eb49950a8d) - ## / 69
Microsoft.CodeAnalysis.Features.dll (b8e6b1b8162b) - ## / 69
Microsoft.CodeAnalysis.Scripting.dll (78a10a283586) - ## / 69
Microsoft.CodeAnalysis.Workspaces.dll (0806e76183a0) - ## / 69
Microsoft.DiaSymReader.dll (2962ddec95ce) - ## / 69
Microsoft.Extensions.Caching.Memory.dll (6528f3d3a7d8) - ## / 69
Microsoft.Extensions.Configuration.EnvironmentVariables.dll (c617025de517) - ## / 68
Microsoft.Extensions.DependencyModel.dll (84791ab89f0e) - ## / 67
Microsoft.Extensions.Logging.Configuration.dll (9a1622c707b4) - ## / 70
Microsoft.Extensions.Logging.Console.dll (3ff648027f8d) - ## / 69
Microsoft.Extensions.Options.ConfigurationExtensions.dll (43f4bf9114f6) - ## / 70
Microsoft.TestPlatform.CommunicationUtilities.dll (ae9690824f10) - ## / 69
Microsoft.TestPlatform.CoreUtilities.dll (5efb930a4bbf) - ## / 69
Microsoft.TestPlatform.PlatformAbstractions.dll (33ad6e30bd4a) - ## / 71
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.dll (46b0deed8871) - ## / 69
Microsoft.VisualStudio.TestPlatform.Common.dll (bb357049b563) - ## / 69
Microsoft.VisualStudio.TestPlatform.ObjectModel.dll (52011dd1e0f4) - ## / 70
Microsoft.VisualStudio.Threading.dll (c9256c45a807) - ## / 70
Microsoft.VisualStudio.Validation.dll (320aa2bccdd7) - ## / 69
Nerdbank.Streams.dll (1cbc3522786a) - ## / 69
NuGet.Common.dll (13edb620aa96) - ## / 70
NuGet.Configuration.dll (113c64b71a56) - ## / 69
NuGet.DependencyResolver.Core.dll (06205ecefa1d) - ## / 70
NuGet.Frameworks.dll (fe3beeb125ca) - ## / 70
NuGet.LibraryModel.dll (e99e01ecb82e) - ## / 70
NuGet.Packaging.Core.dll (c7077b1c53ff) - ## / 70
NuGet.Packaging.dll (4064c37324c5) - ## / 70
NuGet.ProjectModel.dll (eefb4eb8d1f6) - ## / 69
NuGet.Protocol.dll (8c2d400ae139) - ## / 69
NuGet.Versioning.dll (992d663a4083) - ## / 70
OmniSharp.Abstractions.dll (c19ba3da2fe0) - ## / 69
OmniSharp.Cake.dll (4ff00d4acfe3) - ## / 68
OmniSharp.DotNetTest.dll (55e5c148b088) - ## / 69
OmniSharp.exe (1bc5f1498855) - ## / 71
OmniSharp.Extensions.JsonRpc.dll (ef87ce895d4f) - ## / 69
OmniSharp.Extensions.LanguageProtocol.dll (b51c1ea18c65) - ## / 68
OmniSharp.Extensions.LanguageServer.dll (7f4f7b97e8b6) - ## / 69
OmniSharp.Extensions.LanguageServer.Shared.dll (e719b8404e2d) - ## / 69
OmniSharp.Host.dll (c39667c99789) - ## / 68
OmniSharp.LanguageServerProtocol.dll (503de9ace44c) - ## / 69
OmniSharp.MSBuild.dll (99f9e7488e58) - ## / 69
OmniSharp.Roslyn.CSharp.dll (16c09c20a202) - ## / 68
OmniSharp.Roslyn.dll (04a88b3fb6b2) - ## / 69
OmniSharp.Script.dll (bf814cdd71d4) - ## / 69
OmniSharp.Shared.dll (975292625dff) - ## / 69
OmniSharp.Stdio.dll (77f86c55ad00) - ## / 69
System.IO.Pipelines.dll (07b365ae13d5) - ## / 69
System.Reactive.dll (ea69ae3af1cf) - ## / 69
System.Threading.Channels.dll (401398f46179) - ## / 70
System.Threading.Tasks.Dataflow.dll (61213ff92413) - ## / 69
OmniSharp.exe (52b415cd36e9) - ## / 70
OmniSharp.LanguageServerProtocol.dll (8d666b8f0da9) - ## / 68
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (c5d7d98af5d1) - ## / 69
Microsoft.CodeAnalysis.CSharp.resources.dll (6f03cb62a020) - ## / 69
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (11f5e1d088fd) - ## / 69
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (34118aedd67c) - ## / 69
Microsoft.CodeAnalysis.Features.resources.dll (d1c6fc538bf2) - ## / 66
Microsoft.CodeAnalysis.resources.dll (280d93b5359f) - ## / 69
Microsoft.CodeAnalysis.Scripting.resources.dll (61bdef25c8a2) - ## / 68
Microsoft.CodeAnalysis.Workspaces.resources.dll (721bda9c5a32) - ## / 69
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (5907c3972f68) - ## / 71
Microsoft.TestPlatform.CoreUtilities.resources.dll (e53dfc223dc6) - ## / 68
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (62fed524488c) - ## / 68
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (f3614f8dc410) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (9e4ffbb8632c) - ## / 71
Microsoft.VisualStudio.Threading.resources.dll (cab34f3b0aeb) - ## / 69
Microsoft.VisualStudio.Validation.resources.dll (ffcdaed7c0e5) - ## / 70
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (6bc2edf5c8be) - ## / 69
Microsoft.CodeAnalysis.CSharp.resources.dll (f703ae9ce9d1) - ## / 47
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (73b43701dfab) - ## / 65
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (64b82373ddf2) - ## / 69
Microsoft.CodeAnalysis.Features.resources.dll (9f2eeb2e08b9) - ## / 69
Microsoft.CodeAnalysis.resources.dll (6b991d8f18ee) - ## / 69
Microsoft.CodeAnalysis.Scripting.resources.dll (c29728e2035f) - ## / 67
Microsoft.CodeAnalysis.Workspaces.resources.dll (e92fe5e398fd) - ## / 69
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (1d1ea6f15697) - ## / 71
Microsoft.TestPlatform.CoreUtilities.resources.dll (c8ca52402bc7) - ## / 71
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (90a9f9519582) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (388f1acc02bc) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (857c909145b9) - ## / 70
Microsoft.VisualStudio.Threading.resources.dll (e874c1c709a0) - ## / 71
Microsoft.VisualStudio.Validation.resources.dll (bc4cbcec6e90) - ## / 70
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (e223324086c6) - ## / 69
Microsoft.CodeAnalysis.CSharp.resources.dll (a859ad5299c1) - ## / 59
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (32830c57be0b) - ## / 67
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (00cf955af1c4) - ## / 68
Microsoft.CodeAnalysis.Features.resources.dll (7b5eabcae969) - ## / 68
Microsoft.CodeAnalysis.resources.dll (dca6b96e7cc3) - ## / 69
Microsoft.CodeAnalysis.Scripting.resources.dll (2a38eb2e3f8d) - ## / 67
Microsoft.CodeAnalysis.Workspaces.resources.dll (ff0c0c7b87ec) - ## / 69
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (87218f0e62c4) - ## / 71
Microsoft.TestPlatform.CoreUtilities.resources.dll (c58033cd59e8) - ## / 71
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (69e04089a408) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (aa2141af08f0) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (cda37fa2cd04) - ## / 70
Microsoft.VisualStudio.Threading.resources.dll (c45d42085c33) - ## / 70
Microsoft.VisualStudio.Validation.resources.dll (2fcbf1e1c8e8) - ## / 69
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (700a7647d2b3) - ## / 68
Microsoft.CodeAnalysis.CSharp.resources.dll (3188a529b1b1) - ## / 68
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (0c53552de328) - ## / 68
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (b837af66b11f) - ## / 69
Microsoft.CodeAnalysis.Features.resources.dll (dd8fd791daf8) - ## / 68
Microsoft.CodeAnalysis.resources.dll (320f436124b5) - ## / 68
Microsoft.CodeAnalysis.Scripting.resources.dll (69046f4f1f86) - ## / 69
Microsoft.CodeAnalysis.Workspaces.resources.dll (0bd8b391dbb5) - ## / 68
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (4368b2c300d5) - ## / 71
Microsoft.TestPlatform.CoreUtilities.resources.dll (b62ac1f9c5a7) - ## / 69
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (19b2ff60255f) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (3d8c363d6fc9) - ## / 70
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (14563127994a) - ## / 70
Microsoft.VisualStudio.Threading.resources.dll (edfdddada172) - ## / 70
Microsoft.VisualStudio.Validation.resources.dll (db4a7bc6df32) - ## / 71
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (4301f33ca96b) - ## / 68
Microsoft.CodeAnalysis.CSharp.resources.dll (5d97adfee47e) - ## / 68
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (0594228c4fff) - ## / 69
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (a10aa0ac2faf) - ## / 69
Microsoft.CodeAnalysis.Features.resources.dll (3d16ab4e3f18) - ## / 69
Microsoft.CodeAnalysis.resources.dll (c97d8bcf82ec) - ## / 69
Microsoft.CodeAnalysis.Scripting.resources.dll (605de9c1c94f) - ## / 69
Microsoft.CodeAnalysis.Workspaces.resources.dll (cb3cdf57e101) - ## / 67
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (c946e7488c3e) - ## / 70
Microsoft.TestPlatform.CoreUtilities.resources.dll (caa86e5100bf) - ## / 67
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (cb0951e12caa) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (bbf4a8384ef5) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (be9081f36f5c) - ## / 70
Microsoft.VisualStudio.Threading.resources.dll (176b50313b05) - ## / 70
Microsoft.VisualStudio.Validation.resources.dll (a52a7166a00c) - ## / 71
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (a4a0da763e33) - ## / 69
Microsoft.CodeAnalysis.CSharp.resources.dll (87e3fb5c6990) - ## / 69
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (d5d8adc606d6) - ## / 69
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (be8b18673535) - ## / 69
Microsoft.CodeAnalysis.Features.resources.dll (c49ff0806a92) - ## / 69
Microsoft.CodeAnalysis.resources.dll (c4e637dd9104) - ## / 68
Microsoft.CodeAnalysis.Scripting.resources.dll (f5e7c1fff533) - ## / 69
Microsoft.CodeAnalysis.Workspaces.resources.dll (ef250f371d90) - ## / 66
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (d98302514f9a) - ## / 70
Microsoft.TestPlatform.CoreUtilities.resources.dll (1580a956194d) - ## / 70
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (1ee632dfd584) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (d6e9969b9217) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (68ea4931bbdc) - ## / 67
Microsoft.VisualStudio.Threading.resources.dll (48a4b54fc16e) - ## / 66
Microsoft.VisualStudio.Validation.resources.dll (bb78f2772c8c) - ## / 71
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (d7c60af61098) - ## / 67
Microsoft.CodeAnalysis.CSharp.resources.dll (9181c44c9c6d) - ## / 67
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (5095adb955f3) - ## / 68
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (d423939e33ed) - ## / 68
Microsoft.CodeAnalysis.Features.resources.dll (80208af56c13) - ## / 69
Microsoft.CodeAnalysis.resources.dll (9313c589d128) - ## / 67
Microsoft.CodeAnalysis.Scripting.resources.dll (4ac4320051e4) - ## / 66
Microsoft.CodeAnalysis.Workspaces.resources.dll (21823360c313) - ## / 69
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (348e43812b8f) - ## / 71
Microsoft.TestPlatform.CoreUtilities.resources.dll (e786d3ad8b56) - ## / 70
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (00c9505b3303) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (18c6e3d8dc7a) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (7d69adcc946d) - ## / 70
Microsoft.VisualStudio.Threading.resources.dll (8b1367f34a53) - ## / 70
Microsoft.VisualStudio.Validation.resources.dll (a8e562c5a371) - ## / 68
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (760f20187442) - ## / 68
Microsoft.CodeAnalysis.CSharp.resources.dll (704e4083e256) - ## / 68
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (4ba0003384a0) - ## / 69
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (b98846f18abe) - ## / 69
Microsoft.CodeAnalysis.Features.resources.dll (602a0de6209b) - ## / 69
Microsoft.CodeAnalysis.resources.dll (a2cf3beec7b0) - ## / 68
Microsoft.CodeAnalysis.Scripting.resources.dll (50cb59bbc08a) - ## / 69
Microsoft.CodeAnalysis.Workspaces.resources.dll (7ed80ac212e1) - ## / 67
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (af541b9adcff) - ## / 70
Microsoft.TestPlatform.CoreUtilities.resources.dll (ea754c7eaeec) - ## / 70
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (a2297631080e) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (e1315c27b3f5) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (f09f23b741ed) - ## / 67
Microsoft.VisualStudio.Threading.resources.dll (72066982a7b4) - ## / 60
Microsoft.VisualStudio.Validation.resources.dll (0c9f1d059c13) - ## / 70
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (f3ec74463a3a) - ## / 67
Microsoft.CodeAnalysis.CSharp.resources.dll (78e8aeb6dadc) - ## / 69
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (85557a438541) - ## / 68
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (562ca29e3363) - ## / 68
Microsoft.CodeAnalysis.Features.resources.dll (edcff9638874) - ## / 69
Microsoft.CodeAnalysis.resources.dll (19fdf4bf0f44) - ## / 69
Microsoft.CodeAnalysis.Scripting.resources.dll (d1da5121d393) - ## / 69
Microsoft.CodeAnalysis.Workspaces.resources.dll (56733eb7bfc4) - ## / 69
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (41643d457365) - ## / 71
Microsoft.TestPlatform.CoreUtilities.resources.dll (79cffcbf9cf4) - ## / 70
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (bd20ccac310e) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (2c6ca7a77f93) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (c9bd9ef5bb4b) - ## / 69
Microsoft.VisualStudio.Threading.resources.dll (20af52be9be7) - ## / 70
Microsoft.VisualStudio.Validation.resources.dll (cc8e0a574b08) - ## / 68
Microsoft.Win32.Registry.dll (53af8a99b0ed) - ## / 69
System.Data.DataSetExtensions.dll (1706e139187e) - ## / 69
System.Security.AccessControl.dll (53f6d2f69008) - ## / 65
System.Security.Principal.Windows.dll (80aa44791b8a) - ## / 70
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (d6d85dd17b03) - ## / 68
Microsoft.CodeAnalysis.CSharp.resources.dll (a0f90fa5d9c9) - ## / 67
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (f0d7d8d85791) - ## / 67
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (a9ca7d42312a) - ## / 69
Microsoft.CodeAnalysis.Features.resources.dll (6294d61f8874) - ## / 69
Microsoft.CodeAnalysis.resources.dll (24e79d9ef4ac) - ## / 68
Microsoft.CodeAnalysis.Scripting.resources.dll (d449e592c71d) - ## / 67
Microsoft.CodeAnalysis.Workspaces.resources.dll (1033257edcd5) - ## / 69
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (3686fd851e18) - ## / 69
Microsoft.TestPlatform.CoreUtilities.resources.dll (b41fd8839a41) - ## / 70
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (e457a77e1093) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (f1490d15eaa1) - ## / 68
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (e9859e2fa08c) - ## / 70
Microsoft.VisualStudio.Threading.resources.dll (02aff2dee8df) - ## / 71
Microsoft.VisualStudio.Validation.resources.dll (ac81da84ea36) - ## / 71
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (606ef3a3a8fe) - ## / 69
Microsoft.CodeAnalysis.CSharp.resources.dll (b5cf839f1a3e) - ## / 69
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (26065aeb4450) - ## / 68
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (4c639f41e973) - ## / 68
Microsoft.CodeAnalysis.Features.resources.dll (85147c154d06) - ## / 66
Microsoft.CodeAnalysis.resources.dll (2d17577e19ae) - ## / 65
Microsoft.CodeAnalysis.Scripting.resources.dll (314604146efc) - ## / 68
Microsoft.CodeAnalysis.Workspaces.resources.dll (35dc41e7d7d3) - ## / 69
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (dcc2a08af988) - ## / 71
Microsoft.TestPlatform.CoreUtilities.resources.dll (1ac38cb37cbc) - ## / 71
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (cd064a5a6cab) - ## / 70
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (4d8f2d23a34c) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (569917551c38) - ## / 70
Microsoft.VisualStudio.Threading.resources.dll (eb44752accda) - ## / 70
Microsoft.VisualStudio.Validation.resources.dll (5bcfe72b86f9) - ## / 70
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (87c39eb5e429) - ## / 65
Microsoft.CodeAnalysis.CSharp.resources.dll (e61fdd180a73) - ## / 69
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (f6da74657810) - ## / 68
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (27abd8ef0520) - ## / 68
Microsoft.CodeAnalysis.Features.resources.dll (f5c087f785f9) - ## / 69
Microsoft.CodeAnalysis.resources.dll (a368ff3225e1) - ## / 69
Microsoft.CodeAnalysis.Scripting.resources.dll (ab8f1c2274db) - ## / 68
Microsoft.CodeAnalysis.Workspaces.resources.dll (892757ec000b) - ## / 65
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (593066c1f3b2) - ## / 71
Microsoft.TestPlatform.CoreUtilities.resources.dll (7d3aa2ed5f9c) - ## / 69
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (5dfb4f01184f) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (768b15f18e4d) - ## / 71
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (8a6bc054ad04) - ## / 71
Microsoft.VisualStudio.Threading.resources.dll (97f9edde2783) - ## / 70
Microsoft.VisualStudio.Validation.resources.dll (175a1847c46e) - ## / 70
Microsoft.CodeAnalysis.CSharp.Features.resources.dll (8f6c135552fc) - ## / 69
Microsoft.CodeAnalysis.CSharp.resources.dll (34fd0427feca) - ## / 68
Microsoft.CodeAnalysis.CSharp.Scripting.resources.dll (923fa9d838fb) - ## / 68
Microsoft.CodeAnalysis.CSharp.Workspaces.resources.dll (17b49a90fed6) - ## / 69
Microsoft.CodeAnalysis.Features.resources.dll (80644b567659) - ## / 69
Microsoft.CodeAnalysis.resources.dll (b6d42dcec9c0) - ## / 70
Microsoft.CodeAnalysis.Scripting.resources.dll (da6602ec3bed) - ## / 69
Microsoft.CodeAnalysis.Workspaces.resources.dll (3f288ce59b38) - ## / 69
Microsoft.TestPlatform.CommunicationUtilities.resources.dll (402ebe003d4b) - ## / 70
Microsoft.TestPlatform.CoreUtilities.resources.dll (96129603b0d3) - ## / 58
Microsoft.TestPlatform.VsTestConsole.TranslationLayer.resources.dll (8f63546cc4e3) - ## / 71
Microsoft.VisualStudio.TestPlatform.Common.resources.dll (a8490300cf45) - ## / 70
Microsoft.VisualStudio.TestPlatform.ObjectModel.resources.dll (796a6a0eada0) - ## / 70
Microsoft.VisualStudio.Threading.resources.dll (e53775a0e157) - ## / 70
Microsoft.VisualStudio.Validation.resources.dll (40c993e077a5) - ## / 69
e_sqlite3.dll (20ebfb13ea75) - ## / 67
e_sqlite3.dll (015de5cd1071) - ## / 69
e_sqlite3.dll (d25475871bc5) - ## / 69

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version History

Version	Downloads	Last Updated	Status
OmniSharp - Roslyn-based C# Language Server 1.39.11	205	Tuesday, January 2, 2024	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.10	201	Monday, October 23, 2023	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.9	344	Friday, October 13, 2023	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.8	43	Wednesday, October 11, 2023	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.7	205	Wednesday, July 19, 2023	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.6	303	Wednesday, March 15, 2023	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.5	59	Saturday, March 11, 2023	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.4	59	Tuesday, March 7, 2023	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.3	144	Sunday, January 22, 2023	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.2	265	Friday, October 28, 2022	Approved
OmniSharp - Roslyn-based C# Language Server 1.39.1	197	Sunday, July 31, 2022	Approved
OmniSharp - Roslyn-based C# Language Server 1.38.2	217	Tuesday, March 29, 2022	Approved
OmniSharp - Roslyn-based C# Language Server 1.38.1	127	Friday, February 18, 2022	Approved
OmniSharp - Roslyn-based C# Language Server 1.38.0	142	Thursday, December 16, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.17	141	Wednesday, November 3, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.16	123	Saturday, October 2, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.15	106	Tuesday, August 31, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.14	163	Wednesday, July 28, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.13	109	Saturday, July 17, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.12	104	Sunday, July 11, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.11	115	Saturday, June 19, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.10	134	Tuesday, May 25, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.9	104	Wednesday, May 19, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.8	288	Monday, March 29, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.7	122	Monday, March 8, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.6	108	Saturday, March 6, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.5	107	Thursday, March 4, 2021	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.4	198	Wednesday, November 25, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.3	242	Monday, October 19, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.2	154	Wednesday, October 14, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.1	188	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.37.0	190	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.36.1	177	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.36.0	169	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.35.4	159	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.35.3	181	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.35.2	154	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.35.1	143	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.35.0	211	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.15	167	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.14	122	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.13	133	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.12	134	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.11	180	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.10	138	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.9	153	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.8	138	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.7	141	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.6	158	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.5	147	Tuesday, September 29, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.4	136	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.3	126	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.2	161	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.1	140	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.34.0	144	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.33.0	162	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.20	131	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.19	172	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.18	144	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.17	124	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.16	144	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.15	145	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.14	153	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.13	145	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.12	140	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.11	171	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.10	136	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.9	146	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.8	139	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.7	116	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.6	138	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.5	118	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.4	111	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.3	139	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.2	121	Monday, September 28, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.1	137	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.32.0	121	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.31.1	99	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.31.0	110	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.30.1	126	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.30.0	165	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.29.1	147	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.29.0	116	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.29.0-beta1	144	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.28.0	122	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.27.2	115	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.27.1	142	Sunday, September 27, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.27.0	118	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.26.3	126	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.26.2	111	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.26.1	111	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.26.0	134	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.25.0	125	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.24.0	102	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.23.2	131	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.23.1	119	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.23.0	186	Thursday, September 10, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.22.0	120	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.21.0	97	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.20.0	178	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.19.0	107	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.18.1	85	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.18.0	96	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.17.0	105	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.16.1	124	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.16.0	134	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.15.0	107	Saturday, September 26, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.14.0	147	Monday, September 21, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.13.0	150	Monday, September 21, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.12.0	120	Monday, September 21, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.11.0	124	Monday, September 21, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.10.0	124	Monday, September 21, 2020	Approved
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta9	100	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta8	83	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta6	105	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta5	99	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta4	96	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta3	92	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta25	152	Monday, September 21, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta24	174	Monday, September 21, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta23	204	Monday, September 21, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta22	146	Monday, September 21, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta21	95	Monday, September 21, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta20	95	Monday, September 21, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta2	110	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta19	98	Monday, September 21, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta18	93	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta17	104	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta16	104	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta15	96	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta14	111	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta13	86	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta12	95	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta11	87	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta10	100	Sunday, September 20, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-beta1	98	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-alpha8	98	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-alpha7	101	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-alpha3	88	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-alpha2	89	Tuesday, September 15, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-alpha14	86	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-alpha13	91	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-alpha10	95	Saturday, September 19, 2020	Exempted
OmniSharp - Roslyn-based C# Language Server 1.9.0-alpha1	91	Monday, September 14, 2020	Exempted

Release Notes

Changes:

cc23e78fc072964728ff551c2d511ecb23972991 Merge pull request #2489 from dibarbet/1_39_3_release
ac9eab97550f7c723a818364924b445052326692 dont skip verification for changelog since tests are a required check
de3ec9e997a20ef9822d520146949f7c866bf8d1 Update changelog for 2023-01-03 release
9131f11a58c7205fb59b487fee0db10a428332fd Merge pull request #2486 from allisonchou/UpdateRoslynVersion
14fcf919534305f67f9ec2a4ffb12b72f7f7d50d Update PR number
9d798e83acaa4354d0381ba6c9bcd441ff58882b Update package versions
91af9c8e0775a1cc096010bd3c774d444adb4924 Cleanup
dacd86b7ef3c2faf8961d798d12b0bef692cf0e1 Cleanup
60c2ffdc66765d6805c927a221301587115d71cd Cleanup
4ab57e33b4c3d060b4fd1675aaf3dba30ea90b86 Skip test
<details><summary><b>See More</b></summary>
dfb1d4f94105c2606aaf4c52d346adc0d3bcd7fe Actually fix source generator issue
02ab44f04de445a7ae5685427fd2fce6d4b73095 Fix source generator issue
31f0e178b111f6b3b242821d1ee3acb4cb59d5f9 Initial version bump
098238f1527648719d7634963cb41e2817a2bfcd Merge pull request #2477 from OmniSharp/feature/dotnet-script
72b578f2c7840bd812085bbca074717dab2a5c90 added debugger attach task for the STDIO
ab1153935c95b7dfd532cec3b71c27e3d683fd41 updated to dotnet script 1.4.0
e760a6704a05fe7544b5b34da9eedf36e7bcc71b Merge pull request #2473 from dibarbet/register_languageserverlogger_once
bcbf5cf678a99714cbfce8df7081aaa378fdf9c9 Merge branch 'register_languageserverlogger_once' of https://github.com/dibarbet/omnisharp-roslyn into register_languageserverlogger_once
f6d258a499914de3cd720d2f526aba12020e34df formatting
3c7c9cc023a36bb837d14a79d7de42aafffaa38e Register the LanguageServerLogger only once
b05880541f0e091c46da39b9e1ddbb4984bfa074 Register the LanguageServerLogger only once
3ae5c8acd7ea3f03ab9e24c28280a320c573721a Merge pull request #2470 from OmniSharp/fix/azdo-feed-push-again
b3caa6775b944ee62a961734440ec83d6efa30d9 AzDo project name is Builds and feed is omnisharp
e18ee32cee801ba0af29d14eb6a569ce3fea7e32 Merge pull request #2469 from OmniSharp/fix/push-to-azdo
3cc17c2c2a65cac92499575509855c1cbb66e6b6 Fix push to Azure Artificats
908a001be38a32ab7a627c061fb9dc8e5ac3f81a Merge pull request #2468 from OmniSharp/feature/azure-artifacts
935ba115a978ed7669bae182cdbb4d89328ca808 Push NuGet packages to Azure Artifacts

This list of changes was auto generated.</details>

Dependencies

- nuget.commandline (≥ 5.7.0)
- dotnet4.7.2 (≥ 4.7.2.20180712)

Discussion for the OmniSharp - Roslyn-based C# Language Server Package

Ground Rules:

This discussion is only about OmniSharp - Roslyn-based C# Language Server and the OmniSharp - Roslyn-based C# Language Server 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 OmniSharp - Roslyn-based C# Language Server, 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

19,501

144

22 Jan 2023

OmniSharp - Roslyn-based C# Language Server

OmniSharp - Roslyn-based C# Language Server 1.39.3

Some Checks Are Exempted or Have Failed

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Introduction

Configuration

License

.NET Foundation

Changes:

Ground Rules: