Active Query Builder support area

Migration wizard?

Avatar
Jonathan Sion
  • updated
  • Completed

Hello,

I just upgraded from v2 to v3. is there any sort of 'migration wizard' on my project, or do i have to start everything from scratch? You got this article http://feedback.activequerybuilder.com/topics/90-active-query-builder-3-migration-guide/ which just talks about replacing DLL references. that's fine, but it also means rebuilding all my forms from scratch. do you have anything that just takes my project and makes all the controls there v3? (just like devepress migration wizard, or any other .net 3rd party provider) Thanks!

Replies 5
Avatar
0
Andrey Zavyalov, PM

Hello, Yonatan.

Thank you for your continuous interest in Active Query Builder.

There is no migration wizard from the version 2 to 3. We strove to make props and methods of the QueryBuilder component as close as possible, but changes were necessary as we've changed the architecture significantly.

You are right. You have to remade the form containing Active Query Builder. This shouldn't be very hard if you want to continue using it as a single control, but I recommend you to explore the possibilities of the separated controls mode. It lets customize the user interface the way you want.

As always, feel free to contact me with any questions you may have.

Avatar
0
Jonathan Sion

Hi Sergey

So I guess the best place to start is here?

http://feedback.activequerybuilder.com/forums/5-active-query-builder-programmers-guide/categories/68-quick-start-guides/topics/

This 'separate control mode' that you recommend - is all a lot more effort than single control? if not, i'll go for it, following your recommendation. I assume I should start here? http://feedback.activequerybuilder.com/topics/59-getting-started-with-aqbnet-3-in-the-separated-controls-ui-or-non-visual-mode/


also: in the 2.0 version there was some extra code that I needed to put in. some of it for multi threading operation so that the control will be responsive while it loads data. I guess the best thing now would be to just remove all that, and start with a totally clean form? Because it seems (from the demo) that 3.0 loads metadata much faster and doesnt require all that. am I right?


Thanks

Avatar
0
Jonathan Sion

Ok. So I got the basic form working. The loading of Meta Data (by that i mean database schema) seems super fast now and there's no need for all the threading code that I had before. 2 things now:

1. the loading of meta data is still a bit slow... i mean 5 seconds or so. any way to skip that? meaning just load the form first and then launch the loading on a separate thread or something, to be sure the GUI is interactive?

2. in the old version there used to be this thing called a 'syntax provider'. do I not need it anymore?


and oh: 3. the link i sent you eallier for documentation - that is the main documentation? is that where i start from?


Thanks again!

Jonathan

Avatar
0
Andrey Zavyalov, PM

Hello,

You're right. These articles can be helpful.

I don't think that the Separate Controls mode is all a lot more effort than single control. The main question is how you can benefit from it. If you're totally satisfied with the composition of the query building UI that you had in the previous version, possibly you don't need it. If you want to reorganinze the interface, the Separate Controls mode is what you need.

You can post this code here so we will be able to examine it and let you know if it's useful now or not.

Avatar
0
Andrey Zavyalov, PM

1. Currently Active Query Builder only loads objects that need to be displayed in the database schema view. If the tree is collapsed, the component only needs to load the root nodes. Set the QueryBuilder.DatabaseSchemaViewOptions.DefaultExpandLevel to 0 to make loading as fast as possible. Another reason of this delay might be caused by loading the necessary metadata to display the initial SQL query (if it's loaded on start). You can speed up the component loading in this case by setting the QueryBuilder.MetadataLoadingOptions.DisableAutomaticMetadataLoading property to True. Note that doing so has some side effects, you can read about them in remarks.

2. Syntax provider is still necessary. The component can not start without it. You can read about it in this article: What are the Syntax and Metadata providers for?

3. No, this is just a set of the 'Getting started' guides. However they might be helpful in the beginning. I recommend you to start from this link: https://support.activequerybuilder.com/hc/en-us/ We'll be moving to this support portal soon.
Please refer to the "Common Information" and "Active Query Builder for .NET" sections.