Hello lander,
I recommend you to use .NET Reflector
http://www.aisto.com/roeder/dotnet/
to check what happens inside these methods
---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog:
http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
lI've read the page life cycle thing in msdn, still, i'm getting a bit
lconfused of thinking how all the things are going under the hood...
l>
lI know that when page loading, that the controls' properties is
lpopulated and when page unloading, the resources are cleared.
l>
lWhat I want to know is what's happening behind it, that is, from the
lperspective of the asp.net implementor.....I'm not sure whether i've
lstated clearly, hope you get it.
l>
lAnd, as for page life cycle. Does it mean that a request comes in a
lpage object and a HTTPContext object is contructed for the request,
lwhen the request has been processed, the page object is destroyed as
lwell as all other resources......I'm not very sure of it...
l>
lThanks for your attention...
l>
