Answer Posted / moinuddin

Over the history of Windows, the method of tracking of DLL
usage was changed by Microsoft several times, as well as
the problem of rogue
installations that didn't play by the rules--the result was
called "DLL HELL", and the
user was the victim.
Solving DLL hell is one thing that the .NET Framework and
the CLR targeted. Under
the .NET Framework, you can now have multiple versions of a
DLL running
concurrently. This allows developers to ship a version that
works with their program
and not worry about stepping on another program. The
way .NET does this is to
discontinue using the registry to tie DLLs to appliction
and by the concept of assembly

Explain the difference between singleton and single call?

1039

---

Explain the difference between array and linkedlist?

1052

---

Can you change a master page dynamically at runtime? How?

984

---

How does u get record no from 5 to 15 from a dataset of 100 records?

1015

---

What is http session state?

1029

---

What is the asp.net mvc folder conventions? : asp.net mvc

960

---

What are sql joins?

1056

---

Explain difference betn dataset and recordset?

990

---

Differentiate strong typing and weak typing

1006

---

What is data reader in asp.net?

1248

---

How is a session stored and maintained in asp.net?

1048

---

Explain the steps to be followed to use passport authentication.

1092

---

What is the difference between WindowsDefaultLocation and WindowsDefaultBounds?

1219

---

What is HTTPModule and HTTPcontext? What is the use of each?

2676

---

What is query string in asp.net?

1121

---