Previous versions of Iron Speed Designer created one generic table and one generic record control class for all table and record control objects in the page. The generic table and record control classes were called “CustomTableControl” and “CustomRecordControl” respectively. Iron Speed Designer V3.0 creates specific table and record control classes for each table and record control in the page. This gives you more specific control and access when writing code customizations.
Additionally, each record and table control class defines properties for their respective child controls, eliminating the need to use the FindControl function to access child controls. The following table shows the new and old classes created for a list of record control in a page.
|
Objects in Page |
|
OrdersRecordControl OrdersTableControl OrdersDetailsRecordControl OrderDetailsTableControl |
|
Old Classes |
New Classes |
|
CustomTableControl CustomRecordControl |
OrdersRecordControl OrdersTableControl OrdersTableControlRecordControl OrderDetailsRecordControl OrderDetailsTableControl OrderDetailsTableControlRecordControl |
During migration, no changes will be made to your “safe” class files. By policy, Iron Speed Designer does not modify your safe class files.
You should move existing code customizations from the generic record and table control classes into their specific classes. For example, if you have a code customization for the OrdersRecordControl in the CustomRecordControl class, you should move the code customization into the OrdersRecordControl class. If you have multiple record controls you need to move the customization to the appropriate specific record control class.
(Optional) If OrdersRecordControl has a PriceLabel child control, a property called PriceLabel will be available in the specific record control class. As a result, you do not need to use the FindControl function to access the PriceLabel control; instead, you can directly refer to the property. Using these new properties is optional.