NuGet Package Pipeline?

[dazinator]

Pipelines for processing typescript, js, css etc are all very well.

How about a pipeline for processing NuGet packages?

The idea would be, you could drop a NuGet package in a directory (or update an existing NuGet package), and the pipeline would process the NuGet package with options for:

1. Where to install / extract the package contents too.
2. Registering custom handling of package content.

For example, a CMS system could use this pipeline to detect NuGet packages placed in a directory (could be an InMemory directory or Physical directory). When this occurs, the CMS could control via the pipeline options, where the NuGet package will be installed too (Physical or InMemory).

The NuGet package pipeline will take care of:

1. Resolving the package dependencies - i.e if the package foo depends on the package bar, then bar will also be downloaded and processed by the pipeline. (This implies configuration of nuget feeds)
2. Extracting / Installing the files in the package to the install location.

In terms of extracting / installing the files, the pipeline options would allow you to specify which file types should be exposed as StaticFiles.

For example, if a NuGet package contains 'js and 'css' files and also .dll files, then you could configure the pipeline such that the js and css files will be installed to one location, and made visible as static files (i.e visible to the webroot IFileProvider) but the dll files will be installed to another location and not exposed via the webroot file provider.