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 are the events for a form?

2092

---

What is .net mobile utility controls. Explain with an example? : Microsoft dot net mobile

878

---

What is difference between Desktop, Client Server & Web based applications?

1050

---

Define the mesi? : Dot net architecture

938

---

Define a virtual memory? : Dot net architecture

915

---

I can't be bothered with cas. Can I turn it off?

929

---

What is private constructor? And it's use?

1124

---

Does application frame need host?

951

---

How to improve the cache performance? : Dot net architecture

929

---

Why the config file might not be writable

1136

---

Explain the five stages in a dlx pipeline? : Dot net architecture

932

---

Explain the race around condition? : .NET Architecture

1014

---

What is the difference between primary & secondary storage device? : Dot net architecture

970

---

What is .net mobile input validation. : Microsoft dot net mobile

935

---

Explain COM with example?

955

---