asp.net - Design pattern for a simple CRUD data driven application -


I would like to know the best practice for designing a simple CRUD application, in which to update some tables, Along with maintaining static data for an application) The easiest way to drag a data grid / gridview, it must be tied on a dataset and using the data adapter for CRUD operation. But if this application needs to be scalable, then ask to add any additional UI / business logic in the future, so what is a design pattern that can help with this? Am I using the object data source control and instead should bind the business object? Or is there a better way to do this? Should I build a fully layered application or should it be overwriting for this requirement? Any example for UI design will be useful. Thank you.

If you are really looking for a quick and easy approach, then you can use dynamic data like a Linq2SQL or At the top of the EF4 backend - hardly any code is necessary.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -