Skip to main content

What is the difference between Pre-Render and Render events in ASP.NET Page?

Pre Render

This event used for modifying server controls just before sending them down to the client”

Allows final changes to the page or its control. This event takes place after all regular PostBack events have taken place. This event takes place before saving ViewState, so any changes made here are saved. For example : After this event, you cannot change any property of a button or change any viewstate value. Because, after this event, SaveStateComplete and Render events are called.


Render

“This event is used to put the HTML output to the response stream”

This is a method of the page object and its controls (and not an event). At this point, ASP.NET calls this method on each of the page’s controls to get its output. The Render method generates the client-side HTML, Dynamic Hypertext Markup Language (DHTML), and script that are necessary to properly display a control at the browser.

For more ASP.NET page life cycle Click Here…

Comments

Post a Comment

Popular posts from this blog

HTTPHandler and HTTPModule in ASP.NET

If you want to implement pre-processing logic before a request hits the IIS resources. For instance you would like to apply security mechanism, URL rewriting, filter something in the request, etc. ASP.NET has provided two types of interception HttpModule and HttpHandler .   The web server examines the file name extension of the requested file, and determines which ISAPI extension should handle the request. Then the request is passed to the appropriate ISAPI extension.  For Example When an .aspx page is requested it is passed to ASP.Net page handler. Then Application domain is created and after that different ASP.Net objects like Httpcontext, HttpRequest, HttpResponse. HTTPModule: -    It's just like a filter. The Modules are called before and after the handler executes . -    HTTP Modules are objects which also participate the pipeline but they work before and after the HTTP Handler does its job, and produce additional serv...

Connected and disconnected architecture in ADO.Net with Example

Connected Architecture of ADO.NET The architecture of ADO.net, in which connection must be opened to access the data retrieved from database is called as connected architecture. Connected architecture was built on the classes connection, command, datareader and transaction.  Connected architecture is when you constantly make trips to the database for any CRUD (Create, Read, Update and Delete) operation you wish to do. This creates more traffic to the database but is normally much faster as you should be doing smaller transactions. Disconnected Architecture in ADO.NET The architecture of ADO.net in which data retrieved from database can be accessed even when connection to database was closed is called as disconnected architecture. Disconnected architecture of ADO.net was built on classes connection, dataadapter, commandbuilder and dataset and dataview. Disconnected architecture is a method of retrieving a r...

Using SQL self join Find Upper level manager in Employee table

A self-join is a query in which a table is joined (compared) to itself. Self-joins are used to compare values in a column with other values in the same column in the same table . You can use a self-join to simplify nested SQL queries where the inner and outer queries reference the same table . These joins allow you to retrieve related records from the same table. The most common case where you'd use a self-join is when you have a table that references itself I have the employee detail table, In that i want to find the manager for each Employee . The employee nam e and manager column are present in same table Consider the following Employee table CREATE TABLE Employee (     Emp_Id INT IDENTITY ( 1 , 1 ) NOT NULL PRIMARY KEY ,     Emp_Name VARCHAR ( 100 ),     Manager_Id INT NULL ) INSERT INTO Employee ( Emp_Name , Manager_Id ) VALUES ( 'a' ,null) INSERT INTO Employee ( Emp_Name , Manager_Id ) ...