Different version string format

Topics: General
Jan 29, 2015 at 9:28 AM
Edited Feb 3, 2015 at 2:47 PM
My project does not use version strings like "1.2.3". I don't have such thing as major, minor, build and revision numbers. I use a continuous integration scheme and only the master branch gets published. I generate version numbers with a tool that converts Git commit times into a compact string of 4 letters and digits. No dot in it. Unfortunately, NuGet rejects those version specifications.

So what can I do? I don't have version numbers the way NuGet expects them, but I do have newer versions and updates and packages need to be compared. A simple lexical string comparison is fine. Is there an override option to force NuGet to use my version id? Or can't I use NuGet to publish my library?