Home
ASP.Net
Interview FAQs

It measures the performance of a web application against resources (memory, processors, or computers) allocated for it.
It is the number of requests your application can serve in a time unit, usually in a second.
Response.Buffer=true;
Response.ExpiresAbsolute=DateTime.Now.AddDays(-1d);
Response.Expires =-1500;
Response.CacheControl="no-cache";
User controls are reusable controls, and they use the same techniques that are employed by HTML and Web server controls. They offer an easy way to partition and reuse common user interfaces across ASP.NET Web applications. They use the same Web Forms programming model on which a Web Forms page works.
Custom controls are compiled code components that execute on the server, expose the object model, and render markup text, such as HTML or XML, as a normal Web Form or user control does.
Windows Authentication is used when your user is tied up with the Windows Domain and you can validate the requested user against your domain controller or Active Directory.

When you configure ASP.NET for Windows authentication, it can be coupled with IIS authentication where IIS authenticates your application users by using Basic authentication, Integrated Windows authentication, Digest authentication, or Client Certificate authentication. Both Integrated Windows authentication and Client Certificate authentication provide strong authentication, but Integrated Windows authentication is recommended unless you have a PKI infrastructure and your clients have certificates.

SQL Server Authentication is more storing the user information in the database and when user returns you pick there user name and password to validate against the stored information in SQL Server database. This approach is taken in the internet application where they can store some information during the signin and validate when they return back.

You have to Write a code to get the user information, Access the database and validate whether that user is registered user or not.

There are two important classes in the hierarchy that are derived from System.Exception:

1) System.SystemException -> This class is for exceptions that are usually thrown by the .Net runtime, or which are considered to be of a generic nature and must be thrown by almost any application. For example, StackOverflowException will be thrown by the .Net runtime if it detects the stack is full. On the other hand, you might choose to throw ArgumentException or it is subclasses in ur code, if you detect that a method has been called with in-appropriate arguments. Subclasses of System.SystemException includes classes that represent both fatal and non-fatal errors.

2) System.ApplicationException-> This class is important, because it is the intended base for any class of exception defined by third parties. Hence, if you define any exceptions covering error conditions unique to your application, you should derive these directly or indirectly from System.ApplicationException

CTS and CLS are major components through which the interoperablility is achived in .Net framework.

CLS specifies some set of rules for all the .Net compilers. CLS stands for Common Language Specification
CTS stands for Common Type System. CTS ensures compatability between the components that are developed in different languages.

PreviousDisplaying 27 of 46Next
Need Help? Contact Us.

Log in

*
*

Forgot password?

*

New User

*
*
*
*