SqlDataSource vs EntityDataSource

Gudni · March 18th, 2014, 02:28 PM

Hi, there.

Currently, I am building a site, relying heavily on the Beginning ASP.NET 4 book.
As far as I can see, one can choose to work with either SqlDataSources or EntityDataSources. Both are used in the book and, if I am correct, which way you go is mainly a matter of choice. Everytning you can do with a SqlDataSource can be done with a EntityDataSource and vice versa. Am I right?

In chapter 13 of the book, SqlDataSources are used in connection with DataGridView and DetailsView. Then, in chapter 14, EntityDataSources are used for GridView, Repeater an ListView controls. Is there a particular reason for this choice of data source type other than introducing the reader to LINQ and the ADO.NET Entity Framework?

Imar · March 18th, 2014, 03:06 PM

Both have their pros and their cons. The SqlDataSource is easy to set up, but harder to maintain. If you rename tables or columns, you won't notice your SQL is broken until you run the page.
The EntityDataSource is, at first, harder to set up and configure, but then provides better (but not perfect) type checking.

However, the EntitDataSource control is now considered obsolete. Instead, you're advised to use Model Binding: http://blogs.msdn.com/b/webdev/archi...web-forms.aspx

This requires a more recent version of .NET / Visual Studio than this book targets but if you happen to use VS 2012 or later, this is the way forward.

Cheers,

Imar

Gudni · March 19th, 2014, 04:18 AM

Thank you, Imar.
Being a relatively inexperienced web developer, I am learning many new things at the same time. But I will certainly have a look at Model Binding. The site I mention in my post, is done with VS 2010, but I have recently installed VS 2013 and will inspect MB in due time.