Force no cache for single package source in nuget.config

[bpaczkowski]

We're using package version wildcards for some of our internal libraries to make it easier to update them, but as it stands now, they wont get updated to the newest version (matching the wildcard) without the use of the no-cache operator, which also applies it to nuget.org package source. Ideally it would be if no-cache was applied to all wildcarded packages, but if I could apply it to a single package source (our internal one), this would suffice.

[heng-liu]

Similar to #3116

[MV10]

When I'm creating or modifying a library, I will temporarily output the package to a local folder which is defined as a package source. Being able to turn off caching for that source would be a huge time-saver. Currently after rebuilding the library, I have to unload the solution that uses the package, manually delete the cached version, then re-open the solution to restore the package.

I was going to post a suggestion that local package sources shouldn't be cached at all (which is still probably a good idea), but more generally, having the option to disable caching per-source would be pretty useful.

I don't think that 3116 is related.

[MV10]

This does seem to be related: #6579

[MrAntix]

could we have a no-cache flag in the nuget.config?

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
     <add key="local" value="../nuget" no-cache />
  </packageSources>
</configuration>