Upgrade instructions

Upgrade instructions. From Version 3.x to 5.x for .NET Framework 4.x projects

EasyQuery client-side views

Starting from version 5.0 EasyQuery.JS introduces the concept of a view . "View" - is a set of different EasyQuery widgets assembled to work together on some web page to cover a particular use-case. There are several views available out-of-the-box: AdvancedSearchView ReportView DataFilterView

Upgrade instructions: EasyQuery.NET 5.3 + EasyQuery.JS 6.0

If you use EasyQuery.JS via NPM packages (for example, in your Angular or React project) you need to do the following changes: Since JQuery is not used anyore, you can remove @easyquery/ui-jquery package from your project. All functionality from this package was moved either to @easyquery/core or @easyquery/enterprise packages. Add @easyquery/enterprise package if you need full set of features as in previous version (5.1.x) of EasyQuery. Obviously, set the version number for all EasyQuery packages to 6.0.0 (or higher). Get the license key for EasyQuery Enterprise.

Build query by code on the client-side

Here you can find an example of JavaScript code with explanation how to add columns to a current query on client-side.

Upgrade instructions: Version 7.0

You just need to update the version of all EasyQuery packages (except Korzh.EasyQuery.MsSqlGate - see the details below) to 7.0.x (whatever the latest version is there at the time of your reading). For example: should be changed to: As for Korzh.EasyQuery.MsSqlGate package, it was renamed to Korzh.EasyQuery.SqlServerGate (to prevent any confusion with Korzh.EasyQuery.MySqlGate ). Here are examples: Before EasyQuery 7.0: EasyQuery 7.0+ Both functions accepts a delegate with EasyQueryOptions parameter, so no changes here. Here are some examples: In the most cases, your client-side code and markup will not need a lot of changes with version 7.0 of EasyQuery.JS. Here are the thins that require your attention: If the license key for EasyQuery.JS is hardcoded in the page's script as a parameter of useEnterprise(...) call (like view.getContext().useEnterprise('YourEasyQueryJsKeyGoesHere') ) you will need to get a new one for version 7.0 and replace it there.

Upgrading from version 3.x to 4.0

How to upgrade your project from version 3.x to version 4.0 of EasyQuery

Upgrading from version 2.x to 3.0

How to upgrade your project from version 2.x to version 3.0 of EasyQuery

Upgrading from version 4.x to 5.x

Here you will find step-by-step instructions on how to upgrade your current ASP.NET Core project that uses version 4.x of EasyQuery to version 5.0

Upgrading to 5.x: WinForms and WPF projects

This tutorial describes how to modify your old Windows Forms or WPF project with EasyQuery 3.x to upgrade to EasyQuery version 5.2.0 (or higher). Please note. Version 5.2.0 of EasyQuery works only on .NET Framework 4.6.1 or higher. So, if your project targets a lower version of .NET Framework - you will need to update Target Framework for your project first (right-click on the project in Solution

Attaching extra data to a query on the client-side

Sometimes it's necessary to attach some extra data to each query (based on some user's input on the client-side) and then use that extra data on query execution. For example, user might want to specify a date (or a period of time) as an additional filter to the any query. To add some extra data you can use beforeExecuteQuery event handler which can be defined on view initialization: Now if you check in Developer Tools (on Network tab), each .../execute request now includes ad additional data object in the request payload. Now to process this additional request data you can create your own implementation of EasyQueryManager and override its ExecuteQueryCore method. Here is an example: Here we just reconfigure our current query and add in it an additional condition group with a bunch of conditions like SomeColumns contains 'filter text' Finally, you need to register your manager class on EasyQuery middleware initialization: NB: Please note that you can read the ClientData property in any method of your custom manager.

Upgrading to 5.x: ASP.NET (MVC and WebForms) projects

This tutorial describes how to upgrde your old ASP.NET MVC project with EasyQuery 3.x to EasyQuery version 5.2.0 (or higher). 1.2 Use NuGet Package Manager to install the following packages: Korzh.EasyQuery.AspNet4 Korzh.EasyQuery.EntityFramewok6 - if you are using Entity Framework 6.x Korzh.EasyQuery.DataExport - if you will need the data exporting functions Korzh.EasyQuery.MsSqlGate (or .MySqlGate or .OdbcGate depending on your DB) - if you need to load your model directly from DB connection. Finally, we need to make some modifications on our pages where we use EasyQuery scripts. Version 5.2.0 and higher of EasyQuery scripts will not need JQuery anymore, so you will be able to throw them away if they are not used in your own pages. Here is an example for "advanced search" view: To update your Web Forms page your will need to do the following 3 steps: Add EasyQuery scripts and styles on your page.

Custom client-side dialogs

Users who use some other dialogs libary usually want to replace those default dialogs with their own. We are going to replace those default dialogs with nice HTML dialogs made with JQuery UI dialogs library. The approach we will use is quite simple: our AdvancedSearchView JavaScript class has several methods which can be "overriden" to replace the default behavior with your own implemenation of those dialogs. In case of using JQuery dialogs we need to define some placeholders (read div elements) on our page where our new dialogs will be rendered. Here is an example: NB: Please note that this step is specific for JQuery dialogs.

Dynamic queries for ASP.NET Core projects with Entity Framework Core

It takes a few minutes to add a new page with all necessary UI for building dynamic queries and to setup a middleware that will process all requests from that page, convert those request to the queries to your DB and return the result set back for visualization. This step is necessary to get the trial keys for EasyQuery framework. One for ASP.NET Core packages and another one - for EasyQuery.JS scripts. To simplify this task EasyQuery includes a Razor UI library package ( Korzh.EasyQuery.RazorUI ) that contains several predefined pages which you can use in your projects. For example, there is an "advaced search" page which is available via /EasyQuery/AdvancedSearch .

Building dynamic queries with EasyQuery and Entity Framework

Here we describe how EasyQuery helps to implement a query building UI for creating custom, dynamic queries in .NET projects which use Entity Framework (6.x)

EasyQuery.NET 5.4.1 + EasyQuery.JS 6.1.0 release notes

Better performance It takes less time and memory for the new grid to render the same amount of data. It's easier now to define the styles for different parts of the grid and to set custom styles for each column or even for a particular cell. The code of our new grid was moved to a separate NPM package ( @easydata/ui ) and so, can be used even without EasyQuery at all. This new widget allows us to define different views for your result set. As already said, our server-side API code (EasyQuery middleware for .NET Core and WebAPI controller for .NET 4.x) was updated to support the new data format and other changes in EasyQuery.JS 6.1.0 Version 5.4.1 also includes a possibility to save/load queries to/from the files on the visitor's computer.

ASP.NET Core tutorials

This section contains all getting started articles for the version 5.x branch of EasyQuery for .NET Core. Please note if you have a project for .NET Framework (version 4.x or earlier) - please look at the articles in [$$-Version 3.x-$$](/$aid/eqdn-6f1z3hf0ml4u) section.

Managing data formats

This article shows how to implement some particular tasks with your query

Getting started for ASP.NET WebForms

Here you can find the instructions how to add EasyQuery components into your ASP.NET WebForms project

Gridview filtering with EasyQuery ASP.NET (WebForms)

Gridview filtering with EasyQuery ASP.NET (WebForms)