Upgrade instructions

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

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

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.

Edit link dialog

Here you can find all necessary information of how to edit link dialog and how to add new conditions.

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

Entity class

Represents one entity

Entity class

Represents one entity

Entity class

Represents one entity

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)

Entities page

This page describes entities participating in the data model and their attributes.

Hide some entities and/or attributes

Here we explain how to implement different ways to limit the quantity of entities and attributes shown in Data Model

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.

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 .

Dynamic populating of value lists in WinForms or WPF editions

Example of how to solve this problem

Navigate through data model entities and attributes

A code snippet which demonstrates how to run through data model entities and attributes

Version 5.2 release notes

Version 5.2 of EasyQuery not only brings some improvements to the .NET Core edition, it;s also the first release of 5.x branch for all other editions of EasyQuery which uses on .NET Framework 4.x and still were on 3.x branch until now: WinForms, WPF and ASP.NET 4 editions. There are 2 big changes in ASP.NET edition of EasyQuery which affects your MVC project when you upgrade to EasyQuery version 5.2.0 or higher. Starting from version 5.2.0 EasyQuery for ASP.NET uses the latest version of the client-side library (EasyQuery.JS 5.1.8 for now) which is the same that is used in ASP.NET Core edition. The same as for MVC applications, for WebForms we now use the latest version of EasyQuery.JS library on the client-side and a WebAPI controller on the server-side. Bug fixed: Disabled columns were included into GROUP BY section Bug fixed in WPF edition: Empty column title on edit Bug fixed in WPF edition: Wrong behavior of "Duplicate condition" operation If you are upgrading from version 5.x for ASP.NET Core - you just need to change the version numbers of all EasyQuery NuGet packages you are using to 5.2.0 and the version of the EasyQuery script files (or NPM packages) to 5.1.8 NB : For the users of EasyQuery script bundles (like eq.all.min.js ) published on our CDN You will also need to modify the full path to the EasyQuery classes and add ui namespace to it.