Answer Posted / guest

DLL hell is not the problem of dot net. Dot net provided
solution for it.
DLL Hell: In windows applications some dlls are shared
ones. Suppose app1 is an application running perfectly. It
is sharing a shared dll named shared1.dll. You are
installing another application app2. Suppose app2
application is also having a shared dll named shared1.dll.
At the time of app2 installation, installer will overwrite
the shared1.dll which is already there on our system and
being shared by app1. The new shared1.dll may be different
than the previous dll which is overwritten. Now the
application app1 which is depending on overwritten
shared1.dll will become defunct. app1 will fail.
that's all about dll hell.

Dot net shared assemblies are strongly named. Different
assemblies with same name but with different version
numbers may coexist in shared folders.
This is the solution provided by dot net.

what is the method while we are using adapter and dataset ?

1386

---

Explain 'managed' mean in the .NET context

706

---

Xmlserializer is throwing a generic "there was an error reflecting myclass" error. How do I find out what the problem is?

556

---

4. Wcf- what Asych and Sych call and how that works

1457

---

What is a managed code? : Dot net architecture

567

---

---

difference between Response.write,server.transfer and also which one is used when ?

1477

---

Do you know textbox and textview controls of .net mobile? : Microsoft dot net mobile

521

---

Can you explain scriptmanager control?

548

---

Explain about common language infrastructure?

574

---

readonly syntax ?

1425

---

Difference between throw exception and rethrowing ?

1682

---

What is an interrupt? : Dot net architecture

524

---

Explain the purpose of cache? How is it used? : Dot net architecture

554

---

Explain difference between inprocess vs out process session state? : .NET Architecture

558

---

What other than biginteger has been introduced in system.numerics namespace?

545

---