Author: Marinko Spasojevic

.NET Core 2.0, Angular and MySQL. Navigation and the 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

.NET Core 2.0, Angular and MySQL. Preparing the Angular Project

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 the .NET Core series. For the complete navigation and all the basic instructions of the Angular series, check out: Introduction of the...

Read More

.NET Core 2.0, Angular and MySQL. 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 a POST, PUT and 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. If you want to see all the basic instructions and complete navigation for this series, please follow the following link: Introduction page for this tutorial. For the previous part check out: Creating .NET Core WebApi project – Using repository for the GET requests The source code is available for download at .NET Core, Angular and...

Read More

.NET Core 2.0, Angular and MySQL. Get Requests

In the previous post, you have created a repository pattern for collecting the data from the database. Now, it is time to use that repository for the business logic. You will 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 of the application. By doing so, your controllers won’t be overwhelmed with the code thus making the code easier to read and maintain as well. If you want to see all the basic instructions and complete navigation for this series, please follow the following...

Read More

.NET Core 2.0, Angular and MySQL. Repository Pattern

What is Repository pattern and why should you 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. So let’s start. If you want...

Read More