Getting started for ASP.NET Core + React project

Here we describe how to add EasyQuery widgets to your ASP.NET Core + React.js project.

EasyQuery samples

The easiest way to start getting acquainted with EasyQuery framework is to install and launch our demo projects available on GitHub. You can clone that repository with samples, download it as a ZIP archive or even right away!


  1. You have an ASP.NET Core (version 2.1+) project with React.js on the client-side. We suppose the project was created using a standard ASP.NET Core template (dotnet new react or ... reactredux) but it's not the requirement.
  2. Your application uses Entity Framework Core to work with the database. NB: Of course, it's possible to use EasyQuery without EF Core. We show this approach here just because it's the simplest way. For other options please read Possible ways of data model creation and loading article.

Trial version registration (for new users)

To start using EasyQuery trial you need to register and get your trial version keys first. It takes 1-2 minutes of your time. On registration you will get access to a special "Client's Area" of our web-site where you can see available licenses, get the keys, and submit a support request if necessary.

Server-side changes

First, we are going to add EasyQuery to your ASP.NET Core backend project.

1: Add EasyQuery packages to your project

Since we have a standard ASP.NET Core project with EntityFramework Core for working with the database - then we will need the following 2 EasyQuery packages be added to your .csproj file:

  • Korzh.EasyQuery.AspNetCore
  • Korzh.EasyQuery.EntityFrameworkCore.Relational

Hint: To add packages use NuGet Package Manager in Visual Studio (Tools | NuGet Package Manager | "Manager NuGet Packages for Solution menu item).

2: Add EasyQuery services and middleware

The next step will be to setup EasyQuery services and the middleware. Here are the parts your will need to add to your Startup class.

First of all, if you are using trial version, you need to set the trial version keys you got after the registration:

public Startup(IConfiguration configuration, IWebHostEnvironment env)
    Configuration = configuration;

    Korzh.EasyQuery.AspNetCore.License.Key = "YourEasyQueryNetTrialKey";
    Korzh.EasyQuery.AspNetCore.JSLicense.Key = "YourEasyQueryJsTrialKey";

NB: You will replace these keys on the real (non-trial ones) after purchasing the license.

After that, add the inialization code for EasyQuery services in ConfigServices method:

public void ConfigureServices(IServiceCollection services)
    .    .    .    .   .   .

The code above performs two tasks:

  • The first line registers EasyQuery services in the dependency injection container.
  • The second one specifies the default EasyQuery manager which is the main "engine" that covers the most of EasyQuery functions: saving and loading of the models and queries, SQL generation, data retriving and exporting, etc. Currently there are two possible options: EasyQueryManagerSql and EasyQueryManagerLinq.

Finally, we need to set up the middleware which will handle HTTP requests from the client-side, pass them to the manager, takes the result and prepare it for sending back to the client. To avoid any conflicts with MVC or SPA handlers we put EasyQuery middleware before them:

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    .   .   .   .   .   .

    app.UseEasyQuery(options => {
        options.Endpoint = "/api/easyquery";

    app.UseMvc(routes => {
	     .    .    .    .

    app.UseSpa(spa => {
        .   .   .   .

The code above defines the following main settings:

  1. The endpoint is set to /api/easyquery. This means that all requests from EasyQuery widgets will be started with this path (like /api/easyquery/models/{modelId} to load the model). Please note that this is the default value so you can omit this setting in your app.
  2. We will use the DbContext class specified in UseDbContext call to get the model or to execute the generated queries. It's the fastest way to specify the model load and the connection to your DB. Otherwise you will need to set them separately via UseModelLoader or UseDbConnection extension functions.
  3. The last UsePaging call turns on the paging and sets the page size.

So, server-side setup is finished. Now we need to configure EasyQuery on the client-side part of our project.

Add EasyQuery view to your React app

Now it's time to configure the client-side scripts and styles. Here we suppose that your React application is placed in ClientApp subfolder of your main project's folder.

1. Adding EasyQuery styles

If you want to use the default EasyQuery styles you will need to include EasyQuery CSS files right to the index HTML file of your client-side app: ClientApp/public/index.html.

    .    .    .    .    .    .
	<!-- EasyQuery CSS -->
    <link rel="stylesheet" href="">
    <link rel="stylesheet" href="">

Additionally you can add Chat.js script file as well if you plan to show the charts for query results:

    .    .    .    .    .    .

    <!-- ChartJS scripts -->
    <script src=""></script>

2. Adding EasyQuery NPM packages

To install EasyQuery packages just open the console in your ClientApp folder and run the following command :

npm install "@easyquery/core" "@easyquery/ui" "@easyquery/enterprise"

3. Adding EasyQuery component

Here we are goint to add a new view (page) that will contain the EasyQuery "advanced search" functionality.

It terms of React.js it will be a new component which in our case will includes 2 files: EasyQuery.js (the component's code) and EasyQueryHtml.js (the JSX template).

The template part for this new view should contain several "slots" for EasyQuery widgets - some div elements with special IDs. Here are some of those IDs:

  • QueryPanel - for conditions widget
  • ColumnsPanel - for columns widget
  • ResultPanel - for result panel widget that will combine a grid to show the result set and a chart (if showChart option is turned on).

To simplify the task you can use the files from our sample project

Just copy EasyQuery.js and EasyQueryHtml.js files from there to the ClientApp/src/components folder of your project.

Explaining the component's code

EasyQuery introduces the concept of a "view". "View" - is a set of different EasyQuery widgets assembled to work together on some web page. There are several views available out-of-the-box. Here we are going to use the AdvancedSearch view.

So, basically, all you need to do, is to create an instance of some EasyQuery view class during the initialization of your React component and then call its init method. The best place to do it - is in componentDidMount method.

So, in general, the content of your component will look like the following:

import React, { Component } from 'react';

//including easyquery view classes
import { AdvancedSearchView } from '@easyquery/ui';

//including the JSX template 
import AdvancedSearchHtml  from './EasyQueryHtml';

export class EasyQuery extends Component {
    static displayName =;

    //creating an instance of EasyQuery view
    view = new AdvancedSearchView();

    componentDidMount() {
	    //setting differnt EasyQuery options
        const options = {
		  .    .    .    . 
		//initilizing the view

    render() {
	    //rendering the template
        return (
            <AdvancedSearchHtml />

    shouldComponentUpdate() {
	    //EasyQuery view will render everything by itself - so we need to inform React that this component is not affected by the changes in state or props.
        return false;

NB: Do not forget to add the import for enterprise functionality

If you want to use EasyQuery.JS Enterprise, import @easyquery/enterprise package:

    .   .   .   .   .   .   .
    import '@easyquery/enterprise'
    .   .   .   .   .   .   .

4. Wrap it up

To make new component accessible you will also need to add a new item to the main App component (in /ClientApp/src/App.js module):

import React, { Component } from 'react';
.   .   .   .   .   .   .
import { EasyQuery } from './components/EasyQuery';

export default class App extends Component {
  static displayName =;

  render () {
    return (
        <Route exact path='/' component={Home} />
		.   .   .   .   .   .   .
        <Route path='/easy-query' component={EasyQuery} />

That's all. If everything was done right you will get something like the following in result: