ASP.NET supports different session state storage options:

  • In-Process is the default approach. It stores session state locally on same web server memory where the application is running.
  • StateServer mode stores session state in a process other than the one where application is running. Naturally, it has added advantages that session state is accessible from multiple web servers in a Web Farm and also session state will remain preserved even web application is restarted.
  • SQLServer mode stores session state in SQL Server database. It has the same advantages as that of StateServer.
  • Custom modes allows to define our custom storage provider.
  • Off mode disables session storage.

ASP.NET Web Forms uses Page controller pattern approach for rendering layout. In this approach, every page has its own controller i.e. code-behind file that processes the request. 

 ASP.NET MVC uses Front Controller approach. In this approach a common controller for all pages, processes the requests.

We can register javascript for controls using

 <CONTROL -name>Attribtues.Add(scriptname,scripttext) method.

In strong typing, the data types of variable are checked at compile time. On the other hand, in case of weak typing the variable data types are checked at runtime. In case of strong typing, there is no chance of compilation error. Scripts use weak typing and hence issues arises at runtime.

There are two options of session state management techniques in

  • In-Process
  • Out-of-Process.

In-Process stores the session in memory on the web server.

Out-of-Process Session state management stores data in an external server.  The external server may be either a SQL Server or a State Server.  All objects stored in session are required to be serializable for Out-of-Process state management.

They exist for the life of the current page.
ViewState is stored in a hidden field on the page at client side.  ViewState is transported to the client and back to the server, and is not stored on the server or any other external source.

The appSettings block in web config file sets the user-defined values for the whole application.
For example, in the following code snippet, the specified ConnectionString section is used throughout the project for database connection:

<add key=”ConnectionString” value=”server=local; pwd=password; database=default” />

A breakpoint is a marker in your source code that triggers automatic entry into break mode.
These features are available only in debug builds. If you compile a release build, all breakpoints are ignored. There are several ways to add breakpoints. To add simple breakpoints that break when a line is reached, just left-click on the far left of the line of code, right-click on the line, and select Breakpoint ? Insert Breakpoint; select Debug ? Toggle Breakpoint from the menu; or press F9.
A breakpoint appears as a red circle next to the line of code

PreviousDisplaying 3 of 6Next
1 2 3 4 5 6
Need Help? Contact Us.

Log in


Forgot password?


New User