Bending NuGet to Your Will by Manipulating the AppData Cache

NuGet decides which versions of dependencies to pull in based a combination of the way dependencies are specified in the dependent packages and the packages that are available on your feeds.  NuGet drills down pulling all of a components direct dependencies and its indirect dependencies based on the nspec specifications of each pulled in component. This lets you pull in some  OSS component and then its dependencies down to bottom level which might be something like a Microsoft component. NuGet compares the versions specifications when resolving those to NuGet packages on a feed. Here are some example version specifications for the Microsoft MVC

  • "4.0.20505.0"  MVC 4.0 RC or later
  • "[4.0.20505.0]" MVC 4.0 RC only
  • "[4.0.20505.0, 4.1] MVC 4.0 RC through any version of 4.1
  • "[4.0.20505.0, 4.0.20710.0) MVC 4.0 RC and all up to but not including MVC 4 RTM
You can run into problem when new versions of dependencies appear on feeds and dependencies are inccorectly bounded.

Example Problem

Lets say you have library based on MVC 4.0 RC, 4.0.20505.0, that hasn't isn't yet ready to update to MVC 4.0 RTM, 4.0.20710,0.  Now Microsoft updates MVC on the official NuGet feed from 4.0.20505.0 to 4.0.20710.0 making it available to you.  You then update a consuming application pull in this version of your library.

If the library specified its' NuGet dependency as "4.0.20505.0" then NuGet will automatically delete 4.0.20505.0 from your packages folder and add version 4.0.20710.  You now have a component that was built against RC (4.0.20505) but which is sitting in an app with MVC RTM (4.0.20710.) One option is to fix any compile errors resulting from inclusion of 4.0.20710.0 In large projects that is complicated because you might have a multi-solution rol lup to get everything updated and builds rolled up. "Web Component C" in the diagram would require 3 consuming updates to carry this 3rd party version upgrade to the top.



The right way to fix this is to fix this problem is to change the libraries description of it's MVC dependency from "[4.0.20505.0]" which says ignore any other versions on the feed.  This works well also but in a big project may mean that you have to update dozens of nuspec definitions to include the square brackets. This can get complicated in a larger project. I saw one 50 solution project where it took almost a week to roll this type of upgrade from bottom to top.  

Microsoft themselves have some trouble with this.  The MVC/WebApi 4.0.20505.0 RC NuGet internal dependencies are specified as "4.0.20505" for things like Razor, etc.  This means you can potentially end up in a mixed RC / RTM environment where the later dependencies were all pulled in as RTM even though the previous dependencies were RC.

Hacking NuGet to "Use the Cache, Luke"

Another option is to hack NuGet to provide the versions you want.

NuGet caches all of its downloaded dependencies in %HOME%\AppData\NuGet\cache.  This includes any packages that have been updated by the NuGet Package Manager. We make use of this and the fact that this cache looks like a "local" feed.  
  1. Check the cache to see if your packages are already ther.  If not , create a temporary project, and use the package manager to create dependencies that are automatically downloaded to your NuGet cache directory.  Sometimes you need seeding and sometimes you don't.
  2. Turn off your normal feeds including NuGet.org and any local/hosted feeds.. 
  3. Create a new NuGet feed pointing a the AppData\NuGet\cache.  
  4. Purge any conflicting NuGet packages from the cache directory.
  5. Run the NuGet package manager. It will assume that your cache contains the correct versions and it will install from the cache instead of from the actual feeds.

NuGet Package Restore

I'm not sure how this works with Package Restore.  You may be able to use a similar technique

Comments

Post a Comment

Popular posts from this blog

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more