20 results for "$s/use-cases/$s/@tag:subquery"

Using EqMvcDemoEF sample with your own DB context

/getting-started/sample-mvc-entity-framework-new-dbcontext

This article contains a brief instruction how to modify EqMvcDemoEF sample project to make it work with your own context class

Using MS SQL instead of Access in WebDemo sample project

/getting-started/sample-webforms-change-to-mssql

In this article, you will find the detailed instructions how to modify WebDemoCS or WebDemoAjaxCS to make it work with SQL Server instead of Access

EasyQuery ASP.NET - using jQuery widgets on WebForms project

/getting-started/sample-webforms-javascript-webservice

In this article, you can find the instructions how to replace native WebForms with our jQuery widgets, with extract examples

Version 5.0 release notes

/release-notes/version-5-0

Version 5.0 is a completely rewritten major update of EasyQuery which now can be used in any ASP.NET Core (version 2.0 and higher) project and with almost any frontend platform (MVC, Razor pages, Angular, React, Vue, etc). There are a lot of changes both on the server-side part and in the client-side library (EasyQuery.JS). Below we will describe the most important ones: Core library

Working with data models in EasyQuery

/getting-started/working-with-data-model

This article will guide you through all issues about working with data models in EasyQuery library. How to load it from the DbContext or from your DB connection, or now to create a new one using Data Model Editor.

Version 5.3 + EasyQuery.JS 6.0 release notes

/release-notes/version-5-3

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

Building dynamic queries with EasyQuery and Entity Framework

/tutorials/dynamic-queries-with-easyquery-and-entity-framework

Here we describe how EasyQuery helps to implement a query building UI for creating custom, dynamic queries in .NET projects which use Entity Framework (6.x)

Data Model

/fundamentals/data-model

In short (and by its name), data model - is a model (representation) of some data stored in your database. It solves two major problems: Presents the data to the end user in a more friendly and familiar way. Contains some meta information that helps EasyQuery components to build query statements in SQL or other query languages. Any data model contains the following main sections:

Date/time values formatting

/how-to/date-time-formatting

In this article, you can find instructions how to set up different types of date & time formats, with code examples.

Getting started for ASP.NET 4

/getting-started/asp-net-4-mvc-or-webforms

Describes the steps you need to perform for applying EasyQuery ASP.NET to your MVC or WebForms project

EasyQuery License key

/getting-started/product-key

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

Upgrade instructions: Version 7.0

/upgrade-instructions/version-7-0

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

Adding a new operator to your data model

/tutorials/add-new-operator

Here you can find all information about how to add a new operator to your data model either using Data Model Editor (DME) or with a code

Version 5.2 release notes

/release-notes/version-5-2

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