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.

Explain is development of a mobile web application with asp.net is very easy? : Microsoft dot net mobile

944

---

Explain about cookie less session state? : .NET Architecture

969

---

I want to create a project like google maps how can we do that with atlas?

941

---

How to develop mobile applications using microsoft mobile internet toolkit (mmit) or .net mobile? : Microsoft dot net mobile

938

---

Explain the process of gc?

978

---

what is polymorphism and advantage ?

1986

---

How do we do authentications using atlas?

969

---

When do I need to use gc.keepalive?

1065

---

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

930

---

Define domestic architecture artifacts? : Dot net architecture

902

---

What is .net mobile lists. : Microsoft dot net mobile

947

---

Explain the types of memory management? : Dot net architecture

944

---

So what exactly is the configuration file for then?

963

---

Explain element .net mobile with example? : Microsoft dot net mobile

980

---

What is IL code, CLR, CTS, GAC & GC?

1028

---