I'm missing the feature like the BuildNumberPrefix for assembly versioning which can be used in different builds (CI, Daily, ...) to prevent version conflicts and to have common VersionSeed.xml file for all that builds.
I would like to have BuildNumberPrefix working also for nuget packages or to figure out different approach.
I'm not able to find the source code for the v2.0 release to add this support.
SemVer for nuget packages requires to have zero based version number resets, e.g. when you increment Minor part you have to reset Pach part to zero.
Ideally it would be nice if I could have one version definition for all builds and have automatic numbering support for CI builds, so that I have not to maintain two versions:
- one for release version (Manual Build definition) - e.g. 1.2.0 (which is manually incremented)
- another for CI version (CI Build definition) - e.g. 1.2.0.B (which is manually incremented)
As you can see, with the current version of tfsnugetter and tfsversioning activities I'm not able to achieve single maintenance of version for the same package from different builds.