Upgrading from version 3.x to 4.0
/release-notes/upgrade-from-3.x-to-4.0How to upgrade your project from version 3.x to version 4.0 of EasyQuery
Upgrading from version 2.x to 3.0
/release-notes/upgrade-from-2.x-to-3.0How to upgrade your project from version 2.x to version 3.0 of EasyQuery
Upgrade instructions: Version 7.0
/upgrade-instructions/version-7-0You 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.
Version 5.x release notes
/release-notes/version-5-xThis section contains all "release notes" articles for version 5.x
Version 4.x release notes
/release-notes/version-4-xRelease notes articles for all version 4.x releases
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.
Version 4.4.2 release notes
/release-notes/version-4-4-21. Core library UseParameters options in EqServiceProvider class. Now you don't need to define your own QueryBulider handler. Just set eqService.UseParameters = true and all SQL statements will be generated with parameters. Add parameter processing for the special date/time values (like this month , previous year , etc). Fixed: parameters didn't work in sub-queries
Version 4.2.0 release notes
/release-notes/version-4.2.0EasyQuery for ASPNET Core: version 4.2.0 release notes
Version 4.3.1 release notes
/release-notes/version-4-3-11. Core library FullTextSearch extension method - now you can easily set up a full-text search functionality in your app ODataQueryBuilder class - allows to build OData queries ToSql extension method for LINQ expressions - now you can easily get an SQL statement for your LINQ query generated by our components
Version 4.1.0 release notes
/release-notes/version-4.1.0EasyQuery for ASPNET Core: version 4.1.0 release notes
Version 7.2 release notes
/release-notes/version-7-2Version 7.2 is a minor update of EasyQuery.NET and EasyQuery.JS. In the previous version EntityFramework Core EasyQuery packages (Korzh.EasyQuery.EntityFrameworkCore.Relational and Korzh.EasyQuery.EntityFrameworkCore.Identity) didn't include .NET 6 in the list of target frameworks. Now you can move all configuration for EasyQuery middleware to a special class that implements this interface, register this class in DI and all EasyQuery settings will be applied automatically when needed. It's very useful when you have several EasyQuery endpoints with just a slightly different settings or you need to use the same EasyQuery configuration both in the middleware and some background service. Here is a quick guide on how to set up EasyQuery with IEasyQueryConfigurator: Step 1: On DI setup: Step 2: On EasyQuery middleware setup: For applications that still use Startup.cs: Step 3: MyEasyQueryConfigurator class:.