ASP.NET Lecture 1

Editor's Notes

1. Difference between dynamic and static sites
2. Web Pages ASP.NET Web Pages and the new Razor syntax provide a fast, approachable, and lightweight way to combine server code with HTML to create dynamic web content. Connect to databases, add video, link to social networking sites, and include many more features that let you create beautiful sites using the latest web standards. MVC ASP.NET MVC gives you a powerful, patterns-based way to build dynamic websites that enables a clean separation of concerns and that gives you full control over markup for enjoyable, agile development. ASP.NET MVC includes many features that enable fast, TDD-friendly development for creating sophisticated applications that use the latest web standards. Web Forms ASP.NET Web Forms lets you build dynamic websites using a familiar drag-and-drop, event-driven model. A design surface and hundreds of controls and components let you rapidly build sophisticated, powerful UI-driven sites with data access.
3. First Hello World Then say HI
4. Default form tag html rendering <form method=“post” action=“samepage.aspx” id=“form”>
5. Default form tag html rendering <form method=“post” action=“samepage.aspx” id=“form”>
6. Separation of Concerns
7. Directives  are commands to the compiler when compiling a page or control <%@ [Directive] [Attribute=Value] %> Page Directive control behaviour of pages
8. ASP.NET is OO so everything is represented with classes and objects The application is starts once the first request to the application and must not be restarted often, except for maintenance. The page is compiled and cached on first request. Each Application has a virtual directory on the web server. ASP.NET is an event-driven way of making web applications. There are: 1- global application events. 2- page related events 3- control related events Note : Eventually, the page is rendered into HTML.
9. AllControls page
10. Viewstate can be encrypted
11. Page Initialization  Fire Page.Init (controls maynot be created and viewstate information isn’t loaded yet) generates all controls defines with tags in .aspx If postbacked  deserialize the viewstate information and apply it to the controls. User Code Initialization  Page.Load fired Validation After Page.Load and before events handling Event Handling  event model is just an emulation Automatic Data Binding  asp.net automatically performs updates and queries against data source controls 1- changes submited 2- Page.PreRender 3- Queries and controls bound Event handlers wont have access to the most recent data, not yet retrieved CleanUp Page.Unload , no change to controls since HTML already rendered
12. PageEvents page
13. To access all HTTP context information from a non-page class, use System.Web.HttpContext class, HttpContext.Current  static property, returns instance of HTTPContext representing all info on current request and response
14. PageControls page DynamicControl page Remember on postback  dynamically created controls won’t be recreated automatically Use unique id to reach it or using recursive search
15. Windows developers are accustomed to a rich event model that lets reacts to mouse movements, key presses and control interaction. In ASP.NET, responding to events are handled by the server. It adds an amount of overhead to respond. Rapid events are impractical. For UI effects, use client-side javascript or Ajax In HTML, there is only one way to submit a form  a submit button AutoPostBack available with web controls only
16. Classical ASP /PHP developer do it manually and write the code themselves
17. PostBackPage page Autopostback page