AssemblyVersion: any chance of specifying alternate env variable? about cols-agent-tasks HOT 3 CLOSED

hey @mrbelk - not sure what your ask is. Do you want to specify your own version numbers instead of taking it from the build?

If so, that kind of defeats the purpose of this task. This task is meant to match the assembly version to the build number. If you don't like the 1.0.0.r format, then I'd suggest that you create a custom build number and then use the version assemblies task right after doing whatever it is that you need to do. That way you get a scheme that you're happy with and the version assemblies still works as-is.

Let me know if you were thinking of something else entirely :-)

from cols-agent-tasks.

I can see how my original post could be confusing. I love the idea of using the Build number in the versioning of assemblies.

I was more noting that there could be a flaw in the "versionCode" usage of this task because when any part of the BuildNumber changes, the $(rev) property will reset back to one; breaking the "monotonically increasing" requirement of the Android versionCode. So if you change the build number from 1.0.0$(rev:.r) to say 1.1.0$(rev:.r), then your versionCode will drop back to 1.

I actually wound up writing my own powershell task to synthezise a version code based on the current date.

from cols-agent-tasks.

Ah I see what you're getting at. Unfortunately no (clean) way around that.

from cols-agent-tasks.