Explore ASP.NET Core by delving into MVC design, JSON web APIs, repository patterns, and adding authentication. Gain insights to confidently develop full-stack or backend applications.

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 a repository?

To make your complex application code easy to understand and manage, add a layer of abstraction. A repository does just that.

A repository helps achieve abstraction in your application by creating an abstraction layer between data access and business logic (controller). This helps to isolate your application from changes in the data store and facilitates unit testing. This promotes a loosely coupled approach to access your data from the database. It also saved you from writing the same queries across multiple controllers that achieve the same purpose.

## How is it achieved?

An interface is created with all of the declarations of the functions responsible for performing CRUD operations, among other functionalities. Then one or more repository classes are created in which your database context is injected. These repository classes implement the interface’s functions and provide their logic for handling operations. One of these repositories is then injected into your controller to provide functionality. You do not need to inject your database context into your controllers.

# What is a repository?

To make your complex application code easy to understand and manage, add a layer of abstraction. A repository does just that.

A repository helps achieve abstraction in your application by creating an abstraction layer between data access and business logic (controller). This helps to isolate your application from changes in the data store and facilitates unit testing. This promotes a loosely coupled approach to access your data from the database. It also saved you from writing the same queries across multiple controllers that achieve the same purpose.

# How is it achieved?

An interface is created with all of the declarations of the functions responsible for performing CRUD operations, among other functionalities. Then one or more repository classes are created in which your database context is injected. These repository classes implement the interface’s functions and provide their logic for handling operations. One of these repositories is then injected into your controller to provide functionality. You do not need to inject your database context into your controllers.

Learn what the repository pattern is, why it is used, and how it is achieved.

Introduction

Getting Started

MVC in ASP.NET Core

JSON Web APIs in ASP.NET Core

Working with Repositories

Relationships

Authentication and Authorization

Appendix

Conclusion

Introduction to Repository Pattern

What is a repository?