Applied XML Programming for Microsoft .NET.pdf - Csbdu.in

}}menuTools.MenuItems.Add(index, mnuItem);index += 1;The DataSet object that the section handler returns is built from the XML code rooted in. This code originates a DataSet object with one table, named MenuTools.The MenuTools table has three columns: Text, Assembly, and Class. Each row in thetable corresponds to a plug-in module.The preceding code first adds a separator and then iterates on the rows of the tableand adds menu items to the Tools menu, as shown in Figure 15-3. MenuTools is justthe name of the Tools pop-up menu in the sample application.Figure 15-3: Registered plug-in modules appear on the Tools menu of the application.To handle a click on a menu item in a Windows Forms application, you need toassociate an event handler object with the menu item. Visual Studio .NET does this foryou at design time for static menu items. For dynamic items, this association must beestablished at run time, as shown here:DynamicMenuItem mnuItem;mnuItem = new DynamicMenuItem(configMenuItem["Text"].ToString(),new EventHandler(StdOnClickHandler));A menu item is normally represented by an instance of the MenuItem class. What isthat DynamicMenuItem class all about then? DynamicMenuItem is a user-defined classthat extends MenuItem with a couple of properties particularly suited for menu itemsthat represent calls to plug-in modules. Here's the class definition:public class DynamicMenuItem: MenuItem{public string AssemblyName;public string ClassName;public DynamicMenuItem(string text, EventHandler onClick):base(text, onClick){}}526