Create and Publish Universal Packages
  • 17 Feb 2022
  • 1 Minute to read
  • Dark
    Light
  • PDF

Create and Publish Universal Packages

  • Dark
    Light
  • PDF

You can use BuildMaster to package your application in a Universal Package and deploy it to a feed in ProGet. Universal Packages are essentially a zip files, but they contains a manifest file that describes the contents.

The main advantage to using Universal Packages instead of BuildMaster-hosted artifacts are to have self-contained application or component packages that may be distributed and deployed without BuildMaster.

About Universal Package Format

The Universal Package format (UPack) is very simple, and can be used to package applications and components built with any technology: .NET web applications, NodeJS applications, Windows services, plug-ins for your applications, system configuration scripts, and so on.

How to Create a Universal Package

The Create-Package will build a universal package file. For example, to create a package file (ProfitCalc-$ReleaseNumber.upack) in the working directory from the contents of the working directory, you can just do this:

ProGet::Create-Package
(
    Name: ProfitCalc,
    Version: $ReleaseNumber
);

Push a Universal Package to a ProGet Feed

After creating a package source, you can simply use the ProGet::Push-Package operation to push the package to that feed. For example, to push a newly-created package, you can do this:

ProGet::Push-Package
(
    PackageSource: ApplicationPackages,
    FilePath: ProfitCalc-$ReleaseNumber.upack
);

Was this article helpful?