ASP.NET Exclusive Interview Questions and Answers (348) - Page 4

  • A joint initiative from DotNetFunda.Com and Questpond.
  • A one stop place on the internet to get trusted and proven Interview Questions (based on more than a decade of experience in this field) to ensure the success of the candidates.
  • You will find almost all Interview questions from Questpond here and this list is growing day by day with all latest and updated interview questions.

348 records found.

Get 650+ Questpond's Interview videos on discount

How will implement Page Fragment Caching?

Page fragment caching involves the caching of a fragment of the page, rather than the entire page. When portions of the page are need to be dynamically created for each user request this is best method as compared to page caching. You can wrap Web Forms user control and cache the control so that these portions of the page do not need to be recreated each time.


Can you compare ASP.NET sessions with classic ASP?

ASP. NET session caches per user session state. It basically uses “HttpSessionState” class.

Following are the limitations in classic ASP sessions: -

• ASP session state is dependent on IIS process very heavily. So if IIS restarts ASP session variables are also recycled.ASP.NET session can be independent of the hosting environment thus ASP. NET session can be maintained even if IIS reboots.

• ASP session state has no inherent solution to work with Web Farms.ASP.NET session can be stored in state server and SQL SERVER which can support multiple server.

• ASP session only functions when browser supports cookies.ASP.NET session can be used with browser side cookies or independent of it.


Which are the various modes of storing ASP.NET session?

In Proc: - In this mode Session, state is stored in the memory space of the Aspnet_wp.exe process. This is the default setting. If the IIS reboots or web application restarts then session state is lost.

State Server: -In this mode Session state is serialized and stored in a separate process (Aspnet_state.exe); therefore, the state can be stored on a separate computer (a state server).

SQL SERVER: - In this mode Session, state is serialized and stored in a SQL Server database.
Session state can be specified in <session State> element of application configuration file. Using State Server and SQL SERVER session state can be shared across web farms but note this comes at speed cost as ASP. NET needs to serialize and desterilize data over network repeatedly.


Is Session End event supported in all session modes?

Session End event occurs only in “Inproc mode”. “State Server” and “SQL SERVER” do not have Session End event.


What are the steps to configure State Server Mode?

Following are the things to remember so that State Server Mode works properly: -

• State Server mode session data is stored in a different process so you must ensure that your objects are serializable.

• <machine Key> elements in Web.config should be identical across all servers. So this ensures that encryption format is same across all computers.

• IIS meta base (\LM\W3SVC\2) must be identical across all servers in that farm.


What are the steps to configure SQL Server mode?

Following are the things to remember so that SQL SERVER Mode works properly: -

• SQL SERVER mode session data is stored in a different process so you must ensure that your objects are serializable.

• IIS met abase (\LM\W3SVC\2) must be identical across all servers in that farm.

• By default Session objects are stored in “Temped”, you can configure it store outside “TempDB” by running Microsoft provided SQL script.


Note: - “TempDB” database is re-created after SQL SERVER computer reboot.If you want to maintain session state with every reboot best is to run SQL Script and store session objects outside “TempDB” database.


Where do you specify session state mode in ASP.NET?

<sessionState mode=”SQLServer”
stateConnectionString=”tcpip=192.168.1.1:42424"
sqlConnectionString=”data source=192.168.1.1; Integrated Security=SSPI”
cookieless=”false”
timeout=”20"
/>
Above is sample session state mode specified for SQL SERVER.


What are the other ways you can maintain state?

Other than session variables, you can use the following technique to store state: -
• Hidden fields
• View state
• Hidden frames
• Cookies
• Query strings


What are benefits and Limitation of using Hidden fields?

Following are the benefits of using Hidden fields: -

• They are simple to implement.
• As data is cached on client side, they work with Web Farms.
• All browsers support hidden field.
• No server resources are required.

Following are limitations of Hidden field: -

• They can be tampered creating a security hole.
• Page performance decreases if you store large data, as the data are stored in pages itself.
• Hidden fields do not support rich structures as HTML hidden fields are only single valued. Then you have to work around with delimiters etc to handle complex structures.
Below is how you will actually implement hidden field in a project


<input id="Hidden Value" type="hidden" value="Initial Value" run at="server" NAME="Hidden Value">


What is View State?

View state is a built-in structure for automatically retaining values amongst the multiple requests for the same page. The view state is internally maintained as a hidden field on the page but is hashed, providing greater security than developer-implemented hidden fields do.


Does the performance for view state vary according to User controls?

Performance of view state varies depending on the type of server control to which it is applied. Label, Text Box, Check Box, Radio Button, and Hyper Link are server controls that perform well with View State. Drop Down List, List Box, Data Grid, and Data List suffer from poor performance because of their size and the large amounts of data making roundtrips to the server.


What are benefits and Limitation of using View state for state management?

Following are the benefits of using View state: -

• No server resources are required because state is in a structure in the page code.
• Simplicity.
• States are retained automatically.
• The values in view state are hashed, compressed, and encoded, thus representing a higher state of security than hidden fields.
• View state is good for caching data in Web frame configurations because the data is cached on the client.
Following are limitation of using View state:-
• Page loading and posting performance decreases when large values are stored because view state is stored in the page.
• Although view state stores data in a hashed format, it can still be tampered because it is stored in a hidden field on the page. The information in the hidden field can also be seen if the page output source is viewed directly, creating a potential security risk.

Below is sample of storing values in view state.


this. View State ["Enter Time"] = Date Time. Now. To String();


How can you use Hidden frames to cache client data?

This technique is implemented by creating a Hidden frame in page which will contain your data to be cached.

