3-5 Key Concepts

[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!

[Scott M.]

1. Understand what the CLR is and how it manages code.
2. Understand OOP and the related concepts
3. Understand how .NET memory management works (Garbage Collection, Dispose
& Finalize, etc.)
"Robert" <[e-mail]> wrote in message
news:um*************@tk2msftngp13.phx.gbl...

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!

[Kevin Spencer]

1. Object-Oriented Programming Principles
2. System.Web.UI.Control - All ASP.Net UI elements (including Page) inherit
this.
3.HTML
4. HTTP
5. Solid Programming practices

Most of the problems I see in this newsgroup are related to a lack of
understanding of one or more of these concepts. I have them listed in order
of importance (IMHO).

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

"Robert" <[e-mail]> wrote in message
news:um*************@tk2msftngp13.phx.gbl...

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!

[Shan Plourde]

I would recommend that the next step to becoming an ASP.NET guru would
be to understand:
- HTTP Request Processing lifecycle
- Many topics at
http://msdn.microsoft.com/asp.net/us...b/default.aspx.

I've always found it much easier to find the "bottom up" style Microsoft
help rather than the "top down". That link above has a lot of top down,
higher level stuff that hopefully can help you.

Shan

Robert wrote:

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!