This document summarizes Jonathan Terry's .NET course work for a library management system created over three phases. Phase I involved building a Windows forms application to add members, check in/out books. Phase II added business and data access tiers using an n-tier architecture. Phase III transformed the application into a web application using ASP.NET, adding functionality like highlighting overdue books and converting juvenile to adult members aged 18+. The code examples show implementing validation, error handling, and interacting with the database using stored procedures across the different tiers and phases of the project.

1. Jonathan Terry’s .Net Course work For the SetFocus .Net Masters Program

2. Project: Library Phase I – Windows Front-End Application Scenario A database has been created to support the principal functions of a lending library’s day-to-day operations: adding new members (adult and juvenile) and checking books in and out. An assembly has been created that contains classes and interfaces that provide access to the database for these functions. Objective Create a Windows Forms-based front-end application that will provide a librarian with a visual interface through which they may perform the desired function. Requirements • Design and develop a front end application that satisfies the four basic functionalities: Add Adult, Add Juvenile, Check In a book, Check Out a book. • Develop code that is easily maintainable. • Provide validation for all required fields (see details below). • Provide adequate error handling. • Produce a user interface that is intuitive, requiring minimal training for users while minimizing resource utilization.

3. Library Phase I This is form is used to add an adult to the Library’s database. Edits will be performed on the fields before the data is committed.

4. Library Phase I This is part of the code behind for the adding of an adult member. Try Catch blocks are used to insure proper error handling.

5. Library Phase I This is the CheckIn page, users must enter a isbn and copy number then select the get item info button. Details of the book are display after the input data has been verified.

6. Library Phase I This is part of the code behind for the CheckInItem form, the validating event is used to edit the controls on the form that are used for input ( Input controls on forms are edited using the validating event).

7. Project: Library Phase II – Business and Data Access Tiers Scenario Based on the information that librarians presented, the project database designer decided to implement the entities from the scenario presented in Phase 1 of the Library Project in three groups of tables: tables that contain member information; tables that contain item (book) information; and tables that contain loan information. Objective Implement an n-tier architecture that utilizes the.Net functionality. Requirements • Design the Business and Data Access tiers • Develop code that is easily maintainable. • Provide adequate error handling. • Use database-programming techniques that provide maximum programming flexibility and control while minimizing resource utilization.

8. Library Phase II Sample code from the Business tier. The Business tier invokes methods on the Data Access tier and contains regular expressions used to meet edit requirements.

9. Library Phase II Sample code of the Data Access Layer. From here the SQL DB is accessed using stored procedures.

10. Library Phase II This is a sample of a stored procedure used in this phase of the Library project.

11. Library Phase II A bit more of the stored procedure

12. Library Phase II To facilitate the passing of data between the tiers a project was created that holds all the classes used to work within the Library.

13. Project: Library Phase III – Web Application Scenario Create a Web solution to the Library project. Objectives Use Asp.Net to transform the Library project into a web application Requirements Create a web application that supports all the functionality required for Phase I and II of the Library project. When displaying an adult’s information, the application should detect if the card is expired and give the librarian a chance to renew the card. When dealing with juveniles, the application should detect if the juvenile is 18 years old or older and convert the member to an adult (row deleted in the juvenile table, row added to the adult table). Overdue books, shown in any display, must be highlighted. The librarian must be able to enter a new book into the database. If the ISBN already exists in the database, all that is needed is to add a record for a new copy number. On the Member Information page the design must be altered to use two AJAX controls, the Update Panel control and the Update Progress control. The librarian should be able to select a row and click a check in button to check the item back into the library.

14. Library Phase III Add adult page of phase 3. Moving to web cause new way of editing to be done. Validation controls are now used.

15. Library Phase III Part of the code behind for the ‘Click’ event of the button to add an Adult as a member of the library.

16. Library Phase III This shows an item being added to the Library. The error handling prevents an existing item from being added again.

17. Library Phase III Part of the stored procedure that handles adding a new item to the library. If the item already exists a error is raised and set back to the code.

18. Library Phase III This page displays information about a member. Overdue books are highlighted in the gridview control.

19. Library Phase III This code shows how the DueDate column is highlighted in red using the DataRowBound event of the gridview control.

20. Library Phase III When the select link is clicked that row is highlighted and buttons appear that lets the user checkIn an item automatically.

21. Library Phase III When getting member information juveniles should be converted to adults automatically if they are older than 18.

22. Library Phase III Code from data access tier for converting a juvenile to an adult.

23. Library Phase III Part of the stored procedure to convert a juvenile to an adult.

24. Presentation Concluded Jonathan Terry’s .Net Course Work for the SetFocus Masters Program