Author: Marinko Spasojevic

Angular – Navigation and the Angular Routing

One of the every web application’s main features is navigation, and to enable it in our project, we need to use routing. The Angular Router enables navigation from one view to the next as users perform application tasks. In our navigation menu, we are going to have three menu options: one for the home screen, another one for the owner operations and the last one for the account operations. Hopefully, this will help you realize the advantages of using multiple modules inside a project and how the lazy content loading helps your application perform better. If you want to see all...

Read More

Angular – Angular Project Preparation

Angular project preparation can vary from project to project and from version to version, and this article is dedicated to that topic. Creating the server part (.NET Core Web API part) is just half of the job we want to accomplish. From this point onwards, we are going to dive into the client side of the application to consume the Web API part and show the results to the user by using angular components and many other features. If you want to see all the basic instructions and complete navigation for the .NET Core series, check out the following link: Introduction of...

Read More

ASP.NET Core Web API – Post, Put, Delete

In the previous post, we have created a GET request with some code refactoring actions. In this post, we are going to create POST PUT DELETE requests and by doing so we are going to complete the server part (.NET Core part) of this series. Let’s get into it. Creating a Database for Our Project Basic Code Preparations Logging with NLog in ASP.NET Core Repository Pattern with Entity Framework Core How to Handle Get Request Using Repository for POST, PUT and DELETE Requests (Current article) This article is part of the series If you want to see all the...

Read More

ASP.NET Core Web API – How to Handle Get Request

The Get Request in .NET Core as in any other Web API we create is the thing we can’t miss because it is the most common request. So, it is very important to learn more about handling that kind of request. In the previous post, we have created a repository pattern for collecting the data from the database. Now, it is time to use that repository for the business logic. We are going to keep all the database logic inside the repository classes. Controllers will be responsible for handling requests, model validation and returning responses to the frontend part...

Read More

ASP.NET Core Web API – Repository Pattern

What is Repository pattern and why should we use it? With the Repository pattern, we create an abstraction layer between the data access and the business logic layer of an application. By using it, we are promoting a more loosely coupled approach to access our data from the database. Also, the code is cleaner and easier to maintain and reuse. Data access logic is in a separate class, or sets of classes called a repository, with the responsibility of persisting the application’s business model. Implementing the repository pattern is our topic for this post. Additionally, this article has a strong...

Read More