20 results for "how-to/upgrade-instructions/net-framework-3-x-to-5-x-/release-notes/easyquery-net-5-4-1-easyquery-js-6-1-0"

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

/upgrade-instructions/net-5-3-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.

Upgrading from version 3.x to 4.0

/release-notes/upgrade-from-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

/release-notes/upgrade-from-2.x-to-3.0

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

Version 5.x release notes

/release-notes/version-5-x

This section contains all "release notes" articles for version 5.x

Version 4.x release notes

/release-notes/version-4-x

Release notes articles for all version 4.x releases

Version 4.4.2 release notes

/release-notes/version-4-4-2

1. 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

EasyQuery.NET 5.4.1 + EasyQuery.JS 6.1.0 release notes

/release-notes/easyquery-net-5-4-1-easyquery-js-6-1-0

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.

Version 4.2.0 release notes

/release-notes/version-4.2.0

EasyQuery for ASPNET Core: version 4.2.0 release notes

Version 4.1.0 release notes

/release-notes/version-4.1.0

EasyQuery for ASPNET Core: version 4.1.0 release notes

Version 4.3.1 release notes

/release-notes/version-4-3-1

1. 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 7.2 release notes

/release-notes/version-7-2

Version 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:.