There are different methods for data access for web applications Ado.net, EF, L2S.
Till the moment I'm still using ado, but now I have a new mession critical web app to be developed BUT it seems:
1. ADO is an old method.
2. L2S some people claimed that MS will drop it .. which I don't beleve, I think they will only stop releasing new features in it.
3. EF4 I didn't try it yet .. took a look at some code & I think its lengthy coding, a bit complicated, heard a lot about perfomance issues (but EF5 will be released soon & has a lot of enhancements which is encouraging)
I develop using ADO since it came to market. & I am, trying to compare to EF in terms of what I mentioned regarding (performance, staibality, etc.
Even if I spent some time (which I don't have) to try EF there are some problems you can't see in LAB project but it comes in production stages & real life time for the App.
I don't think I'll go with L2S, so my choices are ado or EF !
Hi,
Hope next time you can avoid using "!", which is impolite to other contributors;)
Now let's turn to your problem——
If you wanna speed up by retching out data contents, I'd suggest you choosing "the traditional DataReader including SqlDataReader……".
If you wanna make your programming like OOP，L2S or EF is more suitable for you; However, EF can be reguarded as the "Updated version of L2S, so you can still choose that".
But, according to your many situation, I'd like to say that:
1) If you only wanna do something selecting……, EF will be your choice.
2) For many parts of batchly Crud methods, ado.net (SqlCommand) will be your choice.
All in all, you can combine them together for futher usages.
Hope next time you can avoid using "!", which is impolite to other contributors;)
My apology.
Decker Dong - MSFT
But, according to your many situation, I'd like to say that:
1) If you only wanna do something selecting……, EF will be your choice.
2) For many parts of batchly Crud methods, ado.net (SqlCommand) will be your choice.
For this app its a sort of complicated project has many CRUD, user rights applied all over the app, has 4 major parts or areas for
(1-Admin Controls, 2-Company local users access, 3-Company international agents & resellers access, 4-Anonymous users access).
-Every one will have his/her login & according to the credentials will move in the app and act.
-Alot of CRUD, Online shoping cart, Reservation, Receipt printing, Online payment, etc.
Very similar to flights & ecomodation reservation systems.
Decker Dong - MSFT
All in all, you can combine them together for futher usages.
adscnet
Member
133 Points
44 Posts
Best Data Access Method in Web Apps
Dec 24, 2012 07:06 AM|LINK
Dear All,
There are different methods for data access for web applications Ado.net, EF, L2S.
Till the moment I'm still using ado, but now I have a new mession critical web app to be developed BUT it seems:
1. ADO is an old method.
2. L2S some people claimed that MS will drop it .. which I don't beleve, I think they will only stop releasing new features in it.
3. EF4 I didn't try it yet .. took a look at some code & I think its lengthy coding, a bit complicated, heard a lot about perfomance issues (but EF5 will be released soon & has a lot of enhancements which is encouraging)
check this link Entity Framework 5.0 Performance Improvements
I don't think I'll go with L2S, so my choices are ado or EF !
I need advice keeping in mind the following issues:
- Performance
- Stability
- Secuirty (safer aginist injections)
- Coding
ignatandrei
All-Star
135047 Points
21654 Posts
Moderator
MVP
Re: Best Data Access Method in Web Apps
Dec 24, 2012 07:45 AM|LINK
Very efficient for stored procs.
It's not the same?
IF you do not know ADO, then learn it. Afterwards, you can try EF.
adscnet
Member
133 Points
44 Posts
Re: Best Data Access Method in Web Apps
Dec 24, 2012 08:49 AM|LINK
Hi ignatandrei
I develop using ADO since it came to market. & I am, trying to compare to EF in terms of what I mentioned regarding (performance, staibality, etc.
Even if I spent some time (which I don't have) to try EF there are some problems you can't see in LAB project but it comes in production stages & real life time for the App.
ignatandrei
All-Star
135047 Points
21654 Posts
Moderator
MVP
Re: Best Data Access Method in Web Apps
Dec 24, 2012 09:29 AM|LINK
EF ( or any ORM) is for fastest development.
adscnet
Member
133 Points
44 Posts
Re: Best Data Access Method in Web Apps
Dec 24, 2012 12:56 PM|LINK
Thanks ignatandrei for your input
But I still need more detailed answers about Stability & Secuirty.
ignatandrei
All-Star
135047 Points
21654 Posts
Moderator
MVP
Re: Best Data Access Method in Web Apps
Dec 24, 2012 01:03 PM|LINK
this will be your implementation, not ADO or EF.
tdykstra
Contributor
4460 Points
624 Posts
Microsoft
Moderator
Re: Best Data Access Method in Web Apps
Dec 24, 2012 07:56 PM|LINK
See the ORM section in this MSDN page: http://msdn.microsoft.com/en-us/library/ms178359.aspx#orm
Decker Dong ...
All-Star
118619 Points
18779 Posts
Re: Best Data Access Method in Web Apps
Dec 25, 2012 12:14 AM|LINK
Hi,
Hope next time you can avoid using "!", which is impolite to other contributors;)
Now let's turn to your problem——
If you wanna speed up by retching out data contents, I'd suggest you choosing "the traditional DataReader including SqlDataReader……".
If you wanna make your programming like OOP，L2S or EF is more suitable for you; However, EF can be reguarded as the "Updated version of L2S, so you can still choose that".
But, according to your many situation, I'd like to say that:
1) If you only wanna do something selecting……, EF will be your choice.
2) For many parts of batchly Crud methods, ado.net (SqlCommand) will be your choice.
All in all, you can combine them together for futher usages.
adscnet
Member
133 Points
44 Posts
Re: Best Data Access Method in Web Apps
Dec 25, 2012 09:37 AM|LINK
Thanks tdykstra
Excellent link hilighted some good point.
adscnet
Member
133 Points
44 Posts
Re: Best Data Access Method in Web Apps
Dec 25, 2012 10:07 AM|LINK
My apology.
For this app its a sort of complicated project has many CRUD, user rights applied all over the app, has 4 major parts or areas for
(1-Admin Controls, 2-Company local users access, 3-Company international agents & resellers access, 4-Anonymous users access).
-Every one will have his/her login & according to the credentials will move in the app and act.
-Alot of CRUD, Online shoping cart, Reservation, Receipt printing, Online payment, etc.
Very similar to flights & ecomodation reservation systems.
I think a combination of ADO & EF will be used.