Objective C vs VB.net

[teguh123]

At first I was very disappointed when I learn Objective C.

What the hell. For every member object I have to declare the variable 3 times.

One in the declaration. One for property declaration. One to tell the compiler to synthesize all the function. Another one to release all those members from memory.

Then I learn about Core Data. I generate diagram, poof the classes are made from me and a lot of things are done behind the screen of that visible classes.

Basically Core Data in Objective C represents some form of relational databases. Of course those databases can have relationship, including many to many relationship. The additional detail of having a third table for many to many relationship is already done.

Then, there is indexed property so we can search faster. That's also done.

Does VB.net has something like that? What's the equivalent with VB.net.

[jmcilhinney]

I've never used Objective C or Core Data but it sounds like you would get a similar result by generating a model using the Entity Framework, which is built into VS and the .NET Framework. It's not the only option though. You can also have the IDE generate a typed DataSet or a LINQ to SQL model. There are also third-party options, like LLBLGen, NHibernate and others.