Explore topic-wise InterviewSolutions in Current Affairs.

• @PAGE DIRECTIVE,
• @IMPORT directive,
• @IMPLEMENTS directive,
• @Register directive,
• @Assembly directive,
• @OUTPUTCACHE directive,
• @Reference directive.

PostBack is the name GIVEN to the process of submitting an ASP.NET page to the SERVER for processing. PostBack is done if certain credentials of the page are to be checked against some sources (such as VERIFICATION of username and password using database). This is something that a client MACHINE is not able to accomplish and thus these DETAILS have to be 'posted back' to the server.

PostBack is the name given to the process of submitting an ASP.NET page to the server for processing. PostBack is done if certain credentials of the page are to be checked against some sources (such as verification of username and password using database). This is something that a client machine is not able to accomplish and thus these details have to be 'posted back' to the server.

WINDOWS Forms is employed for developing Windows GUI applications. It is a class LIBRARY that gives developers ACCESS to Windows Common Controls with rich FUNCTIONALITY. It is a common GUI library for all the languages supported by the .NET Framework.

Windows Forms is employed for developing Windows GUI applications. It is a class library that gives developers access to Windows Common Controls with rich functionality. It is a common GUI library for all the languages supported by the .NET Framework.

Web services are programmable business LOGIC components that provide access to functionality through the Internet. Standard PROTOCOLS like HTTP can be used to access them. Web services are based on the SIMPLE Object Access Protocol (SOAP), which is an APPLICATION of XML. Web services are given the .asmx extension.

Web services are programmable business logic components that provide access to functionality through the Internet. Standard protocols like HTTP can be used to access them. Web services are based on the Simple Object Access Protocol (SOAP), which is an application of XML. Web services are given the .asmx extension.

DLL hell is the problem that OCCURS when an installation of a newer application might break or hinder other applications as newer DLLS are copied into the system and the older applications do not support or are not compatible with them, .NET overcomes this problem by SUPPORTING multiple versions of an ASSEMBLY at any GIVEN time. This is also called side-by-side component versioning.

DLL hell is the problem that occurs when an installation of a newer application might break or hinder other applications as newer DLLs are copied into the system and the older applications do not support or are not compatible with them, .NET overcomes this problem by supporting multiple versions of an assembly at any given time. This is also called side-by-side component versioning.

In order to replace a COM component on a live dedicated SERVER, it was necessary to stop the entire website, copy the new files and then restart the website. This is not feasible for the web servers that need to be always running. .NET components are different. They can be overwritten at any time using a mechanism called Shadow Copy. It prevents the Portable Executable (PE) files like DLLs and EXE's from being locked. Whenever new versions of the PE's are RELEASED, they are AUTOMATICALLY DETECTED by the CLR and the changed components will be automatically loaded. They will be used to process all new requests not currently executing, while the older version still runs the currently executing requests. By bleeding out the older version, the update is COMPLETED.

In order to replace a COM component on a live dedicated server, it was necessary to stop the entire website, copy the new files and then restart the website. This is not feasible for the web servers that need to be always running. .NET components are different. They can be overwritten at any time using a mechanism called Shadow Copy. It prevents the Portable Executable (PE) files like DLLs and EXE's from being locked. Whenever new versions of the PE's are released, they are automatically detected by the CLR and the changed components will be automatically loaded. They will be used to process all new requests not currently executing, while the older version still runs the currently executing requests. By bleeding out the older version, the update is completed.

An assembly is a collection of one or more FILES and one of them (DLL or EXE) contains a special metadata called Assembly Manifest. The manifest is stored as binary data and contains details like versioning requirements for the assembly, the author, security permissions, and list of files FORMING the assembly. An assembly is created whenever a DLL is built. The manifest can be viewed programmatically by making use of classes from the System. Reflection namespace. The tool Intermediate Language Disassembler (ILDASM) can be used for this purpose. It can be launched from the COMMAND prompt or via Start> Run.

An assembly is a collection of one or more files and one of them (DLL or EXE) contains a special metadata called Assembly Manifest. The manifest is stored as binary data and contains details like versioning requirements for the assembly, the author, security permissions, and list of files forming the assembly. An assembly is created whenever a DLL is built. The manifest can be viewed programmatically by making use of classes from the System. Reflection namespace. The tool Intermediate Language Disassembler (ILDASM) can be used for this purpose. It can be launched from the command prompt or via Start> Run.

• INIT(),
• LOAD(),
• PreRender(),
• UNLOAD().

The CLI is a set of specifications for a runtime ENVIRONMENT, INCLUDING a common TYPE system, base class library, and a machine-independent intermediate code known as the Common Intermediate Language (CIL). (Source: Wikipedia).

