What is the role of global.asax. »
By admin on Jan 5, 2007 in ASP.NET Interview Questions, Technical | 0 Comments
Store global information about the application
Java Interview Questions | IT interview questions | Software Testing Interview questions | .Net Interview Questions | Job Interview Questions & Answers | Tough Interview Questions | Technology Interview Questions | Tech Interview Questions | Testing Interview Questions | SAP Interview Questions | ABAP Interview Questions | Data Warehousing Interview Questions
Recent ArticlesBy admin on Jan 5, 2007 in ASP.NET Interview Questions, Technical | 0 Comments
Store global information about the application
By admin on Jan 5, 2007 in ASP.NET Interview Questions, Technical | 0 Comments
No, You have to use Server. Transfer to pass the data to another page.
By admin on Jan 5, 2007 in ASP.NET Interview Questions, Technical | 0 Comments
By default all pages in .NET post back to themselves. The view state keeps the users input updated on the page.
By admin on Jan 5, 2007 in ASP.NET Interview Questions, Technical | 0 Comments
Server controls are built-in. User controls are created by the developer to allow for the reuse of controls that need specific functionality.
By admin on Jan 5, 2007 in ASP.NET Interview Questions, Technical | 0 Comments
By admin on Jan 5, 2007 in ASP.NET Interview Questions, Technical | 0 Comments
By admin on Jan 5, 2007 in ASP.NET Interview Questions, Technical | 0 Comments
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.
By admin on Jan 5, 2007 in ASP.NET Interview Questions, Technical | 0 Comments
It allows the page to save the users input on a form across post backs. It saves the server-side values for a given control into View State, 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 view state.