We do not guarantee the correctness of all answers. It is user’s responsibility to make sure that the answers are right. Good luck.
inetinfo.exe is the Microsoft IIS server running, handling ASP.NET requests among with 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 to the actual worker process aspnet_wp.exe.
Response.Output.Write() allows you to write formatted output.
1. PreInit()- In this Page level event, all controls created during design time are initialized with their default values.
Init() - when the page is instantiated. In this event, we can read the controls properties (set at design time).
LoadViewState- This will only fire if the Page has posted back (IsPostBack == true). Here the runtime de-serializes the view state data from the hidden form element and loads all controls who have view state enabled.
LoadPostBackData: In this event the controls which implement IPostBackDataHandler interface gets loaded by the values from the HTTP POST data.
Control Event Handlers-
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.
After the Init() and before the Page_Load(), or OnLoad() for a control.
CodeBehind is relevant to Visual Studio.NET only.
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.
Add an OnMouseOver attribute to the button.
Integer, String, and Date.
Server-side code executes on the server. Client-side code executes in the client's browser.
All user input data validation should occur on the server at a minimum. Additionally, client-side validation can be performed. The client side validation is fast, cofortable for the user and reduce server overhead.
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.
The Global.asax (including the Global.asax.cs file) is used to implement serverl events.
This is where you can set the specific variables for the Application and Session objects.
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.
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.
The" Fill()" method.
Use the AlternatingItemTemplate.
You must set the DataSource property and call the DataBind method.
The Page class.
ControlToValidate property and Text property.
Any number of classess.
SOAP (Simple Object Access Protocol) is the preferred protocol.
Web Services Description Language.
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.
Item stored in ViewState exist for the life of the current page. This includes postbacks (to the same page).
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.
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.
Alias to associate with the usercontrols namespace.
Using "LoadControl()" method of the Page.
Immediatly after the request for the page contain the class in the code behind called.
It returns a read-only, forward-only rowset from the data source. A DataReader provides fast access when a forward-only sequential read is needed.
SQLServer.NET data provider is high-speed and robust, but requires SQL Server license purchased from Microsoft. OLE-DB.NET is universal for accessing other sources, like Oracle, DB2, Microsoft Access and Informix. OLE-DB.NET is a .NET layer on top of the OLE layer, so it’s not as fastest and efficient as SqlServer.NET.
A transaction must be: 1. Atomic - it is one unit of work and does not dependent on previous and following transactions.
2. Consistent - data is either committed or roll back, no “in-between” case where something has been updated and something hasn’t.
3. Isolated - no transaction sees the intermediate results of the current transaction).
4. Durable - the values persist if the data had been committed even if the system crashes right after.
Windows Authentication (via Active Directory) and SQL Server authentication (via Microsoft SQL Server username and password).
Windows Authentication is trusted because the username and password are checked with the Active Directory, the SQL Server authentication is untrusted, since SQL Server is the only verifier participating in the transaction.
The database name to connect to.
Multiple processes must agree that they will share the same connection, where every parameter is the same, including the security settings. The connection string must be identical. Explicitly close connection with the "Close()'.
SqlCommand represent SQL statement or stored procedure.
It contains the results from a database query.
Number of seconds befire the connection timeout.
The process of dyanamically assigning a value to a property of a control at run time is called data binding.
Since ASP.NET page is also a control, the page's Databind() method is called and all databinding expression in the page(including all child control's) is evaluated.
ItemDataBound event is rised when each item retrived from the DataSource. So if the Datasource contains 10 item this event is rised 10 times.
Repeater, DataList and DataGrid controls.
The mechanism of capturing events from the child controls by the container control is called event bubbling.
When an event is rised in a child control, the event "bubbles up" to the containing control and then the containing control can execute the subroutne to handle the event.
Whe we use the method of paging thrugh records all the records must be retrived from the datasource every time we navigate to the new page.
Session_Start() and Session_End()
The global assembly cache stores assemblies specifically designated to be shared by several applications on the computer.
The friend assemblies feature allows you to access internal members in an assembly from another assembly.
Basically adding a assemblies to GAC has four steps
ASP.NET control (sometimes called a server control) is a server-side component that is shipped with .NET Framework. A server control is a compiled DLL file and cannot be edited. It can, however, be manipulated through its public properties at design-time or runtime.
User controls is also called Custom Control or composite control. A user control will consist of previously built server controls (called constituent controls when used within a user control). It has an interface that can be completely edited and changed. It can be manipulated at design-time and runtime via properties that you are responsible for creating. While there will be a multitude of controls for every possible function built by third-party vendors for ASP.NET, they will exist in the form of compiled server controls, as mentioned above.