I learned last week that you can rename the project NuGet feed.
I updated SourceLink and then I worked with Don Syme to update FSharp and FSharp.Compiler.Service. The convention we settled on is to rename the feeds with the AppVeyor account name and project name separated by a dash.
- https://ci.appveyor.com/nuget/ctaggart-SourceLink
- https://ci.appveyor.com/nuget/fsgit-fsharp
- https://ci.appveyor.com/nuget/fsgit-FSharp-Compiler-Service
Their corresponding build history pages can be viewed to determine the desired version.
As documented in the readme, to use one of those prerelease builds, you would add to paket.dependencies:
- source https://ci.appveyor.com/nuget/fsgit-fsharp-compiler-service
- nuget FSharp.Compiler.Service 1.3.1.1-b414
Then run 'paket update'.
To install using NuGet command line, something like this will work:
Versioning
Prerelease builds are builds that come before a release build. In all of these projects, I've setup the build scripts to create release builds based on a valid Git tag. The prerelease identifiers are the AppVeyor build number with a 'b' prefix since NuGet requires a letter. This seems to work well. I've moved away from using date and time in the prerelease identifier on CI builds. I only use date and time on local builds now if at all.
For FSharp, I coded this logic in PowerShell in appveyor.ps1. The version here is only for the prerelease builds. A release build is made from a Git tag and the version in this file is not used.
For FSharp.Compiler.Service, I updated the FAKE build.fsx. The prerelease version is loaded from the release notes.
Summary
A big thank you to AppVeyor for providing this service. I use AppVeyor for commercial and for open source projects and it rocks! I'm hoping more open source projects will be able to benefit by following my lead here.