Using the Domain Model

Here is the corresponding ASPX.CS template. The number of using statements to import namespaces has been reduced for clarity:

TemplatePage.aspx.cs using System; public partial class

{0}

: System.Web.UI.Page {{

{1}

}}

Now that you have your templates, you need to write the code that will iterate through all of the pages in the domain model and generate the physical implementations . As you create pages, you also need to create buttons on the pages to demonstrate the navigation defined in the domain model, so you have some boilerplate button definitions, which you use to simplify insertion of these buttons into the page code.

The code shown retrieves a collection of all the Pages in your domain model and iterates through each one in turn . You then load the templates into a string so you can replace the tokens with the page-specific information.

For each page, you then obtain any child Pages referenced by the Page and construct a button for each one, enabling the user to navigate to them. You also generate the code-behind file that performs the transfer between pages using Response.Redirect .

You then replace any tokens in the two files with the page-specific information and then output the text for the pages to disk. Following its execution, you will see .ASPX and .ASPX.cs files generated:

const string ButtonDefinition = "<asp:Button ID=\"{0}\" runat=\"server\" Text=\"{0}\" OnClick=\"{0}_Click\" />"; const string ButtonCodeDefinition = "protected void {0}_Click(object sender, EventArgs e)\r\n{{\r\n{1}\r\n}}"; IList MELPages = this.Store.ElementDirectory.GetElements(DomainModel.Page.MetaClassGuid); foreach (DomainModel.Page MELPage in MELPages) { //Read the ASP.NET Page Templates into a string so we can customise. StreamReader ASPXTemplatePageReader = new StreamReader("TemplatePage.aspx"); string TemplateASPXPage = ASPXTemplatePageReader.ReadToEnd(); StreamReader CodeTemplatePageReader = new StreamReader("TemplatePage.aspx.cs"); string TemplateCodePage = CodeTemplatePageReader.ReadToEnd(); //We loop around any Child Pages and provide buttons on the ASP.NET Page and //Code Behind handlers to move to the child pages StringBuilder ASPXButtonDefinitions = new StringBuilder(); StringBuilder CodeButtonDefinitions = new StringBuilder(); foreach (DomainModel.Page MELChildPage in MELPage.ChildPages) { //Variable and type names cannot have spaces so we remove string CollapsedChildName = MELChildPage.

Name

.Replace(" ", ""); //Create a new ASP.NET Button ASPXButtonDefinitions.Append( String.Format(ButtonDefinition, CollapsedChildName) ); //Create the Code behind for the button string NavigationCode = String.Format( "Response.Redirect(\"{0}.aspx\");", CollapsedChildName ); CodeButtonDefinitions.Append(String.Format(ButtonCodeDefinition, CollapsedChildName, NavigationCode ) ); } //Variable and type

names

cannot have spaces so we remove string CollapsedName = MELPage.Name.Replace(" ", ""); //Our page templates have the areas that need //to change for each page replaced with tokens which we now fill in. string OutputASPXPage = String.Format(TemplateASPXPage, CollapsedName, MELPage.Name, ASPXButtonDefinitions.ToString() ); string OutputCodePage = String.Format(TemplateCodePage, CollapsedName, CodeButtonDefinitions.ToString() ); using (StreamWriter ASPXPageWriter = new StreamWriter( CollapsedName + ".aspx" ) ) { ASPXPageWriter.Write(OutputASPXPage); } using (StreamWriter ASPXPageWriter = new StreamWriter( CollapsedName + ".aspx.cs" ) ) { ASPXPageWriter.Write(OutputCodePage); } }

If you then copy these files into a new ASP.NET website and navigate to Logon.aspx, you should see the logon page as defined in the language model appear as shown in Figure 6-17.

Figure 6-17

Clicking one of the buttons will enable you to navigate to the page as defined in the language model. For example, clicking ViewStatement will take you to the View Statement page (shown in Figure 6-18), which only has a link to the Signoff page.

Figure 6-18