![]() For the Student entity type you'll create a repository interface and a repository class. In this tutorial you'll implement a repository class for each entity type. Implementing these patterns can help insulate your application from changes in the data store and can facilitate automated unit testing or test-driven development (TDD). The repository and unit of work patterns are intended to create an abstraction layer between the data access layer and the business logic layer of an application. ![]() As in the previous tutorial, in this one you'll change the way your code works with pages you already created rather than creating new pages. In this tutorial you'll see some ways to use the repository and unit of work patterns for CRUD operations. In the previous tutorial you used inheritance to reduce redundant code in the Student and Instructor entity classes. For some common errors and how to solve them, see Errors and Workarounds. You can generally find the solution to the problem by comparing your code to the completed code. ![]() ![]() If you run into a problem you can't resolve, download the completed chapter and try to reproduce your problem. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |