Open KSib opened 7 years ago
Hi
Any part of a version value is treated as a numerical value and therefore the prefixed 0 is automatically removed. A potential future enhancement could be to take number of input digits into consideration.
Do you have a specific requirement?
I don't. Management likes it though ;)
Understood:)
I will keep the feature in mind for possible future development.
it seems to be simple to solve.
This is a requirement for my org. We use $(DayOfYear) in our build number and our file version and they need to be the same for us because we display File Version on the site. This issue causes the two values to be different for the first 99 days of the year.
TFS defaults to 3 digits with a leading 0 for $(DayOfWeek).
If I have a version number such as "03" in one of the version number fields, it parses it to "3"
1.2.03.4 becomes 1.2.3.4, for example.