Using CI Builds

The packages table on the home page lists the currently available builds. The column titled "Latest CI" indicates the version of the most recent build that was pushed automatically as a result of new code being pushed to GitHub. These automated builds are currently sent to (that link will require you to log into your account, which is free if you don't already have one).

In order to consume packages from this feed, you need to create or update the NuGet.Config file for your project. Here is an example:

<?xml version="1.0" encoding="utf-8"?>
    <clear />
    <add key="" value="" protocolVersion="3" />
    <add key="" value="" protocolVersion="3" />

This NuGet.Config file sets two feed sources: the official source from NuGet, and the feed from (Note that while you need an account to view the website, you do not need an account to restore packages, so using this NuGet.Config should be relatively friction free.) We recommend that you place the NuGet.Config file into the top level folder of your source repository so that it will be used for all package operations in your project.

Note that the order of the package sources matters: the first listed source ( in this case) has the highest priority. That means if the package is available from with the version you requested, it will be sourced from there, even if the same version is available on a later package feed.

Copyright © .NET Foundation. Contributions welcomed at