ProGet Documentation

Packages in ProGet

Hosting all your important assets as packages allows the enterprise to uphold regulate and standardize how assets are used. Giving you the ability to ensure that the right components are what’s actually being deployed to production. Packages are essentially one of two things: a Library or an Application. Libraries and Applications are composed of important files and assets that are used throughout the software development lifecycle. They can be an external, third party packages from a repository such as NuGet or an in-house, internal package.


Hosting your in-house packages in ProGet provides the enterprise with the ability to uphold compliance standards and solidify cohesion among all teams. Using ProGet to manage dependencies across the enterprise helps ensure that everyone is working from the correct versions of shared libraries.

ProGet give you the ability to vet your external third party packages to ensure and uphold enterprise security standards; providing the same level of quality as in-house packages. Through connectors, ProGet allows you to connect to outside repositories and cache packages locally. Caching locally in ProGet makes frequently used packages available quickly and even during outages of the external repository.

Package Promotion

As of ProGet 4.4, you are now able to promote packages to specific feeds. This is particularly useful when distinguishing which packages are fit for production. Check out our Promote packages with ProGet video for a quick look at how to do this.

As you can see below, you can also easily promote packages from the Development feed to the Live feed.

Promoted Package

Because security and privileges can be scoped at the feed level, you can ensure only individuals with the proper roles are able to access the Live production-ready feed. Giving your organization another level of control and consistency, in the software development process.

Deployment Records

Deployment records provide additional information about the deployments that utilize your packages. They provide details about where the packages are deployed, who deployed them, and gives you the ability to view, in BuildMaster, additional information.

Deployment Records

This built-in feature provides useful records needed for auditing, and compliance requirements.