daniel rivera .net portfolio

My PortfolioExamples of my development experience with Microsoft .NET

September 1, 2011

Daniel Riveradaniel.dr.rivera@gmail.com

(203)521-7032 (C)

(203)874-9334 (H)

1

Table of Contents

Topic Slide

• .NET Framework Project 3

• .NET Framework Class Diagrams 4-5

• Library Project

• Phase 1 – Develop an ASP.NET Client 6

• Master and Content Pages

• Library Functionality

7-9

10-27

• Phase 2 – Develop Business Layer and Data Transfer Objects 28

• LINQ to SQL Class Diagram 29

• Phase 3 – Develop Web Services using WCF 30

• A

2

.NET Framework Project

• Objective• The goal was to create and test two assemblies that would be part of the business tier for

a retail company.

• Summary• The first assembly developed was a class library project called Foundation. It contained

various interfaces and base classes.

• 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.

• The focus of this project was on Object-Oriented Programming with C#, through the use

of the following concepts:

Inheritance, class properties, abstract classes and methods, interfaces, method

overloading and overriding, enumerations, custom exceptions, delegates, collections

and generics.

3

The AppTypes Assembly

4

The Foundation Assembly

5

Phase 1 – Develop an ASP.NET Client

• Objective• 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.

• Summary• Developed a front-end client application for interacting with the library system using

ASP.NET.

• Developed a user interface that was intuitive to use which required minimal training and

exposure to perform common librarian tasks.

• Utilized the data access and business logic .NET assemblies provided to access the

existing SQL Server database and provide the business logic required.

• The Librarians were authenticated in the web application using the ASP.NET security

models.

6

Master Page for the Library

7

Add Member Content Page

8

Check-In Content Page

9

Library Homepage

10

Library Login Page

11

Library Homepage after Login

12

Add a Adult Member

13

Adult Member added Successfully

14

Item Search

15

Item Search Successful

16

Item Check-Out Successful

17

Selecting Items in Grid View

18

Add a Juvenile Member

19

Adult Sponsor Search

20

Juvenile Member added Successfully

21

Item Check-in search

22

Item Check-in search Successful

23

Item Check-In Successful

24

Expired memberships, and overdue

items

25

Item not found

26

Input Validation

27

Phase 2 – Replace the Business Layer

and Data Transfer Objects

• Objective• 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.

• Summary• Replaced the Business Layer and Data Transfer Objects assemblies previously provided

with ones that I developed.

• Ensured that the assemblies developed continued to provide the functionality previously

provided.

• Used LINQ to SQL to implement data access logic for querying and updating the

database.

28

LINQ to SQL Class

29

Phase 3 – Develop Web Services using

WCF

• Objective• 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.

• Provide interoperability with other systems by implementing Web Services that offers access to the business layer.

• Security must be employed by securing the Web Services.

• Use the existing ASP.NET front-end for the client layer.

• Summary• Used Windows Communication Foundation (WCF) to implement the Web Services.

• The Web services were hosted on IIS.

• Updated the Data Transfer Objects assembly to allow for serialization across the Web Services.

• Removed all references to the Data Transfer Objects and Business Layer assemblies from the ASP.NET client.

• Updated the ASP.NET client to utilize the Web Services

30

Connecting to WCF Service

31

Services exposed through WCF

32

Result of testing GetMember Service

33