Reprint: "Xiachuntao email: [email protected] Blog:http://www.cnblogs.com/summerrain"
Long-term development of the. NET mis system, to the most or the database. Nothing to do, to pick up the flowers, the. NET database programming all the way to the experience to organize and share with friends. Take a small order management system, for example, in the form of practical code, plan to share the following content:
1. Non-hierarchical, using SQL statements to achieve data access;
2. Use DataTable to transmit data based on three-tier architecture;
3. Based on a three-tier architecture, use list to pass data;
4. Based on the three-tier architecture, using list to pass data, using stored procedures to achieve data access;
5. The database can be switched based on the Factory mode (for example, SQL and access);
6. Using Linqtosql to achieve data access (manual);
7. Using Linqtosql to achieve data access (automatic);
8. Using EntityFramework for data access (automatic)
9. Using EntityFramework to achieve data access (automatic pure Poco proxy);
10. Using EntityFramework to achieve data access (manual pure Poco agentless);
11. Using EntityFramework to achieve data access (manual pure Poco proxy);
12. Data input verification, and then look at the layering problem.
"Xiachuntao Email: [email protected] Blog:http://www.cnblogs.com/summerrain"
//===================================================================
Navigation:
//===================================================================
1 intro
2 sample System Overview and Design (1)
3. Using the ADO implementation (SQL statement) (1)
4. Using the ADO implementation (three-tier architecture-using table to pass data) (1)
5. Using the ADO implementation (three-tier architecture-using list to pass data) (1)
6. Using the ADO implementation (three-tier architecture-using list to pass data-based on stored procedures) (1)
7. Using the ADO implementation (Factory mode-implementing multi-Database Switchover) (1)
8. Using Linqtosql to implement
9. Using EF to implement
10. Implementing with EF (dividing the input validation layer)
11. Some thinking