After completing the first PluralSight course and a working App, the first thing I noticed is that my app does not persist data. One of the main goals of this app is to help you track, over time, how many carbs you eat. You can enter data into the app, interact with that data, but once you close the app it all goes away. Thats not terrible useful, so I needed to find a way to store the data that is entered.
I know a little about iOS, and knew that CoreData was a framework that iOS has to store data within an app, so I searched on PluralSight for CoreData and found one course, Introduction to iOS for .NET Developers, by Jon Flanders. I thought, "Hey! That is me, awesome." First major difference in this course over others I have watched, he has broken it up into almost all 1 minute segments. That sort of makes sense here because he is mostly just relating .NET to iOS development, and assumes that once you know how to translate what you want to do in .NET to iOS that you can either figure out what question to ask next or figure it out on your own. Given that, I expect that I will return to this course more when I don't know what to ask Google. Disappointingly, this course did not go into CoreData in a significant way, so I wasn't able to get what I wanted at this time out of this course.
I went back and searched again using the term Core Data instead of CoreData. I found an entire course devoted to Core Data, Core Data Fundamentals, by Brice Wilson. Hopefully this course will provide the information I need to get started with saving data entered into my app. During the introduction, Brice talks about another course of his for consuming web services and storing smaller, more simple data in an app. It sounds like that might be a very good course to come back to if I need to have a web service feeding me data. He also talked about the demo app he will build in this course, which sounds like a great way for me to learn what I was looking for.
At first glance, even though he says it is not, the closest comparison I can make for CoreData is Entity Framework Code-First. Similar to EF, an Entity relates to a table and Attributes relate to a Column in that table. You can define relationships between Entities very much like a Database Foreign Key Constraint, including the ability to cascade delete.
Getting started creating an Entity is really very easy. You add a File and choose the Core Data -> Data Model file type. Then you can start adding Entities using the plus button. Adding Attributes is also as easy as a plus button. Looking at the properties of an attribute I see some things you would expect like data type and whether or not the Attribute is optional. I also found something I was not expecting, validation fields. Core Data has built into it the ability to define minimums and maximums. I will be curious to see how these work out, it can get tiresome always needing to do sanity checks in .NET because none of the objects you are working with are smart enough to know that they can't be below zero or before the year 1/1/1900, EF on a SQL 2005 Server, I am looking at you.
I know a little about iOS, and knew that CoreData was a framework that iOS has to store data within an app, so I searched on PluralSight for CoreData and found one course, Introduction to iOS for .NET Developers, by Jon Flanders. I thought, "Hey! That is me, awesome." First major difference in this course over others I have watched, he has broken it up into almost all 1 minute segments. That sort of makes sense here because he is mostly just relating .NET to iOS development, and assumes that once you know how to translate what you want to do in .NET to iOS that you can either figure out what question to ask next or figure it out on your own. Given that, I expect that I will return to this course more when I don't know what to ask Google. Disappointingly, this course did not go into CoreData in a significant way, so I wasn't able to get what I wanted at this time out of this course.
I went back and searched again using the term Core Data instead of CoreData. I found an entire course devoted to Core Data, Core Data Fundamentals, by Brice Wilson. Hopefully this course will provide the information I need to get started with saving data entered into my app. During the introduction, Brice talks about another course of his for consuming web services and storing smaller, more simple data in an app. It sounds like that might be a very good course to come back to if I need to have a web service feeding me data. He also talked about the demo app he will build in this course, which sounds like a great way for me to learn what I was looking for.
At first glance, even though he says it is not, the closest comparison I can make for CoreData is Entity Framework Code-First. Similar to EF, an Entity relates to a table and Attributes relate to a Column in that table. You can define relationships between Entities very much like a Database Foreign Key Constraint, including the ability to cascade delete.
Getting started creating an Entity is really very easy. You add a File and choose the Core Data -> Data Model file type. Then you can start adding Entities using the plus button. Adding Attributes is also as easy as a plus button. Looking at the properties of an attribute I see some things you would expect like data type and whether or not the Attribute is optional. I also found something I was not expecting, validation fields. Core Data has built into it the ability to define minimums and maximums. I will be curious to see how these work out, it can get tiresome always needing to do sanity checks in .NET because none of the objects you are working with are smart enough to know that they can't be below zero or before the year 1/1/1900, EF on a SQL 2005 Server, I am looking at you.
Comments
Post a Comment