Answer / sunil yadav

Once I’ve got a task to solve the problem with the DLL updates. Some company supplied users with DLLs that contained classes that developers used in their C++ applications. In other words, it was some kind of a SDK in the DLL. There were no restrictions on how to use these classes, so developers derived from them while creating their applications. Soon they realized that their applications started to crash after the DLL updates. Developers were required to rebuild their applications to get versions that can work with the new DLL.

Further I will provide you with my research results on this problem, with the information I have gathered from the external sources and finally I will give my solution for one of the ‘DLL Hell’ problems.

Answer / narendra

EARLY TO .NET IF YOU WANT TO USE ANY DLL IT WAS REQUIRED TO FOLLOW 3 STEPS 1)COPY THE DLL 2)REGISTER THE DLL WITH REGISTRY 3)CONSUME THE DLL
WHEN DLL IS REGISTER WITH REGISTRY THE REGISTRY CONTENTS CAN BE MODIFIED BY UNKNOWN PERSONS OR HACKERS OR INTRUDER THEN THE RESPECTIVE DLL WILL NOT WORK PROPERLY RATHER IT WILL CREATES MANY PROBLEMS THESE PROBLEMS ALONG WITH VERSIONING PROBLEM KNOWN AS DLL

Answer / kamlakar singh

DLL Hell refers to the set of problems caused when multiple applications attempt to share a common component like a dynamic-link library (DLL) or a Component Object Model (COM) class. In the most typical case, one application will install a new version of the shared component that is not backward compatible with the version already on the machine. Although the application that has just been installed works fine, existing applications that depended on a previous version of the shared component might no longer work. In some cases, the cause of the problem is even more subtle.
full implementation of dll hell problem go here :
http://www.mindstick.com/blog/507/DLL%20HELL%20Problem%20in%20Net

Answer / nir

i don't know the correct answer, please send to me the
correct answer.

Answer / srinivas.t

windows applications use some shared DLLs. suppose
application1 is using the shared dell(named as Mydll.dll
which is installed when the application1 installed in to
the system), consider we need another applications called
application2 it is also having a shared dll(named as
Mydll.dll)and this application2 mydll.dll will repalce the
application1 MYdll.dll.

but the implementation of mydll.dll may be different in the
two applications. so that dll is not work properly. this is
called the DLL HEll.

.net gave a solution to this problem by giving the strong
name to the shred assemblies and it allows the side by side
execution.

go with this link for more details
http://msdn.microsoft.com/en-us/library/ms973843.aspx

Answer / maheswaran

App.domain through solve the DllHell problem

Answer / pradeepn gupta

"DLL Hell" refers to the set of problems caused when
multiple applications attempt to share a common component
like a dynamic link library (DLL) or a Component Object
Model (COM) class. In the most typical case, one application
will install a new version of the shared component that is
not backward compatible with the version already on the
machine. Although the application that has just been
installed works well, existing applications that depended on
a previous version of the shared component might no longer
work. In some cases, the cause of the problem is even more
subtle. In many cases there is a significant delay before a
user discovers that an application has stopped working. As a
result, it is often difficult to remember when a change was
made to the machine that could have affected the
application. A user may remember installing something a week
ago, but there is no obvious correlation between that
installation and the behavior they are now seeing. The
reason for these issues is that version information about
the different components of an application aren't recorded
or enforced by the system. Also, changes made to the system
on behalf of one application will typically affect all
applications on the machine.

One reason why it was hard to build an isolated application
was the run-time environment typically allowed the
installation of only a single version of a component or an
application. This restriction means that component authors
must write their code in a way that remains backward
compatible, otherwise they risk breaking existing
applications when they install a new component. In practice,
writing code that is forever backward compatible is
extremely difficult, if not impossible. Also components were
shared because disk space and memory was expensive. In the
past few years, hard disk and memory prices have dropped
dramatically, and disk space is no longer a premium. But as
applications have increased in size and in modularity not so
long ago many applications were entirely self-contained in a
single .exe file - the DLL sharing issue has not been
addressed, and the problem has grown over time.

Answer / libin

"DLL Hell" refers to the set of problems caused when
multiple applications attempt to share a common component
like a dynamic link library (DLL) or a Component Object
Model (COM) class. In the most typical case, one
application will install a new version of the shared
component that is not backward compatible with the version
already on the machine. Although the application that has
just been installed works well, existing applications that
depended on a previous version of the shared component
might no longer work. In some cases, the cause of the
problem is even more subtle. In many cases there is a
significant delay before a user discovers that an
application has stopped working. As a result, it is often
difficult to remember when a change was made to the machine
that could have affected the application. A user may
remember installing something a week ago, but there is no
obvious correlation between that installation and the
behavior they are now seeing. The reason for these issues
is that version information about the different components
of an application aren't recorded or enforced by the
system. Also, changes made to the system on behalf of one
application will typically affect all applications on the
machine.

Answer / gaurav

the hell dll problem , is genenerally occurs in vs.6.
can also called mismatched .dll file or mismatched .ocx
file (active x control).
when os xp is installed the active x sdk(software
development toolkit)& MFC (microsoft foundation classes ).
MFC40.dll is installed . In vs6 application develpoed
will use MFc42.dll. & when the application is installed in
default os , MFC42.dll will be not found & the dll problem
will happen.or HELL DLL PROBLEM -VERSION CONFLICT.
@ dat time we have to paste MFC42.dll in win.system32 .
folder & the problem will be solved . but in earlier
versions this problem has been sorted out.

Answer / kureshi salman

DLL HELL refers to the set of problems caused when multiple
application attempt to share a common component like DLL.In
VB6 there are many DLL,Hence the programmer confused which
DLL he wants to update this situation made a s/w or product
failure.


You can avoid this problem in .net using a s/w recompiling
due to recompiling the program ,a DLL is automatically
updated.If the s/w is deployed on a machine,then You can
avoid this problem in .net using a s/w reinstalling the
program a DLL is automatically updated.

What are the file extensions for razor views?

0 Answers   NA,

Explain how does asp page work?

0 Answers  

Describe the Server Control Events of ASP.NET?

0 Answers   SwanSoft Technologies,

For which does this Codebehind="MyCode.aspx.cs" is relevent to ?

0 Answers   Siebel,

Is asp.net mvc still used? : Asp.Net MVC

0 Answers  

About delegates ?

7 Answers   TCS,

Explain asp.net web forms.

0 Answers  

What is marshalling ? Is it a part of asp.net ?

0 Answers   MCN Solutions,

benefits of migration from asp to asp.net hi frnds, i have to give presentation to a client about how useful would be migrating their project from asp to asp.net .plz give me some points which i should incorporate in my ppt thanks

0 Answers  

What is Hidden Fields in Asp.Net

4 Answers  

What is gacutil.exe? Where do we store assemblies, Should sn.exe be used before gacutil.exe?

2 Answers   Accenture, Aptech,

User contro having 4 text boxes given validation controls. i want to execute validations after the button click event how it is?

3 Answers