Answer Posted / libin

"DLL Hell" refers to the set of problems caused when
multiple applications attempt to share a common component
like a dynamic link library (DLL) or a Component Object
Model (COM) class. In the most typical case, one
application will install a new version of the shared
component that is not backward compatible with the version
already on the machine. Although the application that has
just been installed works well, existing applications that
depended on a previous version of the shared component
might no longer work. In some cases, the cause of the
problem is even more subtle. In many cases there is a
significant delay before a user discovers that an
application has stopped working. As a result, it is often
difficult to remember when a change was made to the machine
that could have affected the application. A user may
remember installing something a week ago, but there is no
obvious correlation between that installation and the
behavior they are now seeing. The reason for these issues
is that version information about the different components
of an application aren't recorded or enforced by the
system. Also, changes made to the system on behalf of one
application will typically affect all applications on the
machine.

What is a session http?

521

---

Which is better viewstate or session?

521

---

Can I tap into other windows livetm services?

572

---

Explain the use of dataadapter.

581

---

Why cyclomatic complexity is important?

564

---

---

What is the difference between response.redirect and server.transfer?

538

---

What is server side session management?

530

---

Is asp.net and .net the same?

516

---

What can we do with asp.net?

516

---

Which is faster viewdata or viewbag?

546

---

What is web router?

505

---

Where you store Connection string in "Web.Config" file in ASP.NET?

586

---

In which event of the page viewstate is available?

470

---

Describe paging in asp.net?

678

---

Describe the disadvantage of cookies.

599

---