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 dot net compiled code will become platform independent?

513

---

What are type/key pairs in client script registration?

567

---

while developing webservices if i want some users to use my webservice only how can i give security to my webservice?

1411

---

Less than one page, how many windows will you be able to maintain?

567

---

How can we implement a identity (sql server) call in an asp.net page?

560

---

---

What is asp.net localization?

503

---

Explain what is clr?

628

---

What are the parts of an http response?

503

---

What is a proxy in web service?

561

---

How can we update records in gridview?Is there any appropriate code for it?

1608

---

How can we prevent browser from caching an aspx page?

531

---

Any disadvantages in Dataset and in reflection ?

2829

---

Is asp.net still used?

495

---

Which is the parent class of the ASP.NET server control?

543

---

What does the .webpart file do?

591

---