Matthew Swanger .NET Portfolio


Published on

Dedicated and resolute C# Software Developer/Programmer with experience using object oriented design techniques and programming languages, including Microsoft .NET Technologies.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Matthew Swanger .NET Portfolio

  1. 1. .NET PORTFOLIO<br />Matthew Swanger<br /><br />(720) 319-8354<br />
  2. 2. Table of Contents<br />.NET Framework Project 3<br />Library Phase 1 Project 6<br />Library Phase 2 Project 11<br />Library Phase 3 Project 16<br />
  3. 3. .NET Framework Project<br />Objective<br />For this project, the objective was to create the business tier for a retail company. This was achieved by creating and testing two assemblies: Foundation and AppTypes.<br />Summary<br />The AppTypes assembly is a Class library project that contains many entity, collection and exception classes that are used to facilitate most of the business processes.<br />The Foundation assembly is a Class library project that contains the base classes and interfaces used in the project. <br />This project focused predominantly on the various aspects of .NET Object-oriented programming with C#. Some of the highlights of this project include the use of C# properties, abstract classes and methods, inheritance, method overloading and overriding, interfaces, attributes, enums, custom exceptions, generics, delegates and collections.<br />
  4. 4. Foundation Assembly<br />.NET Framework Project<br />
  5. 5. AppTypes Assembly<br />.NET Framework Project<br />
  6. 6. Library Phase 1 Project<br />Objective<br />For this project, the objective was to create a Windows Forms-based application that would serve as the user interface tier to the supplied library book management database. This visual interface is responsible for providing a librarian with access to the day-to-day actions preformed in a library.<br />Summary<br />The focus of this project was on Windows Forms programming and it was built with an N-tiered approach in mind. The Business layer, The Data Access layer and the database where provided, so I was responsible for creating an effective front-end application to work with what was given. <br />Requirements<br />Design and develop a front end application that satisfies the four basic functionalities: Add Adult, Add Juvenile, Check-In a book and Check-Out a book.<br />Develop code that is easily maintainable.<br />Provide validation for all required fields.<br />Provide adequate error handling.<br />Provide a user interface that is intuitive, requiring minimal training for users while minimizing resource utilization.<br />
  7. 7. Add Adult and Juvenile Member Forms<br />Library Phase 1 Project<br />
  8. 8. Check In and Check Out Forms<br />Library Phase 1 Project<br />
  9. 9. Add Adult Member Code<br />Library Phase 1 Project<br />
  10. 10. Check In Book Code<br />Library Phase 1 Project<br />
  11. 11. Library Phase 2 Project<br />Objective<br />For this project, the objective was to write my own Business and Data Access layers replacing the layers that were provided in Phase 1 while continuing to support the Windows Forms-based front-end application I created in Phase 1.<br />Summary<br />The focus of this project was predominantly on ADO.NET and T-SQL programming while keeping to the N-tiered structure used in Phase 1.<br />I created T-SQL Stored Procedures for all the Library Functions (Check In, Check Out, Add Member, etc…) which were then called by the Data Access Layer methods. The Business Layer served to enforce the business logic and also to act as the middleman between the user interface and the Data Access Layer.<br />I used ADO.NET to communicate with the database. Also, I chose to use Strongly Typed DataSets for this project to reduce the amount of coding required and also the likelihood of errors.<br />
  12. 12. Library Phase 2 Project<br />Requirements<br />Design the Business and Data Access tiers.<br />Develop code that is easily maintainable.<br />Provide adequate error handling.<br />Use database-programming techniques that provide maximum programming flexibility and control while minimizing resource utilization.<br />
  13. 13. Check In Book Stored Procedure<br />Library Phase 2 Project<br />
  14. 14. Check In Book Stored Procedure (Continued)<br />Library Phase 2 Project<br />
  15. 15. Check In Book Data Access Layer<br />Library Phase 2 Project<br />
  16. 16. Library Phase 3 Project<br />Objective<br />For this project, the objective was to write a web application that supports all the functionality required in Phase 1 and 2 of the Library project.<br />Summary<br />The focus of this project centered around ASP.NET programming and keeping the N-tiered approach used in Phase 1 and Phase 2.<br />The web application created for this project is meant to serve as an alternative user interface, while leaving the Phase 1 Windows Forms-based application unchanged and fully functional. This project will make use of the Business and Data Access layers I created in Phase 2.<br />Highlights of this ASP.NET project include the use of master pages, membership and role management, forms-based authorization and authentication, data preservation using ViewState and Session State objects, partial page postbacks with Ajax, databindings, exception handling and input validation with validator controls.<br />
  17. 17. Library Phase 3 Project<br />Additional Requirements<br />When displaying an adult’s membership information, the application should detect if the membership is expired and provide the librarian an option to renew the membership. Also, members with expired memberships cannot check out books.<br />When working with juvenile members the application will check to ensure that the member is less then 18 years of age, if the member is older then 18 their membership will be automatically converted to an adult membership.<br />Librarians must be able to enter new books into the database.<br />All Overdue books, shown in the application must be highlighted.<br />The design of the Member Information page must include the use of AJAX controls so that the check in and check out functionality cause only a partial page postback.<br />The application must use hyperlinks to navigate between pages.<br />
  18. 18. Website Member Information – Check In Book<br />Library Phase 3 Project<br />
  19. 19. Website Member Information – Check Out Book<br />Library Phase 3 Project<br />
  20. 20. Check Out Book – HTML Markup and C# Code<br />Library Phase 3 Project<br />