I am wondering what the purpose is of the *.plist files? Do I need to check them into the source control, or are they generated automatically?
Asked
Active
Viewed 183 times
-2
-
Which plist file? What's it called? – Wain Apr 29 '13 at 14:50
-
xcschememanagement.pinfo – Adam Lee Apr 29 '13 at 15:03
-
Try this: http://stackoverflow.com/questions/6770472/what-do-all-the-changes-to-xuserstate-and-xcscheme-files-represent – Wain Apr 29 '13 at 15:06
2 Answers
3
Purpose:
- A great way to store dictionary data that does not change during runtime is in a .plist file. If you want to organize some data hierarchically you can store it in .plist file
A property list is a representation of a hierarchy of objects that can be stored in the file system and reconstituted later. Property lists give applications a lightweight and portable way to store small amounts of data. They are hierarchies of data made from specific types of objects—they are, in effect, an object graph. Property lists are easy to create programmatically and are even easier to serialize into a representation that is persistent. Applications can later read the static representation back into memory and recreate the original hierarchy of objects. Both Cocoa Foundation and Core Foundation have APIs related to property list serialization and deserialization.
Do I need to check it into the source control?
- Yes you need to check it into the source control.
Ankur
- 5,086
- 19
- 37
- 62
0
If it is the info.plist file it is where the bundle ID, version number, and loads of other info about the app is stored. If that info isn't important to you then it doesn't need to be in your repo, but the smart money is on keeping it under version control.
Apple has info about the what the file is for and what the various keys are if you Google info.plist you will get all the information you could possibly need about it.
theMikeSwan
- 4,739
- 2
- 31
- 44