We created an open source library EasyData (https://github.com/KorzhCom/EasyData) that covers all CRUD operations, both server-side API and client-side UI.
It takes all necessary information from your DbContext, so no need to modify anything when you add a new model class or change the existing one.
Paging, filtering and lookups are supported out-of-the-box.
Hope it will help someone.
One of the first tasks for most business applications is to implement CRUD (Create, Read, Update, Delete) operations for the main entities the app works with.
Every developer faces the following problems as part of solving the task:
As we already mentioned in the first article, the Startup class is the entry point for all initialization codes in your application. Long story short, the Startup defines what your application will do and how exactly it will work.
By default, any Startup class in the ASP.NET Core application includes three main parts:
When you start learning a programming language, one of your first exercises will probably be to write a “Hello World” application to figure out the basic concepts. This exercise works well if you’re writing a simple console program that will only print out the greetings on the screen.
However, once you move onto learning to write web apps using a new framework, such as ASP.NET Core, such a simple code is not enough — partially because web apps are more complex. …
The concept of Dependency Injection can seem complicated, especially for beginners. Here, I have tried to explain it by using a very simple example from the real world: a food delivery app on your mobile phone.
So, imagine you open such an app on your smartphone. Let’s see what we have here:
Obviously, this app has a menu with a description of each item available there. To make it more similar to the Dependency Injection (DI) container let’s suppose all items on the menu are more or less generic. So, you have such options as a burger, chips, green salad…
Choosing a platform is not easy when you start reflecting on your future as a software developer, especially if you are a newbie. Mastering any programming language takes long hours and an effort you don’t want to waste. And it’s stressful to think that the wrong option might lead you to a job where you will have to change your knowledge base again.
Ok, let’s switch to the positive side. Since you are here, your options are narrowed down to these two: Java or .NET. That’s already a huge move forward. Both options are already a kind of win. Java…
The ASP.NET Core documentation explains thoroughly what a claim is and how to check for a claim. However, there is no information about how to create a new claim and attach it to the user object.
Here we are going to close this gap and provide you with step-by-step instruction on how to add a new claim and use it on views (pages) or in any other part of your ASP.NET Core application.
Let’s describe the task we are going to solve.
ORM (object-relational mapping) frameworks really simplify the developer’s life for all database-related tasks.
However, as it usually happens, such simplification comes with a price. In most cases, the price is flexibility and performance.
In this article, I’m going to describe the three most simple approaches to increase the performance of Entity Framework Core (EF Core) operations in your .NET Core applications.
We start with the most obvious advice which actually can give you the biggest performance boost in some cases when EF Core is not used properly.
So, imagine a very common situation:
Seeding your database can be a quite tricky task. Here we are going to introduce some tools which simplify this operation.
When we distribute a .NET (Core) project, it’s often essential to create and fill the underlying database with some data on the first launch of the app.
For example, let us imagine you have a demo app of some library and for its presentation, it is necessary that the database already have some data. …