EasyQuery client-side views
/fundamentals/easyquery-client-side-viewsStarting from version 5.0 EasyQuery.JS introduces the concept of a view . "View" - is a set of different EasyQuery widgets assembled to work together on some web page to cover a particular use-case. There are several views available out-of-the-box: AdvancedSearchView ReportView DataFilterView
Version 3.x (obsolete)
/getting-started/version-3-xContains the "getting started" articles for version 3.x branch of EasyQuery. This section includes the tutorials for Windows Forms, WPF, WebForms and old ASP.NET MVC (not Core) editions of the library.
Version 5.x
/how-to/version-5-xContains the articles with solutions for different scenarios built on top of EasyQuery 5.0 (or higher)
Version 4.x (obsolete)
/getting-started/version-4-x-obsoleteGetting started articles for the old version (4.x) of EasyQuery for .NET Core
Build query by code on the client-side
/how-to/build-query-by-code-on-clientsideHere you can find an example of JavaScript code with explanation how to add columns to a current query on client-side.
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
Attaching extra data to a query on the client-side
/tutorials/attaching-extra-data-to-query-client-sideSometimes it's necessary to attach some extra data to each query (based on some user's input on the client-side) and then use that extra data on query execution. For example, user might want to specify a date (or a period of time) as an additional filter to the any query. To add some extra data you can use beforeExecuteQuery event handler which can be defined on view initialization: Now if you check in Developer Tools (on Network tab), each .../execute request now includes ad additional data object in the request payload. Now to process this additional request data you can create your own implementation of EasyQueryManager and override its ExecuteQueryCore method. Here is an example: Here we just reconfigure our current query and add in it an additional condition group with a bunch of conditions like SomeColumns contains 'filter text' Finally, you need to register your manager class on EasyQuery middleware initialization: NB: Please note that you can read the ClientData property in any method of your custom manager.
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
Getting started for WPF
/getting-started/version-3-x/wpfYou will be able to apply EasyQuery WPF to your application, performing all the instructions in this article
Version 4.2.0 release notes
/release-notes/version-4.2.0EasyQuery for ASPNET Core: version 4.2.0 release notes
Getting started for Silverlight
/getting-started/silverlightThis article will guide you through all steps necessary to apply EasyQuery.NET to your application, with extract examples
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