Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

33,995

Downloads of v 24.0.27:

18

Last Update:

26 Feb 2025

Package Maintainer(s):

Software Author(s):

  • Inedo

Tags:

proget inedohub

proget (Install)

  • 1
  • 2
  • 3

24.0.27 | Updated: 26 Feb 2025

Downloads:

33,995

Downloads of v 24.0.27:

18

Software Author(s):

  • Inedo

proget (Install) 24.0.27

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

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Installation takes too long on test environment. (Known to work in local test environment)

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install proget (Install), run the following command from the command line or from PowerShell:

>

To upgrade proget (Install), run the following command from the command line or from PowerShell:

>

To uninstall proget (Install), run the following command from the command line or from PowerShell:

>

Deployment Method:

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

  • 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

3. Copy Your Script

choco upgrade proget -y --source="'INTERNAL REPO URL'" [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 proget -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install proget
  win_chocolatey:
    name: proget
    version: '24.0.27'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'proget' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '24.0.27'
end

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


cChocoPackageInstaller proget
{
    Name     = "proget"
    Version  = "24.0.27"
    Source   = "INTERNAL REPO URL"
}

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


package { 'proget':
  ensure   => '24.0.27',
  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 by moderator flcdrg on 03 May 2025.

Description

ProGet is a Self-hosted, Cross-Platform Package and Container Repository that keeps all your packages and Docker containers in one place, allowing you to scan for vulnerabilities and control who can access different feeds.

ProGet supports just about all of the third-party package types you'll need (e.g. NuGet, npm, PowerShell, and Chocolatey) and comes in a powerful free version that you can upgrade when ready.

## Package Parameters

- /TargetDirectory - The root install directory for ProGet. Defaults to $PathCombine($SpecialWindowsPath(ProgramFiles), ProductName).
- /ConnectionString - Connection string used to create and initialize the database schema. Defaults to 'Data Source=Localhost\SQLEXPRESS;Trusted_Connection=true;'
- /DbName - Name of the SQL database to use or create. This overrides any Initial Catalog specified in the connection string. Defaults to ProGet.
- /WebServerPrefixes - Specifies the URL and port used by the integrated web server. Defaults to http://*:8624.
- /ExtensionsPath - Specifies the directory where user-installed ProGet extensions will be stored. Defaults to $PathCombine($SpecialWindowsPath(CommonApplicationData), ProductName, Extensions).
- /ExtensionsTempPath - Specifies the directory where extensions are unpacked and loaded from. Defaults to $PathCombine($SpecialWindowsPath(CommonApplicationData), ProductName, ExtensionsTemp).
- /LicenseKey - If specified, this license key will be written to the database instance on installation. There is no default value.
- /UserAccount - The name of the user account which will be used to run ProGet's services. It may be LocalSystem, NetworkService, or any domain/local account. Defaults to NetworkService.
- /UserPassword - The password of the user account specified with the UserAccount parameter. Ignored if using LocalSystem or NetworkService. There is no default value.
- /IsUpgrade - When true, services will not be created. Defaults to false.


tools\chocolateybeforemodify.ps1
# This runs before upgrade or uninstall.
# Use this file to do things like stop services prior to upgrade or uninstall.
# NOTE: It is an anti-pattern to call chocolateyUninstall.ps1 from here. If you
#  need to uninstall an MSI prior to upgrade, put the functionality in this
#  file without calling the uninstall script. Make it idempotent in the
#  uninstall script so that it doesn't fail when it is already uninstalled.
# NOTE: For upgrades - like the uninstall script, this script always runs from
#  the currently installed version, not from the new upgraded package version.

$env:IsUpgrade = $true
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop' # stop on all errors

Import-Module $env:chocolateyInstall/helpers/ChocolateyProfile.psm1
Update-SessionEnvironment #pickup new PATH items from dependency installs

if ((Get-Command hub.exe -CommandType Application)) {
    Write-Host "Inedo Hub found, we can continue"
}
else {
    throw "Inedo Hub not found, installation cannot continue"
}

$version = '24.0.27'
#Set the location of hub.exe for command execution
$fileLocation = (Get-Command hub.exe).source

#List parameters to be passed to hub.exe during install
$PackageParameters = Get-PackageParameters
$installArgs = @("install", "ProGet:$($version)")

if (-not $PackageParameters['ConnectionString']) {
    $PackageParameters['ConnectionString'] = 'Data Source=Localhost\SQLEXPRESS;Trusted_Connection=true;'
}

if(-not $PackageParameters['WebServerPrefixes']){
    $WebServerPrefixes = '8624'
}

switch ($PackageParameters.Keys) {
    "ConnectionString" {
        $installArgs += "--ConnectionString=`"$($PackageParameters['ConnectionString'])`""
    }
    
    "TargetDirectory" {
        # The root install directory for the Inedo product.
        $installArgs += "--TargetDirectory=$($PackageParameters['TargetDirectory'])"
        # Default value: $PathCombine($SpecialWindowsPath(ProgramFiles), ProductName)
    }

    "DbName" {
        # Name of the SQL database to use or create. This overrides any Initial Catalog specified in the connection string.
        $installArgs += "--DbName=$($PackageParameters['DbName'])"
        # default value: ProductName
    }

    "WebServerPrefixes" {
        # Specifies the URL which is used by the integrated web server. Ignored if UseIntegratedWebServer is not true.
        $WebServerPrefixes = $PackageParameters["WebServerPrefixes"] 
  
        $installArgs += "--WebServerPrefixes=$($WebServerPrefixes)"
        # default value: http://*:8624/
    }

    "ExtensionsPath" {
        # Specifies the directory where user-installed product extensions will be stored.
        $installArgs += "--ExtensionsPath=$($PackageParameters['ExtensionsPath'])"
        # default value: $PathCombine($SpecialWindowsPath(CommonApplicationData), ProductName, Extensions)
    }

    "ExtensionsTempPath" {
        # Specifies the directory where extensions are unpacked and loaded from.
        $installArgs += "--ExtensionsTempPath=$($PackageParameters['ExtensionsTempPath'])"
        # default value: $PathCombine($SpecialWindowsPath(CommonApplicationData), ProductName, ExtensionsTemp)
    }
    
    "LicenseKey" {
        # If specified, this license key will be written to the database instance on installation.
        $installArgs += "--LicenseKey=$($PackageParameters['LicenseKey'])"
        # no default value
    }

    "UserAccount" {
        # The name of the user account which will be used to run your Inedo product's services and/or IIS AppPool. It may be LocalSystem, NetworkService, or any domain/local account.
        $installArgs += "--UserAccount=$($PackageParameters['UserAccount'])"
        # default value: NetworkService
    }

    "UserPassword" {
        # The password of the user account specified with the UserAccount argument. Ignored if using LocalSystem or NetworkService.
        $installArgs += "--UserPassword=$($PackageParameters['UserPassword'])"
        # no default value
    }
    
}

if ($env:IsUpgrade -or $PackageParameters['IsUpgrade']) {
    $installArgs += "--IsUpgrade=true"
}

$Statements = $installArgs -Join " "
Start-ChocolateyProcessAsAdmin -Statements $Statements -ExeToRun $fileLocation

#Notify user of ProGet website once everything has been created and configured

$WebsiteRoot = 'http://localhost:{0}' -f $WebServerPrefixes

Write-Host "ProGet package installed successfully. ProGet web interface can be found at $WebsiteRoot."
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop' # stop on all errors

#Set the location of hub.exe for command execution
$fileLocation = (Get-Command hub.exe).source

$installArgs = @("uninstall","ProGet")

$Statements = $installArgs -Join " "

Start-ChocolateyProcessAsAdmin -Statements $Statements -ExeToRun $fileLocation
tools\proget-icon.svg
 

Log in or click on link to see number of positives.

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.

Add to Builder Version Downloads Last Updated Status

Discussion for the proget (Install) Package

Ground Rules:

  • This discussion is only about proget (Install) and the proget (Install) 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 proget (Install), 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.
comments powered by Disqus