Maybe making too much out of this.
We can probably use:
13.0 build 113.0 build 2...13.0
And later13.0.1 build 113.0.1 build 2...13.0.1
no?
Version Strings
MordachaiOur version scheme and yours are almost compatible, but not quite (at least, at first blush that seems to be the case).
We use: [major.minor][.service-pack][.beta]
So for a released version, we might use 13.0
But for the betas leading up to release, we might have the sequence 13.0.0.1, 13.0.0.2, ...
And after initial release, when we release a service-pack, we might have the internal sequence 13.0.1.1, 13.0.1.2, .... leading up to releasing 13.0.1 (13.0 Service Pack 1).
Any thoughts on how we might adapt your software to our version scheme? There's zero percent chance we'll change our version scheme - way too many other pieces of software already rely upon it, and it has worked very well for us thus far.
Actually, if you replace "build" with "beta", then everything will work fine. For instance:
13.0.1 beta 113.0.1 beta 2...13.0.1
When you add versions to wyBuild, they automatically reorder into the order they will be interpreted by wyUpdate:
[attachment=0]version.order.png[/attachment]
Tell me if this helps.
And what of additional text.
For example, we release foreign language builds separately:
13.013.0 Japanese13.0 Chinese Traditional13.0 Chinese Simplified13.0 Spanish...
So would we have:
13.0 Japanese beta 1or13.0 beta 1 Japanese...
If your other languages have separate binaries, then simply create a new project for each language.
D'oh! Of course. Thanks