-
Which of the 3 lanuages specified can be used for server side scripting in ASP.NET?
Skill/Topic: BeginnerA) C#B) CC) Visual BasicD)
-
The number of forms that can be added to a aspx page is
Skill/Topic: IntermediateA) 2B) 3C) 1D) More than 3
manceelee
- Feb 10th, 2016
Allows 1 form with runat="server" but can be use as many as forms without runat="server"
Pratul Tripathi
- Sep 2nd, 2015
You can have only 1 form with runat="server". If you use more, you will get a runtime error.
-
Custom Controls are derived from which of the classes
Skill/Topic: BeginnerA) System.Web.UI.WebcontrolB) System.Web.UI.CustomcontrolC) System.Web.UI.Customcontrols.Webcontrol
-
What is the default authentication mode for IIS
Skill/Topic: IntermediateA) WindowsB) AnonymousC) Basic AuthenticationD) None
-
-
What are the different types of sessions in ASP.Net? Name them.
Jaimie
- Feb 1st, 2016
1. Inproc
2. Out Proc
3. StateServer -
What executable unit gets created when we build an ASP.Net application?
Skill/Topic: BeginnerA) . EXEB) . DLLC) . COM
-
ASP .Net Page Life Cycle
Explain the life cycle of an ASP .NET page.
Read Best Answer
Editorial / Best Answer
aanand_agrawal- Member Since Apr-2009 | Apr 30th, 2009
1. OnInit (Init) Initializes each child control of the current
2. LoadControlState: Loads the ControlState of the control. To use this method, the control must call the Page.RegisterRequiresControlState method in the OnInit method of the control.
3. LoadViewState: Loads the ViewState of the control.
4. LoadPostData: Is defined on interface IPostBackDataHandler. Controls that implement this interface use this method to retrieve the incoming form data and update the controls properties accordingly.
5. Load (OnLoad): Allows actions that are common to every request to be placed here. Note that the control is stable at this time; it has been initialized and its state has been reconstructed.
6. RaisePostDataChangedEvent: Is defined on the interface IPostBackData-Handler. Controls that implement this interface use this event to raise change events in response to the Postback data changing between the current Postback and the previous Postback. For example, if a TextBox has a TextChanged event and AutoPostback is turned off, clicking a button causes the Text-Changed event to execute in this stage before handling the click event of the button, which is raised in the next stage.
7. RaisePostbackEvent: Handles the client-side event that caused the Postback to occur
8. PreRender (OnPreRender): Allows last-minute changes to the control. This event takes place after all regular Post-back events have taken place. This event takes place before saving ViewState, so any changes made here are saved.
9. SaveControlState: Saves the current control state to ViewState. After this stage, any changes to the control state are lost. To use this method, the control must call the Page.RegisterRequiresControlState method in the OnInit method of the control.
10. SaveViewState: Saves the current data state of the control to ViewState. After this stage, any changes to the control data are lost.
11. Render: Generates the client-side HTML, Dynamic Hypertext Markup Language (DHTML), and script that are necessary to properly display this control at the browser. In this stage, any changes to the control are not persisted into ViewState.
12. Dispose: Accepts cleanup code. Releases any unman-aged resources in this stage. Unmanaged resources are resources that are not handled by the .NET common language runtime, such as file handles and database connections.
13. UnLoad
Abhijit
- Apr 1st, 2015
I wont go in detail but I can write down the sequence of execution.
1) PreInit
2) Init
3) InitComplete
4) PreLoad
5) Load
6) Controls Event (postback events of all controls on page)
7) LoadComplete
8) PreRender
9) SaveSateComplete
10) Render
11) Unload
sivasubramanian.hariharan
- Jan 11th, 2011
Start-properties such as Request,Response,IsPostBack are set.Page IntializationloadValidationPostBack Event handlingRederingUnloadFor Detail Description go thruhttp://msdn2.microsoft.com/en-us/library/ms178472.aspx
-
One application can have only one Web config file - true or false
Read Best Answer
Editorial / Best Answer
Answered by: Harit Pandya
- Oct 10th, 2006
An asp.net application is a virtual directory that you make on a web server. This application will take the settings of machine.config file if a web.config file is not available in that directory. Now if you create a sub directory inside a virtual directory and place another web.config file in the sub directory then the sub directory will take the settings of the web.config file in that particular directory.
So my answer is that an application can have more than one web.config file but they should be in different directories of that web application and also the sub directory that uses it should be a virtual directory
Shrikant B
- May 18th, 2016
One project can have multiple Web.Config files.
Pratul Tripathi
- Sep 2nd, 2015
A project can have multiple web.config files, but at different levels. here different levels means at different folder or structure. In this case every page running uses the web.config file at its level/structure and if not found goes to its parent structure.
-
ASP.NET Interview Questions
Read Best Answer
Ans