Explicit MDI Merging:
Calling this method merges the menus and toolbars of the child forms with that of the main form (in an MDI scenario), immediately. The toolbars from the child forms will then be available in the "Toolbars List" for user-customization.
You should call this in either your MDI Parent Form's constructor or Load event handler.
This method is intended to support the following scenario. In an MDI app, you might want the XPMenus framework to merge the child form types's menus and toolbars that the MDI Parent will be parented to during the course of the application, even before the child forms are visible. Doing so will then present a seemless interface to the user with the toolbars and menus from all the different child form types being available for user-customization, all the time.
Also a dummy instance of the child form types will be created at this time to retrieve the bar items, requring the child types to include a default constructor.
Take a look at our User's Guide (section MDI Merging) for more information on how the MergeType, MergeOrder and the Text properties of BarItems influence the merge behavior of those BarItems.
Automatic MDI Merging:
If you do not call this method explicitly with your child form types, the framework will call it for you when a child form (with XPMenus) gets loaded and then automatically unregister (using the UnregisterMdiChildTypes method) the child form type when all the corresponding instances of the child type are closed.
Herewith I have attached the sample for implicit merging. Please refer to this and let me know if this meets your requirements.http://websamples.syncfusion.com/samples/Tools.Windows/F58909/Main.htm
Thanks for using Syncfusion products.