You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the wildcard versioning (for ex 1.0.0.*), is there a way to make it so the wildcard is generated sequentially?
That is, it would be 1.0.0.0 on the first build, then 1.0.0.1, then 1.0.0.2 ...
The text was updated successfully, but these errors were encountered:
You should use ADO build variables for this. The Counters expression works great for this. Create one that stores a counter against the non-sub number e.g. 1.0.0 and you will then simply need to pass e.g. 1.0.0.$(IncrementableNumber) into the AssemblyInfoTask.
Wildcard versioning is presumably to support specific MSBuild behaviour.
When using the wildcard versioning (for ex 1.0.0.*), is there a way to make it so the wildcard is generated sequentially?
That is, it would be 1.0.0.0 on the first build, then 1.0.0.1, then 1.0.0.2 ...
The text was updated successfully, but these errors were encountered: