question

I'd say it depends on a number of things: - What's your experience with database querying? - Will there be many different types of data sources? - How familiar are you with .NET development? I wouldn't say there's a comparison between ADO.NET and ADO.NET Entity Framework. The Entity Framework uses ADO.NET objects, so I'd say it's an extension to ADO.NET I like control, and I want to query my data in a database server, therefore I've not even started exploring these high level database access frameworks. But I see why people who are less database-centric would like the Entity Framework. I can also see the point when there are many various data sources, but on the other hand one would still want to be familiar with the data source to be able to create the Entity Framework solution. Here's an easy-to-follow tutorial if you want to get started with the Entity Framework: - [**Part1**][1] - **[Part2][2]** - **[Part3][3]** But if you think your data will sit in SQL Server and you are comfortable with querying SQL Server, I'd recommend using "classic" ADO.NET command objects and/or data-adapters, datatables, datasets etc. [1]: http://www.c-sharpcorner.com/UploadFile/ankithakur/Getting_started_with_ADO_NET_Entity_Framework09302008085544AM/Getting_started_with_ADO_NET_Entity_Framework.aspx [2]: http://www.c-sharpcorner.com/UploadFile/ankithakur/ADOEF210032008083247AM/ADOEF2.aspx [3]: http://www.c-sharpcorner.com/UploadFile/ankithakur/ADOEF310102008095055AM/ADOEF3.aspx