1) Page_PreInit 2) Page_Init 3) Page_InitComplete 4) Page_PreLoad 5) Page_Load 6) Page_LoadComplete 7) Page_PreRender 8) Render In ASP.NET, the page life cycle refers to the series of events that occur from the time a page is requested until the time the page is fully rendered and sent to the client browser. Understanding the page life cycle is crucial for developing web applications effectively. Here are the events in the ASP.NET page life cycle: Page Request: The page is requested by…

Read More Read More

Fragment Caching: It caches the portion of the page generated by the request. For that, we can create user controls with the below code: If you want to cache only a portion of a page rather than the entire page in ASP.NET, you would typically use “Partial Page Caching” or “Fragment Caching.” Partial Page Caching allows you to cache specific regions or controls within a page, rather than caching the entire page. This can be useful when certain parts of…

Read More Read More

Caching is a technique used to increase performance by keeping frequently accessed data or files in memory. The request for a cached file/data will be accessed from cache instead of actual location of that file. In the context of ASP.NET, caching refers to the process of storing frequently accessed data in memory temporarily. This allows subsequent requests for the same data to be served more quickly, as the data can be retrieved from the cache rather than being recalculated or…

Read More Read More

Using the Attributes property of server side control. e.g. btnSubmit.Attributes.Add(“onMouseOver”,”JavascriptCode();”) In ASP.NET, you can add an event handler in several ways, depending on the context and the control you’re working with. Here are a few common methods: Using the ASP.NET Markup (Web Forms): In ASP.NET Web Forms, you can define event handlers directly in the markup using the OnEvent attribute. For example: aspxCopy code <asp:Button ID=”btnSubmit” runat=”server” Text=”Submit” OnClick=”btnSubmit_Click” /> In this example, btnSubmit_Click is the name of the event…

Read More Read More

In-Process Out-of-Process. In ASP.NET, there are several options available for session state management. These options include: InProc: Session state is stored locally in the memory of the web server process. This is the default option and is generally suitable for small-scale applications. However, it’s not suitable for web farms or applications requiring high scalability because session data is lost if the web server process restarts. StateServer: Session state is stored in a separate process called the ASP.NET State Service. This…

Read More Read More

They exist for the life of the current page. In ASP.NET, the items stored in ViewState persist for the duration of a single page request-response cycle. Once the page is rendered and sent to the client, the ViewState data is serialized and sent as a hidden field within the page. Upon receiving a postback from the client, ASP.NET deserializes the ViewState data and restores the state of the page controls to their previous values. After the page lifecycle ends, ViewState…

Read More Read More

ViewState is stored in a hidden field on the page at client side. ViewState is transported to the client and back to the server, and is not stored on the server or any other external source. In ASP.NET, after a page postback, the ViewState is stored in the __VIEWSTATE hidden field. This hidden field is automatically generated by ASP.NET and is sent to the client along with the page’s HTML. Upon postback, the contents of the ViewState are sent back…

Read More Read More

ViewState is used to retain the state of server-side objects between page post backs. In ASP.NET, ViewState is a client-side state management technique used to preserve the state of server-side controls (such as textboxes, dropdown lists, etc.) across postbacks. When a web page is posted back to the server, ViewState stores the values of those controls in a hidden field on the page. When the page is reloaded, ASP.NET uses the ViewState to restore the state of the controls to…

Read More Read More

Compare Validator control. In ASP.NET, if you need to ensure that the values in two different controls match, you can use the CompareValidator control. The CompareValidator control compares the value entered into an input control with the value entered into another control or a constant value. You can specify the type of comparison operation (such as equality, less than, greater than, etc.) and the control to compare against using the ControlToCompare property. Here’s a basic example of how you might…

Read More Read More

Required field Validator Range Validator Compare Validator Custom Validator Regular expression Validator Summary Validator In ASP.NET, validators are used to perform validation checks on user input in web forms to ensure that the data entered by the user is valid before it is processed. There are several types of validators available in ASP.NET: RequiredFieldValidator: Ensures that the user enters a value in a specified input control. RegularExpressionValidator: Validates the input against a specified pattern defined by a regular expression. RangeValidator:…

Read More Read More