EasyQuery.NET 5.4.1 + EasyQuery.JS 6.1.0 release notes
/release-notes/easyquery-net-5-4-1-easyquery-js-6-1-0Better 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 7.0 release notes
/release-notes/version-7-0Version 7.0 is a major update of both EasyQuery.NET and EasyQuery.JS. We skipped version 6.x for EasyQuery.NET (the previous was 5.4.x) to sync it with the latest version number of EasyQuery.JS and so, to make it clear that version 7.0 of the scripts requires version 7.0 of the server-side packages. The API endpoints for some actions were renamed in the new version. Provided that they both have the same version 7.0.x One of the most expected features implemented in 7.0 was an ability to set the formatting for the result set data. So, with version 7.0 the best approach will be to create an instance of some EasyQueryManager class descendant (for example, EasyQueryManagerSql ) that is the most suitable for your scenario and use its methods and properties for all necessary operations.