Active Query Builder 3 ASP.NET Edition History

August 02, 2019

Active Query Builder 3 ASP.NET Edition v.

= Query Results Demo is updated in all demo projects.  
- Criteria Builder: the bug with the date picker has been fixed.

June 26, 2019

Active Query Builder 3 ASP.NET Edition v.3.4.7

+ The new AQB.Web.UseRelativePaths property allows to treat paths to
  handlers as relative which allows not to hardcode virtual directory.
  Default: False.
= The QueryBuilder.DataSourceOptions.HideAsteriskItem property now affects 
  the dropdown list in the Expression column of the Query Columns List.
= The AQB.Web.QueryBuilder.onQueryBuilderReady event is now fired when 
  the UI is really operable by the user.
- The bug with setting an empty string to the setSql() method when there's
  no SQL Editor on the page has been fixed.

June 03, 2019

Active Query Builder 3 ASP.NET Edition v.3.4.6

+ "Query Results" demo has been added to JavaScript demo projects for
  Classic ASP.NET and ASP.NET Core.
- Minor synchronization issues for operations with datasources performed 
  right after switching to another sub-query have been fixed.
- The bug with serializing the state of the Query Columns Grid in XML layout 
  has been fixed. This led to problems working with a custom state storage 
  provider relying on the query model serialization.
= Error handling on initializing the component via the configuration file 
  has been improved.
- The bug with displaying of primary key icons has been fixed.
- The bug with removing of a CTE sub-query currently displayed on the Design 
  Pane has been fixed.

May 25, 2019

Active Query Builder 3 ASP.NET Edition v.3.4.5

= Status bar can be closed manually now.
+ The new VerifyingQueryElements demo has been added to illustrate preserving
  of specific query parts despite the user's intention to remove them.
+ New server-side events have been added to the QueryBuilder class: 
  QueryColumnListItemAdding, QueryColumnListItemChanging, 
  QueryColumnListItemRemoving, DataSourceAdding, DataSourceRemoving,
  DataSourceFieldAdding, DataSourceFieldRemoving, LinkRemoving, LinkCreating,
+ GridComponent.Events.GridOnReload client event has been added.
+ The '-ing' QueryBuilder client events can now be used to abort user actions:
  DataSourceFieldAdding, DataSourceFieldRemoving, DataSourceDeleting.
- The bug with loading child items of custom Metadata Structure nodes has been
- The grid.findRowsByExpression method changed, used strict expression 
  comparison instead.

May 01, 2019

Active Query Builder 3 ASP.NET Edition v.3.4.4

+ The new demo project to illustrate the component's usage in a Web API
  project with IoC controller, token-based state saving, and Angular client  
  has been added.
- Unintended datasource collapsing in derived tables on subquery switching 
  has been fixed.
- Minor bugs in demo projects have been fixed.
- Restoring layout for queries with virtual objects has been fixed.

April 12, 2019

Active Query Builder 3 ASP.NET Edition v.3.4.3

! Breaking change for ASP.NET Core: IActiveQueryBuilderService has been split into
  two services: IQueryBuilderService and IQueryTransformerService. Both services 
  are initialized with the services.AddActiveQueryBuilder method. The second service
  is needed if you use the CriteriaBuilder control which is tied to QueryTransformer
  object on the server side. Please refer to the Query Results demo project to
  review the usage code sample. 
+ All appropriate demo projects are ported to the ASP.NET Core platform. 
  (only for C# language). 
- Several demo projects for WebForms and MVC have been fixed. 
- Minor bug fixes are made.

March 13, 2019

Active Query Builder 3 ASP.NET Edition v.3.4.2

- Expanding fields for tables in the search results of Database Schema Tree 
  by clicking on the expand/collapse indicator is possible now. 
+ The new AQB.Web.QueryBuilder.makeLayout method has been added to create 
  the component's layout. It should be used when the component is not visible
  on page load.

March 11, 2019

Active Query Builder 3 ASP.NET Edition v.3.4.1

+ Support for the .NET Standard 2.0 has been made.
! Breaking change: The display of alternate names and other SQL generation
  options for expressions in the user interface is now determined by the
  QueryBuilder.SQLFormattingOptions property (rather than the
  QueryBuilder.SQLGenerationOptions). The QueryBuilder.SQLGenerationOptions
  now influence only on the query text generation returned by the
  QueryBuilder.SQL property.  
- Other minor improvements and bugfixes have been made.

February 15, 2019

Active Query Builder 3 ASP.NET Edition v.3.4.0

+ The new Grid.addExpression method has been added. It accepts string
  expression and a callback function as parameters and puts the newly
  created grid row as a parameter of the callback function.
- The bug with renaming subfolders and queries in them has been fixed.
- The bug the grid.scrollToTop, scrollToBottom methods which caused 
  unwanted scrolling of the grid on deleting a row has been fixed.
= The obsolete property UseDefaultTheme has been removed.

February 06, 2019

Active Query Builder 3 ASP.NET Edition v.3.3.7

- Search in the Database Schema Tree if alternate names are defined and
  visible is performed correctly now.
- The BehaviorOptions.LinkManipulations property now works as it should.
- Turning off grouping in the query via the global Grouping checkbox in the
  header of Query Columns List may lead to inconsistent queries. Fixed now.

Product Summary

 Active Query Builder WinForms .NET Edition:

 Active Query Builder WPF .NET Edition:

 Active Query Builder ASP.NET Edition:

 Active Query Builder Java Edition:

 Active Query Builder ActiveX Edition:

 Active Query Builder VCL Edition:



We have been using Active Query Builder for over a year and must say that both the product and support have been outstanding!

We chose Active Query Builder due to its flexibility and features, but have been truly pleased by its power and hidden capabilities. ...

In summary Active Query Builder provides excellent components, great support and a very flexible feature set. It has allowed us to provide features to our end users that I did not think would be possible in the first release of our new tools and in a timeframe that was much shorter than planned. I would recommend that anyone dealing with databases in the .Net world should be aware of this component and its capabilities!

Social networks