1. On WP7+8 these values are found in the project level file : /Properties/WMAppManifest.xml and set by cordova-cli This is also the value that is shown to the end user when they choose to purchase an app from the store.
WP also has values for a project level version at: /Properties/AssemblyInfo.cs but these are not settable via cordova-cli The AssemblyInfo values are strict in that they need to be a full <*major version*>.<*minor version*>.<*build number*>.<*revision*> 2. n/a 3. The strictness of the value on different platforms makes this a no go, imo @purplecabbage risingj.com On Mon, Jan 27, 2014 at 12:31 PM, Shazron <[email protected]> wrote: > Commenting for iOS > > 1. n/a > 2. Essentially for our purposes CFBundleVersion == > CFBundleShortVersionString. CFBundleShortVersionString is usually a version > number for marketing purposes (say major.minor), and CFBundleVersion is the > "actual" internal build number, which may be of the longer form > (major.minor.patch.build) > 3. Sure > > > On Mon, Jan 27, 2014 at 11:52 AM, Mark Koudritsky <[email protected]> > wrote: > > > On Android and iOS there are two different values in project config for > > setting version numbers. > > > > We are currently using the "version" attribute form config.xml to set > > versionName on Android and CFBundleShortVersionString on iOS. The other > > version values are not set (that is versionCode on Android and > > CFBundleVersion on iOS are not set by cordova). > > > > 1. What about other platforms, which of them also have two different > places > > to set the version? > > > > 2. What's is typically used for CFBundleVersion on iOS? So far I've seen > it > > usually being set to the same value as CFBundleShortVersionString. Should > > cordova-cli just do that? > > > > 3. I want to add a single value in config.xml file that could be used to > > set the "other" versions for both Android and iOS. Does this sound > > reasonable? > > >
