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 how do you deploy your asp.net application?

926

---

What is the difference between asp.net and mvc?

1120

---

What are the ways to sending the data in ASP.NET page?

1098

---

How many types of validators are there in asp net?

962

---

What is scope of an application variable in asp.net?

994

---

How to implement form based authentication in asp.net application?

1123

---

What is the difference between web config and machine config files?

1013

---

Explain different types of Caching techniques in ASP.NET?

1013

---

What is windows active directory authentication?

1063

---

Explain what is the procedure to create the environment for asp.net? : asp.net mvc

1039

---

What is difference between ispostback and autopostback in asp net?

1052

---

Where sessions are stored?

1103

---

What are the Difference between asp.net and asp ?

1155

---

What is cross page posting in asp net?

975

---

What is asp net_sessionid?

1104

---