Bug 3665 - Autoincrement support for iphone app bundle
Summary: Autoincrement support for iphone app bundle
Alias: None
Product: iOS
Classification: Xamarin
Component: MSBuild ()
Version: master
Hardware: Macintosh Mac OS
: Low enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Jeffrey Stedfast
: 33146 ()
Depends on:
Reported: 2012-02-28 07:05 UTC by John Hair
Modified: 2017-08-07 20:53 UTC (History)
8 users (show)

Is this bug a regression?: ---
Last known good build:

auto-inc.patch (7.49 KB, patch)
2016-11-30 21:43 UTC, Jeffrey Stedfast
auto-inc.patch (7.49 KB, patch)
2016-11-30 21:46 UTC, Jeffrey Stedfast
auto-inc.patch (7.49 KB, patch)
2016-11-30 21:48 UTC, Jeffrey Stedfast

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 3665 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description John Hair 2012-02-28 07:05:17 UTC
Feature request
Add support for autoincrement of bundle version numbers, e.g.

Setting bundle version to 1.2.* whould increment the 3rd number on every build.

Comment 1 Derek Foreman 2012-02-28 09:46:07 UTC
I agree. Going further,more options adds flexibility for different versioning types. This plugin for visual studio http://autobuildversion.codeplex.com/ and it is great. The only thing it lacks is providing an option for "quarter" increments. If this is added to MD allowing the flexibility like this plugin has would kill it!
Comment 2 Karl Heinz Brehme Arredondo 2012-03-02 22:04:46 UTC
Please make that run on until four parts as .NET manages it like [Major].[Minor].[Build].[Revision] optionally with * on Revision or Build.

But please do not count it as visual studio nosense way like NextVersion = Today.ToJulianDate() * RandomicNumber(), and do it simply ++NextVersion;


Comment 3 René Ruppert 2012-05-30 07:30:32 UTC
Just to keep this request alive: I second this! Would be cool to have this feature!
Comment 4 Jeffrey Stedfast 2015-10-06 16:25:37 UTC
*** Bug 33146 has been marked as a duplicate of this bug. ***
Comment 5 Paul Read 2015-10-07 03:37:38 UTC
This is a feature built into Borlands RADStudio and is VERY useful so please up the 'Importance' for this request. Thanks
Comment 6 Rolf Bjarne Kvinge [MSFT] 2016-02-11 14:54:20 UTC
Here is documentation and recommendations from Apple: https://developer.apple.com/library/ios/technotes/tn2420/_index.html

This is also interesting: https://developer.apple.com/library/ios/qa/qa1827/_index.html
Comment 7 Jeffrey Stedfast 2016-11-30 21:43:09 UTC
Created attachment 18721 [details]

I've attached a partially implemented patch. The problem is that I don't know of a good way of deciding whether or not the AutoIncrement target/task should run.

The problem is that every time you "Run" an app via XS, it calls the "Build" target which should not auto-increment version numbers in cases where nothing has changed but there's no good way to check if *nothing* has changed.
Comment 8 Jeffrey Stedfast 2016-11-30 21:46:56 UTC
Created attachment 18723 [details]

Oops, fixed typo.
Comment 9 Jeffrey Stedfast 2016-11-30 21:48:47 UTC
Created attachment 18724 [details]

Hah. Uploaded the wrong patch file :(