1. What is [Link]?
[Link] is a server-side technology used for developing dynamic websites and web
applications on the internet.
Microsoft released [Link] in 2002 to build dynamic websites and web applications
using the .NET framework.
2. What platform does [Link] use?
[Link] is a cross-platform which works on the .NET framework and runs on Linux,
Windows, macOS, and Docker.
3. What is the [Link] Life Cycle, and list the types of Life Cycle?
When [Link] pages run, it goes through several steps of the life cycle, which
performs a series of actions like initialization, running, restoring, and
rendering.
Life Cycle is classified into two categories.
Application Life Cycle: The user requests for accessing the application.
Page Life Cycle: Page Life Cycle has phases like initialization, restoring,
execution, and page rendering.
The [Link] life cycle is like the journey of a web page from the moment you
request it in your browser to when it's displayed on your screen. In simple words,
here's what happens:
1. **Initialization**: When you type a web address and hit Enter, the request
reaches the web server. [Link] starts by initializing the page and its components.
2. **Page Request**: [Link] figures out which page you're trying to access and
loads it. It's like opening a book to the right chapter.
3. **Page Loading**: The page loads its controls and their properties. This is like
preparing all the ingredients for a recipe.
4. **Page Postback or Callback**: If you click a button or interact with the page,
it might send data back to the server. This is called a postback or callback. It's
like filling out a form and sending it to someone.
5. **Page Validation**: The server checks if the data you sent is valid and safe.
It's like ensuring that the form you sent is correctly filled and not malicious.
6. **Page Processing**: The server processes your request. For example, if you
requested a search, it searches the database. It's like the chef following the
recipe.
7. **Rendering**: Once the server is done, it creates the HTML and other code that
your browser understands. This is like plating your dish nicely before serving it.
8. **Page Unload**: After sending the web page to your browser, [Link] cleans up
and prepares for the next request. It's like cleaning the kitchen after cooking.
9. **Response**: The server sends the page to your browser, and your browser
displays it on your screen. It's like receiving your meal and enjoying it.
10. **Post-Back Handling**: If you interact with the page again, the process can
repeat from step 4.