R
Robert
I've been working with ASP.NET for about a year and I think I'm on the verge
of "getting it." I suspect that if I came to understand a few key concepts
it would all come together. One of those "key concepts" undoubtedly is the
"pipeline" I see mentioned over and over again in this group. If one were to
understand that, then the relationships amongst HTTP handlers, output
caching, the Cache object, and order of page construction, etc would
hopefully become obvious.
So, from those of you who have a outstanding knowledge of ASP.NET (MVPs
listening?), what would you say are a few key concepts that, if understood,
would go a long way toward "making it all come together" for someone
learning ASP.NET?
Please note that I'm not looking to solve any particular application
problem - I'm after a general and thorough understanding of ASP.NET, and
believe that while this "universe" might have a lot going on in it, it still
has a limited scope.
Thanks!
of "getting it." I suspect that if I came to understand a few key concepts
it would all come together. One of those "key concepts" undoubtedly is the
"pipeline" I see mentioned over and over again in this group. If one were to
understand that, then the relationships amongst HTTP handlers, output
caching, the Cache object, and order of page construction, etc would
hopefully become obvious.
So, from those of you who have a outstanding knowledge of ASP.NET (MVPs
listening?), what would you say are a few key concepts that, if understood,
would go a long way toward "making it all come together" for someone
learning ASP.NET?
Please note that I'm not looking to solve any particular application
problem - I'm after a general and thorough understanding of ASP.NET, and
believe that while this "universe" might have a lot going on in it, it still
has a limited scope.
Thanks!