My .NET Portfolio showing the different concepts I implemented

1. Arthur del Prado
artsdp@yahoo.com
(845) 821-1140

2.  .NET Framework Project
 Library Phase I Project (Windows Application)
 Library Phase II Project (ADO.NET and T-SQL)
 Library Phase III Projects (Web Application)

3.  Objective
◦ The purpose of this project is to exhibit my knowledge in applying various concepts
of the .NET Framework using C#.
◦ In this project, I was tasked to build parts of the business tier for a retail company.
The goal was to create and test two assemblies, Foundations and AppTypes.
 Summary
◦ The first assembly is a class library project called Foundation. It contains various
interfaces and base classes used in the project.
◦ The second assembly is also a class library project called AppTypes. It contains
various entity, collection, and exception classes used by various business processes.
◦ This project focused mainly on the various aspects of .NET object-oriented
programming with C#. Highlights of this project include the use of inheritance, C#
properties, abstract classes and methods, interfaces, method overloading and
overriding, attributes, enums, custom exceptions, delegates, collections and
generics.

6.  Objective
◦ In this project, I was tasked to create a Windows Forms-based front-
end application that will provide a librarian with a visual interface
through which he or she may perform the desired functions.
 Summary
◦ This project focused on Windows Forms programming and was built
with an N-tiered approach. The Business Layer and the Data Access
Layer were provided so I had to build the application to work with
what was given.
◦ 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
 Provide adequate error handling
 Produce a user interface that is intuitive, requiring minimal training for
users while minimizing resource utilization

12.  Objective
◦ In this project, I was tasked to design and develop my own Business and
Data Access tiers to replace the assemblies provided for these from the
Library Phase I Project.
 Summary
◦ This project focused on the use of database-programming techniques
that provide maximum flexibility and control while minimizing resource
utilization
◦ I created all Library functions (Add Member, Check In, Check Out, etc.)
as T-SQL Stored Procedures which were called by the Data Access Layer
methods
◦ I created the Business Layer to call the Data Access Layer methods. The
front-end interface used the Business Layer to facilitate the database
transactions.
◦ I used ADO.NET to communicate with the database. Furthermore, for
this project, I elected to use Strongly-typed DataSets which meant that
I ran into less coding errors and was able to finish the project faster.
◦ I also used LINQ To SQL for finding overdue books in the database.

14. continued

17.  Objective
◦ In this project, I was tasked to create a web application that
supports all the functionality required for Phase I and Phase II of the
Library Project.
 Summary
◦ This project mainly focused on ASP.NET programming and
maintained the N-tiered approach taken during the previous phases.
◦ The Business and Data Access Layers created from Phase II are used
and adapted.
◦ Some ASP.NET highlights in this project include the use of master
pages and themes, css, forms-based authorization and
authentication, ASP.NET membership and role management,
databindings, preservation of data with ViewState and Session
objects, partial page postbacks with Ajax, input validation using
validation controls, exception handling and custom error pages.

18.  Additional Requirements
◦ 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. Librarian must be able to choose whether or not to renew
the card. Members cannot check out books if the card is expired.
◦ 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).
This upgrade takes place automatically and the librarian must be
notified that the upgrade has taken place.
◦ Overdue books, shown in any display, must be highlighted
◦ The librarian must be able to enter a new book into the database.
◦ On the Member information page, the check in and check out
functionality must only cause partial postback.
◦ Use of hyperlinks to navigate between pages.