When is NuGetVersionV3 coming?

[memark]

Browsing through the discussions and the code, I have noticed that the NuGetVersion property is currently pointing at the NuGetVersionV2, returning the same thing. Also there is this comment // TODO When NuGet 3 is released: public string NuGetVersionV3 { get { return ??; } }
https://github.com/GitTools/GitVersion/blob/416ed5ad41a2699bc1dc9fd0731aae1909e1cfdd/src/GitVersionCore/SemanticVersionFormatValues.cs

NuGet 3.5 does support SemVer2 (well, most of it), and has been out for a while. So I'm wondering when this feature NuGetVersionV3 might be coming to GitVersion?

For the moment I've resorted to using the SemVer property, BUT it can generate version strings longer than 20 characters, which are not supported even by NuGet 3.5.

OTOH NuGet 4.0.0-rc4 does accept really long strings, solving the problem for now. But that should be the NuGetVersionV4, right? :)

[pascalberger]

What do you expect in a NuGetVersionV3 variable compared to the already existing variables?

[memark]

I expect support for dot-notation in the prerelease part, allowing proper sorting of e.g. 1.0.0-beta.10 and 1.0.0-beta.2, eliminating the need for any padding.

While you were typing, it appears, I also edited my original post, adding some more information.

[memark]

@pascalberger Does this answer your question?

[JakeGinnivan]

Happy to get a PR to add this :)

[asbjornu]

Doesn't the FullSemVer property cover this use case? Either way closing due to inactivity.

[teneko]

Yes it does @asbjornu, but where can you set or overwrite the use of the synonym for NuGetVersion (reference) when building NuGet packages? Unfortunately you can not find any documentation for it. But luckily I found the solution by reading the sources in the NuGet package of GitVersionTask: In the file build/Directory.Build..props you find the PropertyVariable UseFullSemVerForNuGet, which you can set/overwrite (not sure the Directory.Build.props order) in your own Directory.Build.props.

[asbjornu]

Good question and find, @teroneko. We can probably turn UseFullSemVerForNuGet to true by default now, I guess. We can probably add NuGetVersionV3 as an alias for FullSemVer as well, if needed. Thoughts, @arturcic?