Serverless redirection to save us from ugly URLs

I’m a fan of CI-independent serverless nuget feeds: you can push packages from arbitrary systems to a single feed that is highly available and requires no maintenance. It can also be made public access (which Azure Artifacts/VSTS still doesn’t allow).

There is one minor issue, though: the URL isn’t all that memorable or particularly short. Its format is https://[ACCOUNT][CONTAINER]/index.json. It’s still better than a VSTS packaging feed: https://[ACCOUNT][NAME]/nuget/v3/index.json, but wouldn’t it be nice to have something even shorter, like http://[account] After all, it’s just a trivial HTTP redirect we need. Serverless to the rescue!

NOTE: why even have that index.json at the end? Turns out, that is what tells NuGet to consider the feed as a v3 feed :(

The things we’ll need for this are:

  1. A nice short domain
  2. An Azure DNS zone and records for the domain
  3. An Azure Functions app to perform the redirects

I head over, typed “nuget” and found for ~$3. Then I went to Azure DNS and created a new DNS zone for it.

create DNS zone

NOTE: best way to find stuff in the Azure Portal is to just type in the search box

search DNS in azure portal

Then back to namecheap to configure the DNS for the domain.

After creating the functions app, I created a redirect function which is simple enough:

using System.Net;
using System.Web;

public static HttpResponseMessage Run(HttpRequestMessage req, TraceWriter log) 
    log.Info($"Redirecting {req}");
    var account = req.Headers.GetValues("DISGUISED-HOST").First().Replace("", "");
    var response = req.CreateResponse(HttpStatusCode.MovedPermanently);
    response.Headers.Location = new Uri($"https://{account}");

    return response;

Over in the function app’s Platform features tab, we can configure the custom domain for it:

configure custom domain

I added * since I want the redirection be usable by anyone creating their custom serverless nuget feeds.

Back at the DNS zone, I added a recordset for * to CNAME it to the azure function ( in my case) host name:

add recordset

Finally, we need to make azure function accessible from * The function URL is currently In order to make it accessible via a different URL, we just need to create a Proxy with the desired route:

add proxy

With that in place, anyone using serverless Azure nuget feeds can use a nice sort url like The only requisite is that your storage container name must be nuget, and the storage account becomes the subdomain of

All my upcoming OSS stuff from CI will be available from that feed from now on :)

[Read More]

How To Install and Cleanup Visual Studio 2017 Instances

Visual Studio 2017 allows multiple side by side installations, which makes experimenting with various versions and extensions a breeze. Here's how you quickly and easily install and optionally cleanup so-called 'instances' that may have become broken for whatever reason.

[Read More]

Test and Switch: testable yet high performance cross-platform libraries

How to write cross-platform libraries without resorting to abstractions that slow down an app at run-time while still being able to unit test logic that consumes those libraries. Just like bait & switch gave us the trick to leverage platform-specific code in cross-platform libraries, test & switch gives us the trick to author them in a testable and still high performance way.

[Read More]

Serverless custom NuGet feeds

Pretty much all CI systems offer nuget feed hosting. But why setup those when you can have a CI-independent, static serverless feed virtually for free and almost no effort?

[Read More]

Building like a Pro: A Primer

In this second installment of the series, I showcase the basic core concepts in MSBuild that will get you up and running quickly, with concrete examples to try out the various constructs.

[Read More]