Reading things like,
http://developer.apple.com/qa/qa2004/qa1373.html
which discuss CFBundleIdentifier, the example always given for what it
should look like is of the form:
com.mycompany.MyApp
My question is, as different versions, of the same application, are
released, it is a good
It's really up to you and the kinds of changes that you expect to happen
between each version. Having a single ID allows preferences to be mixed and
matched if different versions of the product are used, but if you want to
support the simultaneous use of last year's version and this year's
On Jul 11, 2008, at 9:40 AM, Eric Gorr wrote:
My question is, as different versions, of the same application, are
released, it is a good idea or recommended that the
CFBundleIdentifier reflect the version of the application as well.
For example, one might have:
com.mycompany.MyApp2007
On Fri, Jul 11, 2008 at 9:40 AM, Eric Gorr [EMAIL PROTECTED] wrote:
Reading things like,
http://developer.apple.com/qa/qa2004/qa1373.html
which discuss CFBundleIdentifier, the example always given for what it
should look like is of the form:
com.mycompany.MyApp
My question is, as
On Jul 11, 2008, at 1:01 PM, Douglas Davidson wrote:
Remember that preferences and the like are keyed off of the bundle
identifier, so changing it would give you some work to do in
migrating older settings.
I am focused on your phrase 'and the like'.
Other then preferences, what else is
On Jul 11, 2008, at 11:54 AM, Eric Gorr wrote:
Other then preferences, what else is keyed off of the bundle
identifier?
So, just to be clear, would you generally consider it to be the case
that a unique bundle identifier is intended to identify a unique
application and not different
On Jul 11, 2008, at 12:58 PM, Gary L. Wade wrote:
It's really up to you and the kinds of changes that you expect to
happen between each version. Having a single ID allows preferences
to be mixed and matched if different versions of the product are
used, but if you want to support the
