Create Reusable Templates and Skins in ASP.NET

摘要

As you've seen, templates and skinning really don't take much work to set up and are easy to customize. I challenge you to take what I've discussed in this article further. You can include style sheets for each skin or maybe even implement caching, so each skin comes from the cache instead of being loaded dynamically. It's a good idea to make it even more dynamic. Have the list of available skins come from a database instead of being hardcoded, and as I mentioned before, have all template.ascx files inherit from a single BaseSkin class. With the announcement of Whidbey (the next version of Visual Studio), ASP.NET has a new feature called Master Pages that is the ultimate template system. It's a great feature and definitely worth looking at for the future. Because Whidbey won't be released until late 2004, the topics discussed in this article are very pertinent and useful. You can organize templates and skins in ASP.NET to make organized, reusable, and maintainable Web applications, as well as save time building the look of new Web applications.