Matched assembly versioning to actual versioning

[kf6kjg]

Helps keep things understandable.

[appurist]

This will break the auto-build numbering.

[kf6kjg]

Hence it has the change for appveyor's automatic building built in. Unless you mean some other system?

…

On Sun, Aug 5, 2018 at 3:31 PM appurist ***@***.***> wrote: This will break the auto-build numbering. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#465 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABGoaONwKsaHQMfBwnN78h6l0-82IPhbks5uN3IogaJpZM4Vvifh> .

[appurist]

Last time I checked, the automatic build numbers in Visual Studio only support the * in the third place. The * in the fourth place was something like seconds since midnight, which would mean non-incrementing build numbers. This is why the AssemblyVersion did not include the leading "0." and restoring in will cause the build number to appear to be somewhat random.