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 is IPostBack? How to use it?

0 Answers   MCN Solutions,

---

What will happen if the server confugration file and the application confugration file have different values for sassion state ASP.NET?

0 Answers   HCL,

---

What is localhost in asp.net?

0 Answers  

---

How to implement globalization and localization in the use interface in .net.

0 Answers  

---

What tags do you need to add within the asp:datagrid tags to bind columns manually? How?

0 Answers  

---

What is validation in asp.net?

0 Answers  

---

How do you do Client-side validation in .Net?

0 Answers  

---

What is a PostBack? What is ViewState? How is it encoded? Is it encrypted? Who uses ViewState? Why is it either useful or evil?

3 Answers   TCS,

---

What is the relationship between IIS and ASP.NET in the generation of dynamic Web sites?

1 Answers  

---

What does aspnet_regiis -i do ?

1 Answers  

---

How Can we use multiple forms in single asp.net application?

3 Answers   Polaris,

---

Can the unique key be null?

0 Answers  

---