Typed Dataset, Linq-To-Sql, Entity Framework, MVC are new to me. What among them to start with on new project

Question

I am from a world where people dont want to come out of there comfort zone to learn new technologies and I am among them as an exception looking for something different. Since I am not getting any learning opportunities and hence decided to create an application. Here are my details.

I have to create a new web application for personnel use. A very very small one containing 20-30 tables with annual record intake of 10000 rows in each table. I will be applying all the constraints at database that are possible to keep data consistent.

At preset i am aware of only Untyped dataset and have good hands on it. But while creating this application which is more of data, validation checks driven and no or less focus given on UI what technology should I use: traditional one, typed dataset or Linq to Sql or Entity Framework.

I would be going with frequent database schema change(addition or removal of columns in a table). Less frequent table breakup and so.

This application will have a sole purpose of learning a new technology rather than going with traditional one that I am using for a long.

I have been studying about typed datasets, Linq to Sql. I have used little bit of Linq on Datasets and so have idea about linq. Read efficient enough about typed dataset to start with and 0% idea about entity framework but doesn't matters I can go for it also.

I can learn new technology doesn't matter how much time it will take.

What do you suggest what should I go for that can be scalable, will open the doors of huge source of learning that I can use in industry as well

Answer 1

From the list of technologies you supply, it has to be Entity Framework. Here is why.

Typed / Untyped datasets just wholly bind your application to the database. You need more disconnection between persistence and logic than these give. I haven't seen datasets for a very long time.

Linq to Sql is reasonable, but Microsoft rolled their Linq to Sql team into the Entity Framework team. They are really pushing Entity Framework, which has benefits over and above Linq to Sql. One is that you can create your domain model in code and then auto-gen your database from it. This is a skill that is becoming reasonably valuable as more and more companies see the benefit of this type of technology. This is definitely a re-usable skill for you to learn.

Answer 2

Sounds as if you are after technologies in the area of the database access layer, the domain layer and object-relational mapping.

If true, that I'd suggest to look at NHibernate and fluent-nhibernate. In working with these you will have typed results (List<T> instead of DataSet) but also the opportunity to work with LINQ.