asp.tar.gz

ASP.NET

MVC in ASP.NET Core - Models in ASP.NET

MVC in ASP.NET Core - Models in ASP.NET-copy

This course is for you if you’re looking to start your journey in either full-stack MVC or backend development with ASP.NET Core.

In the first half of the course, you’ll learn about the Model-View-Controller design pattern and how you can use it to organize and develop your web application. You’ll then dive into JSON web APIs which allow communication between your back-end ASP.NET application and front-end web/mobile application.

In the latter half, you’ll learn about the repository pattern, how relationships work, and how to add authentication and authorization to your application.

By the end of this course, you will have the confidence to develop your own applications in ASP.NET Core.

Developing Applications with ASP.NET Core

## What is normalization? And why do we use it?

In databases, normalization allows you to reduce, if not eliminate, database redundancy and inconsistency, making your databases more flexible. You achieve database normalization by breaking one table into multiple tables and creating relationships between them. The process of breaking one table into smaller tables is done by following different normalization forms.

## Example
Take the example of a Contacts application. This application needs to store names, phone numbers, email addresses, and home/work addresses. A contact can have one or more phone numbers and email addresses. A contact can either have a home address, a work address, or both. A contact can have more than one home and/or work address.

Your properties will be:

* First name
* Last name
* List of phone numbers
* List of home/work addresses

Your table could end up looking something like this:




# What is normalization? And why do we use it?

In databases, normalization allows you to reduce, if not eliminate, database redundancy and inconsistency, making your databases more flexible. You achieve database normalization by breaking one table into multiple tables and creating relationships between them. The process of breaking one table into smaller tables is done by following different normalization forms.

# Example
Take the example of a Contacts application. This application needs to store names, phone numbers, email addresses, and home/work addresses. A contact can have one or more phone numbers and email addresses. A contact can either have a home address, a work address, or both. A contact can have more than one home and/or work address.

Your properties will be:

* First name
* Last name
* List of phone numbers
* List of home/work addresses

Your table could end up looking something like this:




To normalize or not to normalize, that is the question.

Introduction

Getting Started

MVC in ASP.NET Core

JSON Web APIs in ASP.NET Core

Working with Repositories

Relationships

Authentication and Authorization

Appendix

Conclusion

Issues of Normalization

What is normalization? And why do we use it?

Example