The CLI is a set of specifications for a runtime environment, including a common type system, base class library, and a machine-independent intermediate code known as the Common Intermediate Language (CIL). (Source: Wikipedia).

Common Language RUNTIME (CLR) is a run-time environment that manages the execution of .NET code and provides SERVICES like memory management, debugging, SECURITY, etc. The CLR is also known as Virtual Execution SYSTEM (VES).

Common Language Runtime (CLR) is a run-time environment that manages the execution of .NET code and provides services like memory management, debugging, security, etc. The CLR is also known as Virtual Execution System (VES).

• Windows(default),
• FORMS,
• Passport,
• NONE(SECURITY disabled).

Namespaces are logical GROUPINGS of names used WITHIN a program. There may be multiple namespaces in a SINGLE application code, grouped based on the identifier's use. The NAME of any given identifier must appear only once in its namespace.

Namespaces are logical groupings of names used within a program. There may be multiple namespaces in a single application code, grouped based on the identifier's use. The name of any given identifier must appear only once in its namespace.

ASP.NET 2.0, Visual Studio 2005 (Whidbey), Visual Web Developer 2005 EXPRESS Edition are the NEXT releases of Microsoft's Web platform and tools. They have ALREADY been RELEASED as Beta versions. They are scheduled to be released in the week of November 7, 2005.

ASP.NET 2.0, Visual Studio 2005 (Whidbey), Visual Web Developer 2005 Express Edition are the next releases of Microsoft's Web platform and tools. They have already been released as Beta versions. They are scheduled to be released in the week of November 7, 2005.

ASP.NET is a PART of the .NET framework which was released as a SOFTWARE platform in 2002.

ASP.NET is a part of the .NET framework which was released as a software platform in 2002.

.NET SDK can be OBTAINED here.

(You have to INSTALL the Microsoft .NET Framework Version 1.1 Redistributable PACKAGE before installing the .NET SDK.)

.NET SDK can be obtained here.

(You have to install the Microsoft .NET Framework Version 1.1 Redistributable Package before installing the .NET SDK.)

MICROSOFT provides Visual STUDIO 2005 EXPRESS Edition Beta for free. Of particular interest to the ASP.NET developers would be the Visual Web Developer 2005 Express Edition Beta 2 available as a free download.

The ASP.NET Web Matrix Project (supported by Microsoft) is a free IDE for developing ASP.NET applications and is available here.

There is also a free open-source UNIX version of the Microsoft .NET DEVELOPMENT platform called Mono available for download here.

Another increasingly popular Open Source Development Environment for .NET is the #develop (short for SharpDevelop) available for download here.

Microsoft provides Visual Studio 2005 Express Edition Beta for free. Of particular interest to the ASP.NET developers would be the Visual Web Developer 2005 Express Edition Beta 2 available as a free download.

The ASP.NET Web Matrix Project (supported by Microsoft) is a free IDE for developing ASP.NET applications and is available here.

There is also a free open-source UNIX version of the Microsoft .NET development platform called Mono available for download here.

Another increasingly popular Open Source Development Environment for .NET is the #develop (short for SharpDevelop) available for download here.

WINDOWS 2000, Windows Server 2003 or Windows XP.

ASP.NET, which can be either the redistributable (INCLUDED in the .NET SDK) or Visual Studio .NET.

Windows 2000, Windows Server 2003 or Windows XP.

ASP.NET, which can be either the redistributable (included in the .NET SDK) or Visual Studio .NET.

Linked List:

• They allow a NEW element to be inserted or deleted at any position in a constant number of operations (changing some references) O(1).
• Easy to delete a NODE (as it only has to rearrange the links to the different nodes)., O(1).
• To find the nth node, will need to recurse through the list TILL it finds [linked lists allow only sequential access to elements. ], O(n)

Array

• Insertion or deletion of element at any position require a linear (O(n)) number of operations.
• POOR at deleting nodes (or elements) as it cannot remove one node without individually shifting all the elements up the list by one., O(n)
• Poor at inserting as an array will EVENTUALLY either fill up or need to be resized, an expensive operation that may not even be possible if memory is fragmented. Similarly, an array from which many elements are removed may become wastefully empty or need to be made smaller, O(n)
• easy to find the nth element in the array by directly referencing them by their position in the array.[ arrays allow random access ] , O(1)

Linked List:

Array

CurrentPageIndex.

You NEED to SET this ONE with the DataGridPageChangedEventArgs' NewPageIndex.

CurrentPageIndex.

You need to set this one with the DataGridPageChangedEventArgs' NewPageIndex.

False.

False.

SERVER.Transfer.

