KEMBAR78
Introduction to 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
 Client Side Scripting
 Server Side Scripting
 HTML
 JavaScript
 CSS
 JQuery
 Ajax
 XML
 Separate Code & Design
 Rich Web Forms
 Drag & Drop Design
 Like WinForms
 Page Directive
 Server side code
 Form
 Normal HTML Structure
 Server Controls
PreInit Init
Init
Complete
PreLoad
Load
Control
events
Load
Complete
Pre
Render
Save
StateComplete
Render Unload
 Post Back
 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
 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.
 Template to Other pages
 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
 Web Application
 Recommended
 Compiles all pages into one DLL
 Faster on first load after deployment
 Must recompile whole site for code change
Introduction to asp .net

Introduction to asp .net

  • 2.
     Simply Serverside 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
  • 4.
     Client SideScripting  Server Side Scripting  HTML  JavaScript  CSS  JQuery  Ajax  XML
  • 5.
     Separate Code& Design  Rich Web Forms  Drag & Drop Design  Like WinForms
  • 6.
     Page Directive Server side code  Form  Normal HTML Structure  Server Controls
  • 7.
  • 8.
     Post Back 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.
     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.
     Template toOther pages
  • 11.
     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.
     Web Application Recommended  Compiles all pages into one DLL  Faster on first load after deployment  Must recompile whole site for code change