Downloads » Active Query Builder 2 ASP.NET Edition History
Below is the list of fixes and improvements in Active Query Builder 2 ASP.NET Edition v.2.13.5.
= MVC: The QueryBuilderControl.Init event can be replaced now with the Init method in inheritor of the new InitializeQueryBuilderAttribute attribute applied to the controller method. All of the MVC demo projects are updated according to this change. = The HttpCompressionEnabled and MultipleQueriesPerSession properties of the QueryBuilderControl have been replaced with respective 'web.config' file options and marked as obsolete. The syntax for these options: <appSettings><add key="MultipleQueriesPerSession" value="True" /> + The new delegates have been added to the SessionStoreItem: BeforeSqlParsing, AfterSqlGeneration. They allow to perform pre- and post-processing of the SQL query text. The BeforeSqlParsing lets abort the parsing and return an error message to end-user. + The new demo projects have been made to illustrate changing of connection in runtime. - The bug with the Linked Objects menu not adding new links to already existing objects, even if they utilize different relationships has been fixed.
[ Legend: ] [ + New feature ] [ = Improved/changed feature ] [ - Bug fix ] [ ! Important notice ]
You can always get the latest trial version of Active Query Builder 2 ASP.NET Edition at the download page.
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!