Response.Redirect ALSO does that but it requires ROUND trip between CLIENT and server.

Server.Transfer.

Response.Redirect also does that but it requires round trip between client and server.

SOAP.

SOAP.

HyperLinkColumn.

HyperLinkColumn.

If you are DEVELOPING web services and the cookies need to be travelled across multiple requests, then it need to have PERMANENT or persistant cookie. In ORDER to do this, you have to set your webserivce CookieContainer to a newly created Cookie Container, and set its cookie to a session value and then store the cookie(s) into the SERVICE CookieCollection from that cookie container if something is there otherwise ADD cookie to the container.

If you are developing web services and the cookies need to be travelled across multiple requests, then it need to have permanent or persistant cookie. In order to do this, you have to set your webserivce CookieContainer to a newly created Cookie Container, and set its cookie to a session value and then store the cookie(s) into the Service CookieCollection from that cookie container if something is there otherwise add cookie to the container.

You NEED to SET AutoGenerateColumns PROPERTY to FALSE.

You need to set AutoGenerateColumns Property to false.

The common PROPERTIES are:

• ISVALID (bool)
• ControlToValidate (STRING)
• ErrorMessage (string)
• ValidationDisplay (DISPLAY)
• TEXT (string)

The common method is:Validate().

The common properties are:

The common method is:Validate().

Actually I never did this. But there should be a WAY to do this. May be need to write your own CODE to do this USING RESPONSE. Cookies collection and HTTPCookie class and ALSO SessionStateMode. Or there may be some simple way to do it. Need to do further research on this.

Actually I never did this. But there should be a way to do this. May be need to write your own code to do this using Response. Cookies collection and HTTPCookie class and also SessionStateMode. Or there may be some simple way to do it. Need to do further research on this.

Session.Abandon()

Session.Abandon()

This is the order of Page EVENTS

• Page_Init
• Page_LoadViewState
• Page_LoadPostData
• Page_Load
• Page_RaisePostDataChanged
• Page_RaisePostBackEvent
• Page_PreRender
• Page_SaveViewState
• Page_Render
• Page_Dispose
• Page_Error(this is caused whenever there is an exception at the page LEVEL).

Out of all the Page_Load is the one where your code GETS LOADED and your magic should be written. page_init occurs only once, i.e. when the page is initially created.

As a DEVELOPER you need to know these, becuase your development activity is coding for these only.

This is the order of Page events

Out of all the Page_Load is the one where your code gets loaded and your magic should be written. page_init occurs only once, i.e. when the page is initially created.

As a developer you need to know these, becuase your development activity is coding for these only.

You need to CREATE a CLRHost, which hosts the CLR (ASP.NET) on top of Apache. SINCE Apache is #1 webserver used by many COMPANIES, this would allow more NUMBER of web SITE owners to take advantage of ASP.NET and its richness.

You need to create a CLRHost, which hosts the CLR (ASP.NET) on top of Apache. Since Apache is #1 webserver used by many companies, this would allow more number of web site owners to take advantage of ASP.NET and its richness.

Sometimes it is NECESSARY to carry a particular session data across PAGES, and HTTP is a stateless protocol. In order to maintain state between page calls, we could use cookies, hidden form fields etc. One of them is using sessions. each sessions are maintain a unique key on the server and serialize the data on it. Actually it is a hashtable and stores data on key/value pair of combination. You could set a session using Session Object and retrieve the same data/state by passing the key.

//Set
Session["abc"] = "Session Value";

// Get
string abc = Session["abc"].ToString();

The downside of sessions is scalability. Say your application gets more and more hits and you though instead of one webserver handling it, have it in a webform (multiple web servers working under one domain). You cannot transfer the session so easily across multiple webservers. it PHYSICALLY serializes the state data to webserver hard disk. .NET proposes a new way to handle this using a stateserver (actually a trimmed down sql server) storing the web session data in a factory configured database SCHEMA or using Database with your own schema defined to handle the sessions.

Sometimes it is necessary to carry a particular session data across pages, and HTTP is a stateless protocol. In order to maintain state between page calls, we could use cookies, hidden form fields etc. One of them is using sessions. each sessions are maintain a unique key on the server and serialize the data on it. Actually it is a hashtable and stores data on key/value pair of combination. You could set a session using Session Object and retrieve the same data/state by passing the key.

//Set
Session["abc"] = "Session Value";

// Get
string abc = Session["abc"].ToString();

The downside of sessions is scalability. Say your application gets more and more hits and you though instead of one webserver handling it, have it in a webform (multiple web servers working under one domain). You cannot transfer the session so easily across multiple webservers. it physically serializes the state data to webserver hard disk. .NET proposes a new way to handle this using a stateserver (actually a trimmed down sql server) storing the web session data in a factory configured database schema or using Database with your own schema defined to handle the sessions.

