Answer: inetinfo.exe is theMicrosoft IIS server running, handling ASP.NET requests among other things.When an ASP.NET request is received (usually a file with .aspx extension), the ISAPI filter aspnet_isapi.dll takes care of it by passing the request tothe actual worker process aspnet_wp.exe.
Answer: Response.Output.Write() allows you to write formatted output.
Answer: Methods are:
- Init(): When the page is instantiated.
- Load(): When the page is loaded into server memory.
- PreRender(): The brief moment before the page is displayed to the user as HTML.
- Unload(): When page finishes loading.
Ans: After the Init() and before the Page_Load(), or OnLoad() for a control.
Ans: CodeBehind is relevant to Visual Studio.NET only.
Ans: 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.
Q9: Suppose you want a certain ASP.NET function executed on MouseOver for a certain button. Where do you add an event handler?
Ans: Add an OnMouseOver attribute to the button.
Ans: Integer, String, and Date.
Ans: Server-side code executes on the server. Client-side code executes in the client's browser.
Ans: 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.
Q14: What is the difference between Server.Transfer and Response.Redirect? Why would I choose one over the other?
Ans: 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.
Ans: Valid answers are:
- A DataSet can represent an entire relational database in memory, complete with tables, relations, and views.
- A DataSet is designed to work without any continuing connection to the original data source.
- Data in a DataSet is bulk-loaded, rather than being loaded on demand.
- There's no concept of cursor types in a DataSet.
- DataSets have no current record pointer You can use For Each loops to move through the data.
- You can store many edits in a DataSet, and write them to the original data source in a single operation.
- Though the DataSet is universal, other objects in ADO.NET come in different versions for different data sources.
Ans: The Global.asax (including the Global.asax.cs file) is used to implement application and session level events.
Ans: This is where you can set the specific variables for the Application and Session objects.
Ans: When you want to inherit (use the functionality of) another class. Example: With a base class named Employee, a Manager class could be derived from the Employee base class.
Q19: Whats an assembly and Explain what a diffgram is, and a good use for one?
Ans: Assemblies are the building blocks of the .NET framework. Overview of assemblies from MSDN Describe the difference between inline and code behind. Inline code written along side the html in a page. Code-behind is code written in a separate file and referenced by the .aspx page.
The DiffGram is one of the two XML formats that you can use to render DataSet object contents to XML. A good use is reading database data to an XML file to be sent to a Web Service.
Q20: Whats MSIL, and why should my developers need an appreciation of it if at all?
Ans: MSIL is the Microsoft Intermediate Language. All .NET compatible languages will get converted to MSIL. MSIL also allows the .NET Framework to JIT compile the assembly on the installed computer.
Q21: Which method do you invoke on the DataAdapter control to load your generated dataset with data?
Ans: The Fill() method.
Ans: Use the AlternatingItemTemplate.
Q24: What property must you set, and what method must you call in your code, in order to bind the data from a data source to the Repeater control?
Ans: You must set the DataSource property and call the DataBind method.
Ans: The Page class.
Ans: ControlToValidate property and Text property.
Q27: Which property on a Combo Box do you set with a column name, prior to setting the DataSource, to display data in the combo box?
Ans: DataTextField property.
Q28: Which control would you use if you needed to make sure the values in two different controls matched?
Ans: CompareValidator control.
Ans: It can contain many classes.
Q30: What is the transport protocol you use to call a Web service?
Ans: SOAP (Simple Object Access Protocol) is the preferred protocol.
Ans: Web Services Description Language.
Q33: To test a Web service you must create a Windows application or Web application to consume this service. True or False?
Ans: False, the web service comes with a test page and it provides HTTP-GET method to test.
Q34: What is ViewState?
Ans: ViewState allows the state of objects (serializable) to be stored in a hidden field on the page. ViewState is transported to the client and back to the server, and is not stored on the server or any other external source. ViewState is used the retain the state of server-side objects between postabacks.
Ans: Item stored in ViewState exist for the life of the current page. This includes postbacks (to the same page).
Q36: What does the "EnableViewState" property do? Why would I want it on or off?
Ans: It allows the page to save the users input on a form across postbacks. It saves the server-side values for a given control into ViewState, which is stored as a hidden value on the page before sending the page to the clients browser. When the page is posted back to the server the server control is recreated with the state stored in viewstate.
Q37: What are the different types of Session state management options available with ASP.NET?
Ans: ASP.NET provides In-Process and Out-of-Process state management. In-Process stores the session in memory on the web server. This requires the a "sticky-server" (or no load-balancing) so that the user is always reconnected to the same web server. Out-of-Process Session state management stores data in an external data source. The external data source may be either a SQL Server or a State Server service. Out-of-Process state management requires that all objects stored in session are serializable.