Skip to main content

Extend NuGet Server to store packages on Azure Blob Storage

By
Continuing the last post about Azure Web Apps and Data Disk size limit let's assume that you want to host inside a Web App a NuGet Server. The server would require more storage than you have available on the current tier that you use and upgrading the tier would be too expensive.

The good part with NuGet is that we are talking about an open-source project that can be modified and extended depending on our needs and requirements. The current NuGet implementation allows us to store packages on disk or to fetch them from external data sources as long as they are available over HTTP. Basically, they are allowing us to have a remote repository 

An interesting idea would be to extend NuGet to allow us to store package content inside Azure Blob Storage and not on the disk. This would involve the capability to fetch the payload of packages from Blob storage directly, without having to store them on a local disk.
Taking into account the current implementation and how NuGet libraries are structured internally, I think that it can be achieved easily with a minimal effort. After a short review (15 minutes) of NuGet libraries, I identified a few interfaces and classes that are relevant to do such a thing. 

The most important classes/interfaces that we need to be aware of are:
  1. IServerPackageRepository: Provides access to the file system, in this case, we need to rewrite it to support Blob storage
  2. IPackageService & PackageService: Package download capabilities 
  3. IPackage: Defines a package with all the supported functionality
Beside this, you might be interested to take a look on:
1. Core interfaces used to download and access package payload
  • IPackageDownloader
  • IPackageContentReader
  • IAsyncPackageContentReader
2. Core implementation to read and extract packages
  • PackageReaderBase
  • PackageFolderReader
  • PackageExtractor
3. Mechanisms used to access package content
  • NuGet.Protocol.LocalRepository
  • NuGet.Protocol.RemoteRepositories
  • NuGet.Protocol.PackagesFolder
  • NuGet.Protocol.HttpSource
4. Core factory to create and register specific repository providers
  • FactoryExtensionsV3
Once we implemented the NuGet extension for Azure Storage, we would need to rebind the NuGet 'kernel' to use our own implementations of Package Repository and custom Package implementation. 

The idea is not new, there were already other people that tried it, but because of lack of time they were not able to finish it. If you want to get some inspiration or to give a hand, please visit the following GitHub repository - https://github.com/Assassyn/Nuget.Server.AzureStorage. Even if it was not updated in the last few years, it is still a good starting point. 

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

By
In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more