<FRAMESET cols="100%,*,*">
<FRAMESET rows="100%">
<FRAME src="data_of_frame1.html"></FRAMESET>
<FRAME src="data_of_hidden_frame. html">
<FRAME src="data_of_hidden_frame.html" frame border="0" no resize scrolling="yes">
</FRAMESET>


Above is a sample of hidden frames where the first frame “data_of_frame1.html” is visible and the remaining frames are hidden by giving whole col section to first frame. 100 % is allocated to first frame and remaining frames thus remain hidden.


What are benefits and limitations of using Hidden frames?

Following are the benefits of using hidden frames: -

• You can cache more than one data field.
• The ability to cache and access data items stored in different hidden forms.
• The ability to access JS crept ® variable values stored in different frames if they come from the same site.

The limitations of using hidden frames are: -

• Hidden frames are not supported on all browsers.
• Hidden frames data can be tampered thus creating security hole.


What are benefits and limitations of using Cookies?

Following are benefits of using cookies for state management: -
• No server resources are required as they are stored in client.
• They are light weight and simple to use


Following are limitation of using cookies: -
• Most browsers place a 4096-byte limit on the size of a cookie, although support for 8192-byte cookies is becoming more common in the new browser and client-device versions available today.
• Some users disable their browser or client device’s ability to receive cookies, thereby limiting the use of cookies.
• Cookies can be tampered and thus creating a security hole.
• Cookies can expire thus leading to inconsistency.


Below is sample code of implementing cookies

Request. Cookies. Add (New Http Cookie (“name”, “user1”))

What is Query String and What are benefits and limitations of using Query Strings?

A query string is information sent to the server appended to the end of a page URL.

Following are the benefits of using query string for state management: -
• No server resources are required. The query string containing in the HTTP requests for a specific URL.
• All browsers support query strings.

Following are limitations of query string: -
• Query string data is directly visible to user thus leading to security problems.
• Most browsers and client devices impose a 255-character limit on URL length.
Below is a sample “Login” query string passed in URL http://www.querystring.com/login.asp?login=testing.
This query string data can then be requested later by using Request.QueryString(“login”).


What is Absolute and Sliding expiration?

Absolute Expiration allows you to specify the duration of the cache, starting from the time the cache is activated. The following example shows that the cache has a cache dependency specified, as well as an expiration time of one minute.

Cache. Insert ("announcement", announcement, depends, _DateTime.Now.AddMinutes(1), Nothing)



Sliding Expiration specifies that the cache will expire if a request is not made within a specified duration. Sliding expiration policy is useful whenever you have a large number of items that need to be cached, because this policy enables you to keep only the most frequently accessed items in memory. For example, the following code specifies that the cache will have a sliding duration of one minute. If a request is made 59 seconds after the cache is accessed, the validity of the cache would be reset to another minute:


Cache.Insert("announcement", announcement, depends, _Date Time. Max Value, _TimeSpan.FromMinutes(1))


What is cross page posting?

Note: - This is a new feature available in ASP. NET 2.0.


By default, button controls in ASP. NET pages post back to the same page that contains the button, where you can write an event handler for the post. In most cases this is the desired behavior, but occasionally you will also want to be able to post to another page in your application. The Server. Transfer method can be used to move between pages, however the URL does not change. Instead, the cross page-posting feature in ASP .NET 2.0 allows you to fire a normal post back to a different page in the application. In the target page, you can then access the values of server controls in the source page that initiated the post back.

To use cross page posting, you can set the PostBackUrl property of a Button, Link Button or Image Button control, which specifies the target page. In the target page, you can then access the Previous Page property to retrieve values from the source page. By default, the Previous Page property is of type Page, so you must access controls using the Find Control method. You can also enable strongly-typed access to the source page by setting the @Previous Page Type directive in the target page to the virtual path or Type name of the source page.

Here is a systematic guide for implementing the cross-page post back using controls that implement the I Button Control interface.
• Create a Web Form and insert a Button control on it using the VS .NET designer.
• Set the button's PostBackUrl property to the Web Form you want to post back. For instance in this case it is "nextpage.aspx"


<asp: Button ID="Button1" run at="server" PostBackUrl="~/nextpage.aspx" Text="Post to next page" />

When the PostBackUrl property of the I Button Control is set, the ASP .NET framework binds the corresponding HTML element to new JavaScript function named Web Form _Do Post Back With Options. The corresponding HTML rendered by the ASP .NET 2.0 will look like this:


<input type="submit" name="Button1" value="Post to Page 2" on click="java script: Web Form_ Do Post Back With Options (new Web Form_ Post Back Options("Button1", ",false”,"Page2.aspx", false, false))" id="Button1" />


How do we access view state value of this page in the next page?

View state is page specific; it contains information about controls embedded on the particular page. ASP.NET 2.0 resolves this by embedding a hidden input field name, __POST BACK. This field is embedded only when there is an IButtonControl on the page and its PostBackUrl property is set to a non-null value. This field contains the view state information of the poster page. To access the view state of the poster page, you can use the new Previous Page property of the page:


Page poster = this. Previous Page;


Then you can find any control from the previous page and read its state:


Label poster Label = poster. find Control ("my Label"); string lbl = poster Label. Text;


This cross-page post back feature also solves the problem of posting a Form to multiple pages, because each control, in theory, can point to different post back URL.


Can we post and access view state in another application?

You can post back to any page and pages in another application, too. However, if you are posting pages to another application, the PreviousPage property will return null. This is a significant restriction, as it means that if you want to use the view state, you are confined, for example, posting to pages in the same virtual directory. Even so, this is a highly acceptable addition to the functionality of ASP.NET.


More ASP.NET Interview Questions & Answers here

Found this useful, bookmark this page to the blog or social networking websites. Page copy protected against web site content infringement by Copyscape

 Exclusive Interview Questions and Answers Categories