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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
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

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more