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.

Distinguish between Server-side and Client-side code?

0 Answers   Siebel,

---

How do you handle session management in ASP.NET and how do you implement them. How do you handle in case of SQLServer mode ?

0 Answers   Microsoft,

---

what is narmalization

4 Answers   Wipro,

---

What is the difference between a session object and cache object

2 Answers   CitiGroup, PennyWise,

---

Difference between Htttppost and Httpget Methods?

3 Answers   Infosys, Microsoft,

---

a)COM Callable Wrapper b)Runtime Callable Which one of the above is Win32 API in .Net?

0 Answers   CTS,

---

what is wpf and wcf in .net explain with an example?

2 Answers  

---

What are typed datasets?

1 Answers   IBS,

---

what are the main advantage in .net?

4 Answers   TCS,

---

Explain the difference between value type and reference type?

0 Answers  

---

How do you identify that the page is postback?

0 Answers  

---

Differentiate between namespace and assembly.

0 Answers  

---