Modify NuGet Build for Different Feeds
Hmmm... I tried to reply on this thread, but it didn't post:
https://help.appveyor.com/discussions/questions/43569-modify-nuget-package-version-before-build
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!
Keyboard shortcuts
Generic
| ? | 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
1 Posted by Mike-EEE on 08 Nov, 2019 04:35 PM
FWIW, additional context and our GitHub issue around this can be found here:
https://github.com/ExtendedXmlSerializer/ExtendedXmlSerializer/issues/259
2 Posted by Mike-EEE on 12 Nov, 2019 02:53 PM
You can disregard this question. We completely overhauled the versioning and made use of the csproj patching:
https://www.appveyor.com/docs/build-configuration/#net-core-csproj-files-patching
3 Posted by Mike-EEE on 12 Nov, 2019 02:55 PM
<deleted>
Support Staff 4 Posted by Feodor Fitsner on 12 Nov, 2019 07:23 PM
OK, thanks for the update!