Modify NuGet Build for Different Feeds

Mike-E's Avatar


08 Nov, 2019 04:33 PM

Hmmm... I tried to reply on this thread, but it didn't post:

So posting new discussion here.

We're encountering an issue around this space, too.

We have two feeds, our preview feed is on myget and always has the "next" version, e.g. 2.1.25. Nuget has the currently released version, e.g. 2.1.24.

The problem we are encountering is on the myget feed. We of course send a new version with each commit. However, users have complained that the new package will not download due to caching issues, and that they already have a downloaded version from the preview feed, if that makes sense.

So, in the case of a myget v2.1.25, we commit a fix and the user downloads it. They report another issue, and we commit v2.1.25 again. They attempt to get latest but they do not because nuget reports that they already have v2.1.25 installed.

Ideally, we would like to have v2.1.25.{buildnumber} on myget and v2.1.24 on NuGet.

Thank you for any assistance you can provide!

  1. 1 Posted by Mike-E on 08 Nov, 2019 04:35 PM

    Mike-E's Avatar

    FWIW, additional context and our GitHub issue around this can be found here:

  2. 2 Posted by Mike-E on 12 Nov, 2019 02:53 PM

    Mike-E's Avatar

    You can disregard this question. We completely overhauled the versioning and made use of the csproj patching:

  3. 3 Posted by Mike-E on 12 Nov, 2019 02:55 PM

    Mike-E's Avatar


  4. Support Staff 4 Posted by Feodor Fitsner on 12 Nov, 2019 07:23 PM

    Feodor Fitsner's Avatar

    OK, thanks for the update!

  5. Mike-E closed this discussion on 15 Nov, 2019 03:34 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac