CS 233S: Web Application Development II	Name:	
Assignment #4 Consistent UI Tools: Master Pages & Themes	Date Due:	

In this fourth assignment, you will explore the tools available through ASP.NET that allow developers to create a consistent user interface look and feel for their projects. Master pages act as programmatically accessible page templates, while themes combine images, CSS, and custom designs for ASP.NET web server controls not directly available to CSS formatting.
Part A: Text Reading	50 points
1.	Read Chapters 5 and 6 in the textbook. Read all of the pages – you are responsible for the knowledge in each section, even if you are not required to complete the coding. Follow the VB or C# directions for:
•	Page 224, Listing 5-1: create the file shown, using your last name in the filename (e.g carino.master).
•	Page 226, Listing 5-2: create the file shown, using chap5page1.aspx as the name of the file and selecting the master page created in Listing 5-1 as the master page.
•	Page 228, Listing 5-3: modify chap5page1.aspx; add the server-side script shown as well as the HTML tags and web server controls inside each content area.
•	Page 230, Listing 5-4: create a second file named chap5page2.aspx as shown; use the code behind model.
•	Page 231, Listing 5-5: modify the web.config file.
•	Page 232, Listing 5-6: modify the web.config file.
•	Page 232. Listing 5-7: modify chap5page1.aspx; add the Page_LoadComplete event procedure
•	Page 233, Listing 5-8: modify the yourlastname.master file; add the Page_Load event and an ASP label.
•	Page 234, Listing 5-9: modify chap5page1.aspx; add the Label1.Text assignment to the existing Page_LoadComplete event procedure
•	Page 240. Listing 5-14: modify yourlastname.master; add the default content shown
•	Page 240, Listing 5-15: create a new file named chap5page3.aspx based on the master page
•	Page 243, Listing 5-17: create the ReutersMain.master file shown
•	Page 244, Listing 5-18: create the ReutersEurope.master file shown
•	Page 259, Listing 6-3: add the App_Themes folder and Summer subfolder. Create a new file named summer.skin in the appropriate directory as shown
•	Page 259, Listing 6-4: create a chap6page1.aspx file as shown.
•	Page 262, Listing 6-5: create the summer.css file inside of the App_Themes/Summer directory. (Be sure to view chap6page1.aspx in the browser after this step to see any effect of adding CSS to theme folder.)
•	Page 266, Listing 6-8: modify summer.css; add the CSS declarations shown
•	Page 266, Listing 6-9: modify summer.skin and chap6page1.aspx; add the asp:calendar definition shown, add the images to the images folder, and add a calendar control to chap6page1.aspx
•	Page 268, Listing 6-10: modify summer.skin; add the additional highlighted asp:textbox definitions
•	Page 268, Listing 6-11: modify chap6page1.aspx; add the additional TextBox1 and TextBox2 controls
2.	Email or print the code view (including the code behind the page as needed) from:
•	
•	Yourlastname.master
•	Chap5page1.aspx
•	Chap5page2.aspx
•	Chap5page3.aspx
•	Web.config
•	ReutersMain.master
•	ReutersEurope.master
•	Summer.skin
•	Summer.css
•	Chap6page1.aspx

Part B: On Your Own	50 points
1.	Build a consistent user interface for your project site including: 
a.	A master page that contains elements common to all pages within the site (Header? Footer? Navigation?) and at least two different content areas.
b.	At least one theme that includes:
i.	 a .skin file with a definition for at least 3 different ASP web server controls.
ii.	a .css file with a definition for at least 6 different elements, one of which should be an element that is created from a web server control. (you could choose, for example, to use CSS to format input boxes with a type=”text” attribute; the control should be created on the HTML page both by a “normal” input tag and by the rendered version of the asp:textbox web server control.
c.	An .aspx page that:
i.	Uses the master page created in step (a).
ii.	Uses the theme created in step (b) for the vast majority of the page.
iii.	The 3 ASP web server controls from your .skin file in a meaningful way.
iv.	Contains at least one element that does not use the applied theme.
v.	Enough other content to make to purpose of the page clearly understandable.
2.	Email or print the code view of the .master, .skin, and .css files and the code and browser view of your .aspx file as well as any associated code-behind files.