ASP Net MVC 3Tier

Real Time Asp.Net MVC Web App On 3-Tier

Mohd Manzoor Ahmed (www.ManzoorTheTrainer.com)

www.ManzoorTheTrainer.com

Asp.Net MVC Web App on 3-Tier for Beginners

(Part-1)

–

Objective: The objective of this article series i s to make the beginners understand how the data moves from one layer to another layer in Asp.Net MVC web app when it i s designed on 3-layers. Overview: Q. Do you want to see a live web app built on 3-Tier arch using Asp.Net MVC, jQuery, Bootstrap, C#.Net, Entity Framework and MS SQL S erver? A. Here it is http://linkhub.manzoorthetrainer.com/ Q. Are you really excited to learn how to develop this 3-tier web app on Asp.Net MVC and Entity Framework? A. Then you are going to learn it here with me from scratch. In this article we are going to learn how to break requirements into objects and find relation among them. We will then learn designing database out of this objects and relationships. Moving forward we will also see how to design a basic 3-Tier architecture of the project and implement various layers. We are going to learn implementation of business object layer using Entity Framework and data access layer using repository design pattern and Entity Framework. For user interface we will see Asp.Net MVC, jQuery and Bootstrap. We will learn how bootstrap makes our application responsive. We will also see how to i mplement custom sorting and paging. Moving ahead you will learn forms validations and business rules validations as well. We are going to secure our app usi ng custom membership provider and role provider and publish it on web. In Advance operations we will try to understand how to implement transactions, bind multiple models to single view and Ajaxifiying our Asp.Net web App. Finally we will also see few SSRS client side reporting. Tools Requirements:  

SQL Server 2008 Express or Higher VS2013 express or higher

Target Audience:  

Should be good at OOPs through C#.Net Should have good understanding of Asp.Net MVC and Entity Framework

Disclaimer: The sample code is solely based on my self -study, research results and based on any practical project. The code is just for the purpose to explain the overall architecture only. If you want to use the code in your project, you need to enrich and modify it to meet your own need. In addition, the CRUD operations in the sample project is very primitive with basic features, you can enrich them with some advanced features. Content: 1: Introduction

Complete video tutorial of this course at a discount of 50% is here

Enroll Now

1|Page


Introduction 2: Analysis And Design Requirements Gathering, Identifying Objects And Relationships, Designing Database, Database Implementation And Understanding Architecture, Creating Solution And Projects. 3: Implementing All The Layers Creating Business Object Layer Using Entity Framework, UI Prototyping, Designing Controllers And Actions, Implementing Bootstrap 4: Implementing User And Admin Module Creating Data Access Layer Using Repository Design Pattern, Creating Business Logic Layer And Implement BrowseUrLs, Filtering BrowseURLs, Impl ementing Custom Sorting in MVC on BrowseUrls table, Implementing Custom Paging in MVC on BrowseUrls table, Implementing ListUsers, ListCategory And DeleteCategory 5: Architectural Enhancements And Validations Implementing CreateCategory With Forms Validation, Implementing SubmitUrl And Adding Base Class in BLL - AdminBsClass, Creating Base Classes For BLL And ControllersI, mplementing Approve Urls And UserRegistration 6: Securing Asp.Net MVC Web App Implementing Authentication-I, Implementing Authentication-II, Implementing Authorization 7: Applying Bootstrap Theme Applying New Bootstrap Theme And Implementing Slider-I, Applying New Bootstrap Theme And Implementing Slider-II 8: Implementing Transactions Binding Multiple Models To A Single View, Working With Identity Field, Transactions 9: Ajaxifying An MVC App Ajaxifying Demo, Making A JQuery Based Ajax Call, Implementing Approve And Reject ALL With Update Progress Bar, Partial Page Update In MVC 10: External Login Login With Gmail, Login With Facebook 11: The Final Push ProjectSetup - Source Code, Publishing Your Site Live 12: Reports In Asp.Net MVC RDLC Reports In Asp.Net

