|
Iron Speed Designer creates a sub-class of the .NET Framework Page class and uses it as the class
from which all generated pages are derived.
 | All Page classes in your application derive from the BasePage class. |
The BasePage extends the default Page class of the Microsoft .NET Framework classes. All ASPX
files created by Iron Speed Designer are derived from the BasePage class.
The application classes extend the .NET Framework to support applications generated by Iron Speed
Designer. Applications generated by Iron Speed Designer use classes inherited from other application
classes and .NET Framework classes.
 | Application classes are generally derived from .NET Framework classes. |
For example, the default page class used by .NET is System.Web.UI.Page. This class is sub-classed
in application classes as BasePage. Applications use this class to generate individual pages.
The purpose of application classes is twofold. First, application classes provide extensions to the
Microsoft .NET Framework to deliver additional functionality. Second, they enable you to add features
that apply to the entire application by making changes to these classes.
Iron Speed Designer makes use of Base Application Page (part of Generated Application Classes) as a base
to every page generated in the application. This allows a user to write more generic code in the Base
Application Page instead of repeating the code on every page.
The Base Application Page exists under the shared folder in the App_Code folder for each Iron Speed
Designer application.

The advantages are obvious: you only have to write the code in one place, and every page inherits it
automatically. Iron Speed Designer Code Customization “Application Wide Page Security” generates the
code in a Base Application Page, which in turn makes every page check for security. Thus, even if you
create 1000 pages in your application, your security is checked at one place. It is possible to
implement your custom security model for each page with some metadata configuration.
|