EasyQuery License key
/getting-started/product-keyHere we describe how to apply the product key that you get after purchasing the license and which allows you to unlock all the features of EasyQuery library.
Signals enum
/api-reference/korzh-easyquery-winforms/korzh-easyquery-winforms-namespace/signals-enumEnumerates all possible internal signals
Query with OR operators
/tutorials/query-with-or-operatorsIn this article, you will learn how to build queries that contain both AND and OR operators.
Version 5.2 release notes
/release-notes/version-5-2Version 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.
Version 5.3 + EasyQuery.JS 6.0 release notes
/release-notes/version-5-3The biggest change in this release is a new major update (version 6.0) of JavaScript library (EasyQuery.JS) used with ASP.NET or ASP.NET Core editions of EasyQuery. Version 5.3 of EasyQuery contains rather small improvements in the core libraries and all .NET editions. Community edition packages include @easyquery/core , @easyquery/ui . All license owners of EasyQuery for ASP.NET or EasyQuery for ASP.NET Core automatically got a license for EasyQuery.JS as well. to set your key, now for ASP.NET Core edition it will be Respectively, you should use Korzh.EasyQuery.AspNet...
EqExpression class
/api-reference-5x/korzh-easyquery-namespace/eqexpression-classRepresents common expression object.
Upgrade instructions: EasyQuery.NET 5.3 + EasyQuery.JS 6.0
/upgrade-instructions/net-5-3-js-6-0If 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.
EqExpression class
/api-reference/korzh-easyquery/korzh-easyquery-namespace/eqexpression-classRepresents common expression object.
Dynamic queries for ASP.NET Core projects with Entity Framework Core
/tutorials/dynamic-queries-ui-aspnet-core-entity-frameworkIt 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 .
Getting started for ASP.NET Core + MVC or Razor pages
/getting-started/aspnet-core-razorHow to use install EasyQuery to your ASP.NET Core project with Razor Pages or MVC.
DbExprTag class
/api-reference-5x/korzh-easyquery-db-namespace/dbexprtag-classContains several constants for db-related expressions tags values
DbExprTag class
/api-reference/korzh-easyquery-db/korzh-easyquery-db-namespace/dbexprtag-classContains several constants for db-related expressions tags values
ExprTag class
/api-reference-5x/korzh-easyquery-namespace/exprtag-classContains several constant definitions for expressions tag
ExprTag class
/api-reference/korzh-easyquery/korzh-easyquery-namespace/exprtag-classContains several constant definitions for expressions tag
Getting started for ASP.NET 4
/getting-started/asp-net-4-mvc-or-webformsDescribes the steps you need to perform for applying EasyQuery ASP.NET to your MVC or WebForms project
Terminology
/fundamentals/terminologyCommon terms Database - may refer to any data storage but in most cases we mean some relational database such as MS SQL Server, My SQL, Oracle, etc. Result set - a result of some search request (query). Usually, is presented as tabular data. Query - a search request. Query condition - one of the search terms (for example: "Customer name starts with 'A'")
Using EqMvcDemoEF sample with your own DB context
/getting-started/sample-mvc-entity-framework-new-dbcontextThis article contains a brief instruction how to modify EqMvcDemoEF sample project to make it work with your own context class
QueryExpr class
/api-reference-5x/korzh-easyquery-namespace/queryexpr-classRepresents a sub-query expression