Ado.net MVC3 way of ADO.NET using?

Number 1 is classical, 'pure ADO. Net Number 2 is ADO. Net Entity Framework also called Entity Framework for short, which adds an Object/Relational Mapper (ORM) on top of classical ADO.Net.

Number 1 is classical, 'pure' ADO.Net. Number 2 is ADO. Net Entity Framework, also called Entity Framework for short, which adds an Object/Relational Mapper (ORM) on top of classical ADO.Net.

Either way can work for working with data in ASP. NET MVC. The first one is using ADO.NET straight up, using sql commands and what not.

The second one looks like it's possibly using Entity Framework or Linq to SQL. If you're working an existing data access layer, you're probably going to be doing things the first way. If you're lucky enough to start a brand new project, you would probably want to take advantage of the much cleaner way using Entity Framework of Linq to SQL.

Once again, both are acceptable way of working with data in MVC projects. Good luck, and hope this helps you.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.