There are three types of authentication available in ASP.NET:
Windows Authentication - This authentication method uses built-in windows security features to authenticate user.
Forms Authentication - authenticate against a customized list of users or users in a database.
Passport Authentication - validates against Microsoft Passport service which is basically a centralized authentication service.

Response.Redirect: A new request is generated from client-side for redirected page. Its a kind of additional round trip. As new request is generated from client, so the new URL is visible to user in browser after redirection.
Server.Transfer: A request is transferred from one page to another without making a round trip from client. For the end user, URL remains the same in browser even after transferring to another page.

Custom controls are basically compiled code i.e. DLLs. These can be easily added to toolbox, so it can be easily used across multiple projects using drag and drop approach. These controls are comparatively hard to create.
User Controls (.ascx) are just like pages (.aspx). These are comparatively easy to create but tightly couple with respect to User Interface and code. In order to use across multiple projects, we need to copy and paste to the other project as well.

The system.Diagnostics namespace contains the Debug and Trace classes that include shared methods.The difference between these two classes is in the way Trace and Debug statements are treated at the of creating a release build.

  • Trace statements are included by default when the program is compiled in to release build,where as debug statements are not.
  • The Debug class is used for debugging,however, the Trace class is used for testing and optimization even after an application is compiled and released.

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 asp.net-

  • 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.

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

Log in

*
*

Forgot password?

*

New User

*
*
*
*