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.

Can I create my own context attributes?

712

---

Explain cache? : Dot net architecture

747

---

where should I put this information then?

741

---

Explain the difference between primary & secondary storage device? : .NET Architecture

706

---

Explain difference between machine config vs. Web config? : .NET Architecture

705

---

Different types of authentication modes in .net framework ?

703

---

What is the .net class that allows the retrieval of a data element using a unique key?

737

---

What are bindings?

733

---

What is .net mobile images control. : Microsoft dot net mobile

672

---

Explain hard disk? : Dot net architecture

739

---

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

685

---

State and explain about microsoft.net?

689

---

What is the mesi? : .NET Architecture

765

---

How do I prevent concurrent access to my data?

727

---

i wish to write mcts(microsoft certified technology specialist) exam. can anyone give the model question or format and preparation method?

2495

---