Polymorphism is ACHIEVED through virtual, overloaded, OVERRIDDEN METHODS in C# and VB.NET.

Polymorphism is achieved through virtual, overloaded, overridden methods in C# and VB.NET.

ASP.NET webforms are analogous to Windows Forms which are available to most VB developers. A webform is essentially a core container in a Page. An empty webform is nothing but a HTML FORM tag(CONTROL) RUNNING at server and posting form to itself by DEFAULT, but you could change it to post it to something else. This is a container, and you could place the WEB controls, user controls and HTML Controls in that one and interact with user on a postback basis.

ASP.NET webforms are analogous to Windows Forms which are available to most VB developers. A webform is essentially a core container in a Page. An empty webform is nothing but a HTML Form tag(control) running at server and posting form to itself by default, but you could change it to post it to something else. This is a container, and you could place the web controls, user controls and HTML Controls in that one and interact with user on a postback basis.

Use the STATE server or store the state in the DATABASE. This can be easily done through simple setting change in the web.config.

<sessionState mode="InProc" stateConnection String= "tcpip=127.0.0. 1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa; password=" cookieless="false" timeout="30"/>

in the above one INSTEAD of mode="InProc", you specifiy stateserver or sqlserver.

Use the state server or store the state in the database. This can be easily done through simple setting change in the web.config.

<sessionState mode="InProc" stateConnection String= "tcpip=127.0.0. 1:42424" sqlConnectionString="data source=127.0.0.1;user id=sa; password=" cookieless="false" timeout="30"/>

in the above one instead of mode="InProc", you specifiy stateserver or sqlserver.

In the Application_Start event you COULD store the DATA, which is used throughout the life time of an application for example application name, where as Session_Start could be used to store the information, which is required for that SESSION of the application SAY for example user ID or user name.

In the Application_Start event you could store the data, which is used throughout the life time of an application for example application name, where as Session_Start could be used to store the information, which is required for that session of the application say for example user id or user name.

You have to USE System.EnterpriseServices NAMESPACE and ALSO COMInterop the EXISTING APPLICATION.

You have to use System.EnterpriseServices namespace and also COMInterop the existing application.

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 re connected 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.

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 re connected 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.

It ALLOWS the page to save the users INPUT on a FORM across postbacks. It saves the server-side values for a GIVEN control into ViewState, 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 viewstate.

It allows the page to save the users input on a form across postbacks. It saves the server-side values for a given control into ViewState, 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 viewstate.

ITEM stored in ViewState EXIST for the life of the CURRENT page. This includes POSTBACKS (to the same page).

Item stored in ViewState exist for the life of the current page. This includes postbacks (to the same page).

VIEWSTATE allows the state of objects (SERIALIZABLE) to be stored in a hidden field on the page. ViewState is transported to the CLIENT and back to the server, and is not stored on the server or any other EXTERNAL source. ViewState is used the RETAIN the state of server-side objects between postbacks.

ViewState allows the state of objects (serializable) to be stored in a hidden field on the page. ViewState is transported to the client and back to the server, and is not stored on the server or any other external source. ViewState is used the retain the state of server-side objects between postbacks.

Webservice is one of main component in Service Oriented Architecture. You could use WEBSERVICES when your clients and servers are running on different networks and also different PLATFORMS. This provides a loosely COUPLED system. And also if the client is behind the firewall it would be EASY to use webserivce since it runs on PORT 80 (by default) instead of having some thing else in SOA apps.

Webservice is one of main component in Service Oriented Architecture. You could use webservices when your clients and servers are running on different networks and also different platforms. This provides a loosely coupled system. And also if the client is behind the firewall it would be easy to use webserivce since it runs on port 80 (by default) instead of having some thing else in SOA apps.

False,

The web service comes with a TEST PAGE and it PROVIDES HTTP-GET METHOD to test.

False,

The web service comes with a test page and it provides HTTP-GET method to test.

HTTP://www.uddi.org

http://www.uddi.org

WEB SERVICES DESCRIPTION LANGUAGE.

Web Services Description Language.

SOAP(SIMPLE Object Access PROTOCOL) is the PREFERRED protocol.

SOAP(Simple Object Access Protocol) is the preferred protocol.

It can CONTAIN MANY CLASSES.

It can contain many classes.

CompareValidator CONTROL.

CompareValidator control.

DataTextField PROPERTY.

DataTextField property.

• ControlToValidate PROPERTY and,
• TEXT property.

The PAGE CLASS.

The Page class.