ASP.NET Themes
What are ASP.NET 2.0 Themes?
One of the most important aspects of a Web application is a consistent look and feel across the site. ASP.NET 1.x developers usually use Cascading Style Sheets (CSS) to implement a consistent look and feel. ASP.NET 2.0 themes significantly improve upon CSS because they give the ASP.NET developer the ability to define the appearance of ASP.NET server controls as well as HTML elements. ASP.NET themes can be applied to individual controls, a specific Web page, or an entire Web application. Themes use a combination of CSS files, an optional skin file, and an optional Images directory if images are needed. The skin file controls the visual appearance of ASP.NET server controls.
Where are Themes Stored?
The location where themes are stored differs based upon their scope. Themes that can be applied to any application are stored in the following folder:
C:\WINDOWS\Microsoft.NET\Framework\v2.x.xxxxx\ASP.NETClientFiles\Themes\
A theme that is specific to a particular application is stored in an App_Themes\
Note: A skin file should only modify server control properties that affect appearance.
A global theme is a theme that can be applied to any application or Web site running on the Web server. These themes are stored by default in the ASP.NETClientfiles\Themes directory that is inside of the v2.x.xxxxx directory. Alternatively, you can move the theme files into the aspnet_client/system_web/[version]/Themes/[theme_name] folder in the root of your Web site.
Application-specific themes can only be applied to the application in which the files reside. These files are stored in the App_Themes/
The Components of a Theme
A theme is made up of one or more CSS files, an optional skin file, and an optional Images folder. The CSS files can be any name you wish (i.e. default.css or theme.css, etc.) and must be in the root of the themes folder. The CSS files are used to define ordinary CSS classes and attributes for specific selectors. To apply one of the CSS classes to a page element, the CSSClass property is used.
The skin file is an XML file that contains property definitions for ASP.NET server controls. The code listed below is an example skin file.
<asp:TextBox runat="server"
BackColor="#FFC080"
BorderColor="Black"
BorderStyle="Solid"
BorderWidth="1px"
Font-Names="Tahoma, Verdana, Arial"
Font-Size="Smaller" />
<asp:Button runat="server"
BackColor="#C04000"
BorderColor="Maroon"
BorderStyle="Solid"
BorderWidth="2px"
Font-Names="Tahoma,Verdana,Arial"
Font-Size="Smaller"
ForeColor="#FFFFC0" />
Figure 1 below shows a small ASP.NET page browsed without a theme applied. Figure 2 shows the same file with a theme applied. The background color and text color are configured via a CSS file. The appearance of the button and textbox are configured using the skin file listed above.
Figure 1: No Theme
Figure 2: Theme Applied
The skin file listed above defines a default skin for all TextBox controls and Button controls. That means that every TextBox control and Button control inserted on a page will take on this appearance. You can also define a skin that can be applied to specific instances of these controls using the SkinID property of the control.
The code below defines a skin for a Button control. Only Button controls with a SkinID property of goButton will take on the appearance of the skin.
<asp:Button runat="server"
BackColor="#C04000"
BorderColor="Maroon"
BorderStyle="Solid"
BorderWidth="2px"
Font-Names="Tahoma,Verdana,Arial"
Font-Size="Smaller"
ForeColor="#FFFFC0"
Text=go
SkinID=goButton
Width="95px" />
You can only have one default skin per server control type. If you require additional skins, you should use the SkinID property.
Applying Themes to Pages
A theme can be applied using any one of the following methods:
* In the
* In the @Page directive of a page
* Programmatically
Applying a Theme in the Configuration File
To apply a theme in the applications configuration file, use the following syntax:
<system.web>
<pages theme="CoolTheme" />
...
</system.web>
The theme name specified here must match the name of the themes folder. This folder can exist either in any one of the locations mentioned earlier in this course. If you attempt to apply a theme that doesn't exist, a configuration error will occur.
Applying a Theme in the Page Directive
You can also apply a theme in the @ Page directive. This method allows you to use a theme for a specific page.
To apply a theme in the @Page directive, use the following syntax:
<%@ Page Language="C#" Theme=CoolTheme CodeFile="Default.aspx.cs" ... %>
Once again, the theme specified here must match the theme folder as mentioned previously. If you attempt to apply a theme that doesn't exist, a build failure will occur. Visual Studio will also highlight the attribute and notify you that no such theme exists.
Applying a Theme Programmatically
To apply a theme programmatically, you must specify the Theme property for the page in the Page_PreInit method.
To apply a theme programmatically, use the following syntax:
Page.Theme = CoolTheme;It is necessary to apply the theme in the PreInit method due to the page lifecycle. If you apply it after that point, the pages theme will have already been applied by the runtime and a change at that point is too late in the lifecycle. If you apply a theme that doesn't exist, an HttpException occurs. When a theme is applied programmatically, a build warning will occur if any server controls have a SkinID property specified. This warning is intended to inform you that no theme is declaratively applied and it can be ignored.
Exercise 1 : Applying a Theme
In this exercise, you will apply an ASP.NET theme to a Web site.
IMPORTANT: If you are using Microsoft Word to enter information into a skin file, make sure that you are not replacing regular quotes with smart quotes. Smart quotes will cause problems with skin files.
- Create a new ASP.NET Web site.
- Right-click on the project in Solution Explorer and choose Add New Item.
- Choose Web Configuration File from the list of files and click Add.
- Right-click on the project in Solution Explorer and choose Add New Item.
- Choose Skin File and click Add.
- Click Yes when asked if youd like to place the file inside of the App_Themes folder.
- Right-click on the SkinFile folder inside of the App_Themes folder in Solution Explorer and choose Add New Item.
- Choose Style Sheet from the list of files and click Add. You now have all of the files necessary to implement your new theme. However, Visual Studio has named your themes folder SkinFile. Right-click on that folder and change the name to CoolTheme.
- Open the SkinFile.skin file and add the following code the end of the file:
<asp:TextBox runat="server"
BackColor="#FFC080"
BorderColor="Black"
BorderStyle="Solid"
BorderWidth="1px"
Font-Names="Tahoma, Verdana, Arial"
Font-Size="Smaller"
/>
<asp:Button runat="server"
BackColor="#C04000"
BorderColor="Maroon"
BorderStyle="Solid"
BorderWidth="2px"
Font-Names="Tahoma,Verdana,Arial"
Font-Size="Smaller"
ForeColor="#FFFFC0"
/>
<asp:Button runat="server"
BackColor="#C04000"
BorderColor="Maroon"
BorderStyle="Solid"
BorderWidth="2px"
Font-Names="Tahoma,Verdana,Arial"
Font-Size="Smaller"
ForeColor="#FFFFC0"
Text="go"
SkinID="goButton"
Width="95px"
/>
10. Save the SkinFile.skin file.
11. Open the StyleSheet.css.
12. Replace all of the text in it with the following:
body {
background-color: #FFDEAD;
}
- Save the StyleSheet.css file.
- Open the Default.aspx page.
- Add a TextBox control and a Button control.
- Save the page. Now browse the Default.aspx page. It should display as a normal Web form.
- Open the web.config file.
- Add the following directly underneath the opening
<system.web>
tag:
<pages theme="CoolTheme" />
19. Save the web.config file. Now browse the Default.aspx page. It should display with the theme applied.
20. If it's not already open, open the Default.aspx page in Visual Studio.
21. Select the Button.
22. Change the SkinID property to goButton. Notice that Visual Studio provides a dropdown with valid SkinID values for a Button control.
23. Save the page. Now preview the page in your browser again. The Button should now say "go" and should be wider in appearance.
Using the SkinID property, you can easily configure different skins for different instances of a particular type of server control.
The StyleSheetTheme Property
So far, we've talked only about applying themes using the Theme property. When using the Theme property, the skin file will override any declarative settings for server controls. For example, in exercise 1, you specified a SkinID of "goButton" for the Button control and that changed the Button's text to "go". You may have noticed that the Text property of the Button in the designer was set to "Button", but the theme overrode that. The theme will always override any property settings in the designer.
If you'd like to be able to override the properties defined in the theme's skin file with properties specified in the designer, you can use the StyleSheetTheme property instead of the Theme property. The StyleSheetTheme property is the same as the Theme property except that it does not override all explicit property settings like the Theme property does.
To see this in action, open the web.config file from the project in exercise 1 and change the
<pages styleSheetTheme="CoolTheme" />
Now browse the Default.aspx page and you'll see that the Button control has a Text property of "Button" again. That's because the explicit property setting in the designer is overriding the Text property set by the goButton SkinID.
Overriding Themes
A global theme can be overridden by applying a theme by the same name in the App_Themes folder of the application. However, the theme is not applied in a true override scenario. If the runtime encounters theme files in the App_Themes folder, it will apply the theme using those files and will ignore the global theme.
The StyleSheetTheme property is overridable and can be overridden in code as follows:
const String THEME_NAME = "CoolTheme";
public override string StyleSheetTheme {
get { return THEME_NAME; }
set { Page.StyleSheetTheme = THEME_NAME; }
}