1: Introduction Complete video tutorial of this course at a discount of 50% is here

Enroll Now

2|Page


Introduction: Link hub is a web portal where a user can submit their portal URL under a specific category to be shared on link hub. Admin can approve or reject the URL submitted by the user and in each case an email is sent out to the user. Once the link is approve it will be available on the link hub portal. This is what we are going to achieve: Screen-1. User Registration

Screen-2: User Login

Screen-3: Submit URL After Login


Enroll Now

3|Page


Screen-4: URL approval by Admin

Screen-5: Browse All The Approved URL


Enroll Now

4|Page


Note: In future articles we will also try to do see some extra features whose screen are not described here. 2: Analysis And Design (Requirements Gathering, Identifying Objects And Relationships, Designing Database, Database Implementation) Let us say that the client has given us a b rief requirements or you can also called it as user story i.e., They need to develop a portal called as LINKHUB… Link hub is a web portal where a user can submit their portal URL under a specific category to be shared on link hub. Admin can approve or reject the URL submitted by the user and in each case an email is sent out to the user. Once the link is approve it will be available on the link hub portal. Step-1: From the above requirements let us define the roles and responsibilities first Defining the Roles & Responsibilities Roles: 

User o o o



Can Browse URLs Can Register Can Submit A URL

Admin o o o

Can CRUD Category Can View All Users Can ApproveOrReject URL

Step-2: Now let us identify the object Objects


Enroll Now

5|Page


  

User Category URL

Step-3: Now we need to find the relationship among these objects Relationships  

Category : Url (1:M) (As a single category can have many urls) User : Url (1:M) (As a single user can upload many urls)

Step-4: Once we have objects and relationships with us, we can g o designing the data base with the 3 key rules of database design 3 Key Rules For Database Design 1. One table for each object 2. For 1:M relationship. 1 will become master and M will become chil d i.e., primary key of 1 will act as a foreign key for M. Eg:Department : Employees is 1 : M Department

3. M:M relationship. Both the objects will become master and there will be one more new table called as transaction table or child table with primary keys of masters as foreign Keys in it. Eg:Student : Course is M : M


Enroll Now

6|Page


With these above three rules our data base design would look something like this and role column in the tbl_User table will differentiate a normal user as ‘U’ and Admin as ‘A’

LinkHubDb Let us implement it:


Enroll Now

7|Page


Step-5: Once we have our datadase ready we need to insert few meaning full and dummy records which will help us in further implementation process.

Understanding The Architecture:


Enroll Now

8|Page


Data Access Layer: In the above architecture our application’s back end is MS SQL Server and to access the data from the database we are using ADO.Net Entity Framework and we call it as Data Access Layer (DAL).

Business Logic Layer: Before I store data into the database or after reading data from the database I need to perform some business logic on the data. For example I want to store the salary of an employee and it is $25 per hour and say he is worked for 50hrs. So, his salary would be calculated as 25X50=1250$ which is called as business logic and this logical code will go to business logic layer and it will be developed using C#.Net programming language. So, here it is Business Logic Layer (BLL).


Enroll Now

9|Page


UI: Now, how do I interact with the application? Yes, the interface from which I interact with the application is called as user interface of presentation logic layer where we see all the form controls like textboxes, buttons, grids, etc., and we are going to use Asp.Net MVC 5 to implement our presentation Logic layer (PLL).

Business Object Layer: And finally how do I pass the data from one layer to another layer? We need a container to store the data so that we can pass that container to other layers and that container is called as business object and they reside in business object layer (BOL).


Enroll Now

10 | P a g e


Therefore we need to have a solution which should contain the following four project 1. 2. 3. 4.

UI (Asp.Net MVC Web App) BOL (C# Class Library to generate a dll) BLL (C# Class Library to generate a dll) DAL (C# Class Library to generate a dll)

Thanks for reading




Enroll Now


Enroll Now

11 | P a g e

ASP Net MVC 3Tier

Recommend Documents