Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 06, 2012 01:29 AM by Decker Dong - MSFT
May 04, 2012 02:54 PM|LINK
I'm currently working on a huge public interfacing web site...we are in the process of deciding the Data Access Technology...I personally have a feeling that LINQ 2 SQL & Entity Framework are for smaller or less mission-critical applications where performance
is not a major criteria...
I'm suggesting the client to use Data Access Application Block with Stored Procedures...with a combination of "Custom Attribute / System.Reflection " to map the physical model to the conceptual model...
May 04, 2012 03:08 PM|LINK
May 06, 2012 01:29 AM|LINK
In my mind，I think you can use LINQ-TO-SQL or EF+ObjectDataSource（because it directly supports three-tier or N-tier）easily；And to speed up the speed of execution，I think you can use StoredProcdure+LINQ/EF。
For Linq+ObjectDataSource，you can refer：http://weblogs.asp.net/zeeshanhirani/archive/2008/05/05/using-linq-to-sql-with-objectdatasource-control.aspx
And for complicated datasources or variable structures of DataTables，you can use general ADO.NET（SqlDataAdapter+DataTable/DataSet）to deal with the problem。
For more about ObjectDataSource+DataAdapter：http://help.infragistics.com/Help/NetAdvantage/ASPNET/2010.1/CLR3.5/html/WebGrid_Using_Custom_Paging_with_ObjectDataSource.html