ProGet Documentation

Asset Directory in ProGet

Starting in ProGet 4.8, an Asset Directory is a uniquely-named Root Directory in ProGet that contains sub-directories and files. Similar to feeds, Asset Directories can have their own specific configuration including scoped security privileges.

Asset Directories

Asset Directories in ProGet allow for arbitrary file storage with easy access via a web browser and a RESTful API. Universal Packages in ProGet are great for storing self-contained versioned artifacts with medtadata and dependencies, but not everything fits this package format. Sometimes a file is simply just a file, and this is where Asset Directories come in.

An Asset Directory is a container for any number of subdirectories and files. These files are stored using the same extensible mechanism used by ProGet's feeds, which allows for the use of default disk/network share storage or S3 and Azure blob storage.

For Example:

An installer may be used by a configuration script for setting up a workstation. The installer is already a self-contained package, so packaging it further would be redundant; it just needs to be downloaded and executed. It could simply be stored in an Asset Directory, and referenced using a well-known URL.

Alternatively, Asset Directories could be used to host a simple internal static web site, or sharing a picture with your organization without emailing or uploading it to a cloud service. You could even configure a Retention Policy to automatically clean up old or unused files.

Asset Directories provide the versatility of a file share, and the added benefit of all the security and stability features ProGet offers, such as scoped privileges, retention policies, and automatic failover.


Files, similar to packages, can be added to a Directory in a number of ways. You can:

  • Upload a single file using a browser
  • Import multiple files at once contained in a .zip or a .tar.gz
  • Upload files using the API

Multiple or large (1GB+) files may be uploaded by dragging & dropping files using the multiple files option. Note however that this functionality is only available for feeds whose underlying package store is is backed by a directory, and will not be available for asset directories backed by Amazon S3, Azure, etc.

Configuring Asset Directories

Asset Directories are now top-level concepts in ProGet, along with Feeds and Packages. The Assets link at the top of the page will take you to the Asset Directory overview, which will display every Directory in ProGet. From here, you can create a new directory, modify an existing directory, delete a directory, or browse a directory.

When creating a new Directory, the only required field is its name. Like Feeds, Asset Directories must be uniquely named, and should be names that can be easily represented in a URL (in other words, avoid characters like /, :, or spaces). As soon as you have named the new Directory, you can start uploading files to it.

Internally, Asset Directories are represented as Feeds, which means the Asset Directory name must also not be the same as any Feed name. This also means that Feed-scoped privileges can also be applied to Asset Directories.

Retention policies for Asset Directories work just like they do for Package Feeds, except that any rules relating to version numbers are not applicable since Asset Directories store simple unversioned files.

Accessing Files

You can browse the contents of an Asset Directory from your browser. The directory is displayed as a standard hierarchy of folders and files; individual files can be selected and downloaded or viewed. Files in an Asset Directory can also be accessed as if they are hosted on a web server by navigating to the REST API URL for the file (see API documentation).