I’m in the process of learning about ASP.NET master pages and themes support. I’m trying to incorporate runtime switching of themes on the master page, and what seems to be a pattern in my learning process occurred again.
What I’m finding is that when I’m having a hard time understanding what’s going on in a partucular "problem space", it’s time to dig a little deeper and first understand the underlying architecture.
There are many approaches to learning software architectures, but I’n my case using UML class and other diagrams always seems to do the job.
So, here we go. The following UML class diagram show the classes involved with loading an ASPX page:
The diagram is not intended to be 100% correct or cover all related classes and relationships. Instead, the purpose is to communicate to me (and hopefully you) something that helps me remember how ASP.NET works.
Tor Langlo 