Daniel Rivera .NET Portfolio


Published on

My .NET Portfolio

Published in: Technology
  • 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

Daniel Rivera .NET Portfolio

  1. 1. Daniel Rivera<br />daniel.dr.rivera@gmail.com<br />(203)521-7032 (C)<br />(203)874-9334 (H)<br />My PortfolioExamples of my development experience with Microsoft .NET<br />September 1, 2011<br />1<br />
  2. 2. Table of Contents<br />2<br />
  3. 3. .NET Framework Project<br />Objective<br /><ul><li>The goal was to create and test two assemblies that would be part of the business tier for a retail company. </li></ul>Summary<br /><ul><li>The first assembly developed was a class library project called Foundation. It contained various interfaces and base classes.
  4. 4. The second assembly developed was also a class library project called AppTypes . It contained various entity, collection, and exception classes that would be used by the various business processes.
  5. 5. The focus of this project was on Object-Oriented Programming with C#, through the use of the following concepts:</li></ul>Inheritance, class properties, abstract classes and methods, interfaces, method overloading and overriding, enumerations, custom exceptions, delegates, collections and generics.<br />3<br />
  6. 6. The AppTypes Assembly<br />4<br />
  7. 7. The Foundation Assembly<br />5<br />
  8. 8. Phase 1 – Develop an ASP.NET Client<br />Objective<br /><ul><li>A database has been created to support the principle functions to support a library’s day to day operations: primarily adding new members and the checking in or out of books. Two .NET assemblies have also been created to access the database system and provide the core business logic functionality for the system.</li></ul>Summary<br /><ul><li>Developed a front-end client application for interacting with the library system using ASP.NET.
  9. 9. Developed a user interface that was intuitive to use which required minimal training and exposure to perform common librarian tasks.
  10. 10. Utilized the data access and business logic .NET assemblies provided to access the existing SQL Server database and provide the business logic required.
  11. 11. The Librarians were authenticated in the web applicationusing the ASP.NET security models.</li></ul>6<br />
  12. 12. Master Page for the Library<br />7<br />
  13. 13. Add Member Content Page<br />8<br />
  14. 14. Check-In Content Page<br />9<br />
  15. 15. Library Homepage<br />10<br />
  16. 16. Library Login Page<br />11<br />
  17. 17. Library Homepage after Login<br />12<br />
  18. 18. Add a Adult Member<br />13<br />
  19. 19. Adult Member added Successfully<br />14<br />
  20. 20. Item Search<br />15<br />
  21. 21. Item Search Successful<br />16<br />
  22. 22. Item Check-Out Successful<br />17<br />
  23. 23. Selecting Items in Grid View<br />18<br />
  24. 24. Add a Juvenile Member<br />19<br />
  25. 25. Adult Sponsor Search<br />20<br />
  26. 26. Juvenile Member added Successfully<br />21<br />
  27. 27. Item Check-in search<br />22<br />
  28. 28. Item Check-in search Successful<br />23<br />
  29. 29. Item Check-In Successful<br />24<br />
  30. 30. Expired memberships, and overdue items<br />25<br />
  31. 31. Item not found<br />26<br />
  32. 32. Input Validation<br />27<br />
  33. 33. Phase 2 – Replace the Business Layer and Data Transfer Objects<br />Objective<br /><ul><li>In Phase 1, a front-end was built to support the library operations. For this phase, the assemblies provided to support the UI in the previous phase will be replaced by new data access and business layer assemblies.</li></ul>Summary<br /><ul><li>Replaced the Business Layer and Data Transfer Objects assemblies previously provided with ones that I developed.
  34. 34. Ensured that the assemblies developed continued to provide the functionality previously provided.
  35. 35. Used LINQ to SQL to implement data access logic for querying and updating the database.</li></ul>28<br />
  36. 36. LINQ to SQL Class <br />29<br />
  37. 37. Phase 3 – Develop Web Services using WCF<br />Objective<br /><ul><li>As the potential to acquire libraries and creating partnerships with others increases, we need to allow the library system to be interoperable with other systems.
  38. 38. Provide interoperability with other systems by implementing Web Services that offers access to the business layer.
  39. 39. Security must be employedby securing the Web Services.
  40. 40. Use the existing ASP.NET front-end for the client layer.</li></ul>Summary<br /><ul><li>Used Windows Communication Foundation (WCF) to implement the Web Services.
  41. 41. The Web services were hosted on IIS.
  42. 42. Updated the Data Transfer Objects assembly to allow for serialization across the Web Services.
  43. 43. Removed all references to the Data Transfer Objects and Business Layer assemblies from the ASP.NET client.
  44. 44. Updated the ASP.NET client to utilize the Web Services </li></ul>30<br />
  45. 45. Connecting to WCF Service<br />31<br />
  46. 46. Services exposed through WCF<br />32<br />
  47. 47. Result of testing GetMember Service<br />33<br />