Answer / 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 are custom user controls in asp.net?

0 Answers  

---

Is post back property in asp net?

0 Answers  

---

What are the page life cycle events?

0 Answers  

---

What is preprocessor in .net and type, where it use?

0 Answers  

---

Why we use dbms for projects? Why don’t we save any application data in separate files instead of dbms?

0 Answers  

---

---

difference between Trace and Debug ?

2 Answers   Accenture, HCL, Patni,

---

How will you maintain versioning in asp.net 2.0?

0 Answers   MCN Solutions,

---

Explain what is an abstract class?

0 Answers  

---

What is web.config. How many web.config files can be allowed to use in an application?

6 Answers   Accenture, HCL, InterGraph, iSoft,

---

what is view stat? how it is use.

3 Answers   TCS,

---

What is a session http?

0 Answers  

---

What is smpte vc-1?

0 Answers  

---