Answer Posted / skmdali786

ASP:

1)ASP 's Session State was stored in the same process that
hosts ASP.

2)for different web servers, each Web server had its own
session state.

There was a problem in sharing session states in a web farm
situation.

3)No support for Cookieless sessions.

4)No web.config files for configuring the session state.

ASP.NET:

1)ASP.NET 's Session State is stored in the same process
that hosts ASP.net(default)
It can also be stored out of process in an sql server
database or a state server

2)different web servers can easily share the session state
using the appropriate

configurations.

3)Supports Cookieless sessions.(<sessionState
cookieless=true/>) in web.config file.

SessionId is visible in the browser.

4)uses web.config files for configuring the seesion state.

What is meant by ispostback in asp net?

1019

---

What is the difference between the response.write() and response.output.write() methods?

968

---

Why would anyone need to implement their own hashtable or linked list?

2907

---

What are the parts of an http response?

913

---

Explain form level validation and field level validation?

956

---

What are the differences between clr & cts?

1008

---

What is the difference between executescalar and executenonquery?

951

---

What is difference between viewstate and session in asp net?

998

---

Explain file-based dependency and key-based dependency.

947

---

What is ispostback property?

871

---

Define transparent caching with aop?

1015

---

What is rich control in asp.net?

968

---

Explain the difference between singleton and single call?

937

---

How to prepare culture-specific formatting in .net.

977

---

What is the life cycle of web page?

915

---