Pros and cons of using EntityDataSource vs ObjectDataSource in Entity Framework?

Basically EntityDataSource is build to support Entity Framework entities for features like sorting, filtering, inserting, deleting etc... If you use the ObjectDataSource you will have to do this on your own.

One huge disadvantage of EDS controls that I just discovered the hard way, is that they want to update the database immediately and each such control has its own EF object context, its own database connection, and even after I wrote a handler to share a context, share a db connection and turn off all immediate inserting, updating and deleting, so that I could do the final SaveChanges() at the end when the user hit the final "submit" button, the EDS control uses EF in such a fashion that it still fetches deleted records. And does not fetch inserted records. SO I am going to convert where I use EDS controls to use ODS controls instead and thus allow me to interject another object model in between my radgird views and EF in order to have the grid show inserted records and not show deleted records and be able to allow the user the delayed commit back to the database.

As far as I can tell, there is no other way to have web grids use EDS controls and to delay this final commit as well as show inserted records or not show deleted records. I would love to be proven wrong on these facts...Dave.

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.