This document provides an introduction to ASP.NET development. It outlines that ASP.NET is a server-side language that uses a simplified page development model and modular, extensible architecture. It also discusses ASP.NET features like superior debugging, rich caching support, scalable session state, and error recovery. The document then covers request and response processing, common technologies used like HTML and JavaScript, and how ASP.NET web forms separate code from design and use server controls like Windows forms. It explains the ASP.NET page lifecycle and concepts like postbacks and view state. It concludes by discussing using session state and application state to store object data and how to start ASP.NET development using web sites versus web applications.

1. Introduction to
ASP.NET
development
http://melick-
rajee.blogspot.com/

2. Asp.NET ?
 Simply Server side language
 Simplified page development model
 Modular, well-factored, extensible architecture
 Superior debugging and tracing support
 Compiled, not interpreted
 Rich caching support
 Web farm scalable session state
 Automatically detects and recovers from errors

3. Request And Respond

4. General Things to know
 ClientSide Scripting
 Server Side Scripting
 HTML
 JavaScript
 CSS
 JQuery
 Ajax
 XML

5. Web Forms in .NET
 Separate Code & Design
 Rich Web Forms
 Drag & Drop Design
 Like WinForms

6. Understand the Web Form
 Page Directive
 Server side code
 Form
 Normal HTML Structure
 Server Controls

7. Page Life Cycle
Init
PreInit Init PreLoad
Complete
Pre Load Control
Load
Render Complete events
Save
Render Unload
StateComplete

8. You must Know
 PostBack
 communicates back to the server
 View State
 state stored in a hidden field on the page
 transported to the client and back to the server,
 Is not stored on the server

9. ASP.NET States
 Session State
 allows the state of objects (serializable) to
be stored for a single session (lifetime of the
user’s browser or specific timeout)
 Application State
 allows the state of objects (serializable) to
be stored for the application across
different sessions.

10. Master Page
 Template to Other pages

11. Starting ASP.NET Development
 Web Site
 Don’t use this, here for compatibility only
 Each page is dynamically loaded into
memory
 Slow on first load after deployment
 No need to recompile for code change

12. Starting ASP.NET Development
..
 Web Application
 Recommended
 Compiles all pages into one DLL
 Faster on first load after deployment
 Must recompile whole site for code change

13. Thank You!