Indexer: Indexer can be termed as location indicators and they are used to access class objects in the same way as array elements are accessed.

Cookie is the small text file which is stored on client machine. It uses to store the small amount of information on client.
Cookie consists of the following two parts:
Key – Name of Cookie.
Value – Information stored in the cookie.
We also can specify the life of a cookie, if you do not specify the life of a cookie, then it will last on the client machine till you do not clean it.We can specify the particular date and time when the cookie is automatically removed from the client machine.Cookie are used to transfer the information from one page to another page. You can also disable the cookie on the browser so that the information did not store on your machine.

.Net is not a language, it is a framework that provides a library for writing and executing programs at runtime in many programming languages, including Visual C#, Visual Basic, Visual F# and C++/CLI. The .NET Framework consists of a virtual execution system called CLR and a set of Class Libraries.We can create or develop Web, Window and Console applications within the Microsoft Environment.

 ASP.NET provides validation server controls. All validation controls inherits from BaseValidator class which contains the common validation properties and methods like ControlToValidate, Enabled, IsValid, EnableClientScript, ValidationGroup,Validate() etc.
ASP.Net provides a range of validation controls:

Global.asax is basically ASP.NET Application file. It’s a place to write code for Application-level events such as Application start, Application end, Session start and end, Application error etc. raised by ASP.NET or by HTTP Modules.There is a good list of events that are fired but following are few of the important events in Global.asax:
Application_Init occurs in case of application initialization for the very first time.
Application_Start fires on application start.
Session_Start fires when a new user session starts
Application_Error occurs in case of an unhandled exception generated from application.
Session_End fires when user session ends.
Application_End fires when application ends or time out.

The first line of an ASP.NET page is the page directive; you will find it on all ASP.NET pages. These directives are instructions for the page. It begins with the @Page directive and continues with the various attributes available to this directive.
Its unreasonable to expect a candidate to know all of these attributes, but a few popular ones include the following.
AutoEventWireup: Indicates whether page events are autowired.
CodeBehind: The name of the compiled class associated with the page.
Debug: Indicates whether the page is compiled in debug mode (includes debug symbols).
EnableTheming: Indicates whether themes are used on the page.
EnableViewState: Indicates whether view state is maintained across pages.
ErrorPage: Specifies a target URL to be used when unhandled exceptions occur.
Language: Indicates the language used when compiling inline code on the page.
Trace: Signals whether tracing is enabled on the page.

An array of arrays is known as jagged array.It is single dimensional and the arrays which it contains as its elements need not be of same size

Instead of enabling tracing for individual pages, you can enable it for your entire application. In that case, every page in your application displays trace information. Application tracing is useful when you are developing an application because you can easily enable it and disable it without editing individual pages. When your application is complete, you can turn off tracing for all pages at once.

One solution that you can use to handle the session timeout errors is using JSON or XML format as output for your AJAX requests.

Finalizers

Finalizers are special methods that are automatically called by the GC before the object is collected. They can only be called by the GC provided they exist. The .NET ultimate base class Object has a Finalize method that can be overridden by child objects (anyone basically). The purpose of finalizers is to ensure all unmanaged resources the object may be using are properly cleaned up prior to the end of the object lifetime.
If a type has an implemented (overridden) finalizer at the time of collection, the GC will first put the object in the finalization queue, then call the finalizer and then the object is destroyed.Finalizers are not directly supported by C# compilers; instead you should use destructors using the ~ character, like so:

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

Log in

*
*

Forgot password?

*

New User

*
*
*
*