ASP.net Interview Questions - 2

• What’s a bubbled event?
  When you have a complex control, like DataGrid, writing an event processing routine for each object (cell, button, row, etc.) is quite tedious. The controls can bubble up their eventhandlers, allowing the main DataGrid event handler to take care of its constituents.
  
• Suppose you want a certain ASP.NET function executed on MouseOver for a certain button. Where do you add an event handler?
  Add an OnMouseOver attribute to the button. Example: btnSubmit.Attributes.Add("onmouseover","someClientCodeHere();");
  
• What data types do the RangeValidator control support?
  Integer, String, and Date.
  
• Explain the differences between Server-side and Client-side code?
  Server-side code executes on the server.
  Client-side code executes in the client's browser.
  
• What type of code (server or client) is found in a Code-Behind class?
  The answer is server-side code since code-behind is executed on the server. However, during the code-behind's execution on the server, it can render client-side code such as JavaScript to be processed in the clients browser. But just to be clear, code-behind executes on the server, thus making it server-side code.
  
• Should user input data validation occur server-side or client-side? Why?
  All user input data validation should occur on the server at a minimum. Additionally, client-side validation can be performed where deemed appropriate and feasable to provide a richer, more responsive experience for the user.
  
• What is the difference between Server.Transfer and Response.Redirect? Why would I choose one over the other?
  Server.Transfer transfers page processing from one page directly to the next page without making a round-trip back to the client's browser. This provides a faster response with a little less overhead on the server. Server.Transfer does not update the clients url history list or current url. Response.Redirect is used to redirect the user's browser to another page or site. This performas a trip back to the client where the client's browser is redirected to the new page. The user's browser history list is updated to reflect the new address.