Answer / arjun jaiswal

Dll Hell refers to a set of problems caused when multiple
applications attempt to share a common component like a
dynamic link library (DLL). The reason for this issue was
that the version information about the different components
of an application was not recorded by the system.

.Net Framework provides operating systems with a Global
Assembly Cache. This Cache is a repository for all the .Net
components that are shared globally on a particular
machine. When a .Net component is installed onto the
machine, the Global Assembly Cache looks at its version,
its public key, and its language information and creates a
strong name for the component. The component is then
registered in the repository and indexed by its strong
name, so there is no confusion between different versions
of the same component, or DLL.

Answer / imtiyaz chanderki

Windows Registry can not support the multiple versions of
same com component this is called the dll hell problem.

Dll hell problem is solved by dotnet it allows the
application to specify not only the library it needs to
run but also the version of the assembly

Answer / vimal victor

DLL Hell :- This is a problem in loading a specific dll
(class id, version number, path etc). For example, if I
build test.dll v1.0.0.0 and deploying it in c:\MyProg. My
application App1 and App2 are using the methods in that
dll. And there is a requirement to change something in App1
and I supposed to change test.dll also for the same
requirement. Once I finished with all my changes, I will be
deploying them in the appropriate locations. Now, the older
dll will be overwritten. And my App2 will look for test.dll
of older version and since it is not there it will not
work. This is a scenario for dll hell issue.

.NET and dll hell:- .NET has a provision to specify whether
a 'Specific Version' to be loaded or not. If you check with
any dll's propery window, that has a property called
Specific Version. By default it will be false for the dll's
created by users. It means whether the specific version
alone has to be loaded for that project. If that is false,
then te runtime will load any available higher version of
dll for that project. Thus this issue has been sorted out.

Answer / dhana

.net solved using dll with different versions

Answer / robert

DLL Hell :- This is a problem in loading a specific dll
(class id, version number, path etc). For example, if I
build test.dll v1.0.0.0 and deploying it in c:\MyProg. My
application App1 and App2 are using the methods in that
dll. And there is a requirement to change something in App1
and I supposed to change test.dll also for the same
requirement. Once I finished with all my changes, I will be
deploying them in the appropriate locations. Now, the older
dll will be overwritten. And my App2 will look for test.dll
of older version and since it is not there it will not
work. This is a scenario for dll hell issue.
.Net Framework provides operating systems with a Global
Assembly Cache. This Cache is a repository for all the .Net
components that are shared globally on a particular
machine. When a .Net component is installed onto the
machine, the Global Assembly Cache looks at its version,
its public key, and its language information and creates a
strong name for the component. The component is then
registered in the repository and indexed by its strong
name, so there is no confusion between different versions
of the same component, or DLL.

Answer / kobra thakur

Registry of operating system is unable to support the
multiple versions of
same com component this is called the dll hell problem.

Dll hell problem is solved by dotnet it allows the
application to specify not only the library it needs to
run but also the version of the assembly

Answer / moinuddin

Over the history of Windows, the method of tracking of DLL
usage was changed by Microsoft several times, as well as
the problem of rogue
installations that didn't play by the rules--the result was
called "DLL HELL", and the
user was the victim.
Solving DLL hell is one thing that the .NET Framework and
the CLR targeted. Under
the .NET Framework, you can now have multiple versions of a
DLL running
concurrently. This allows developers to ship a version that
works with their program
and not worry about stepping on another program. The
way .NET does this is to
discontinue using the registry to tie DLLs to appliction
and by the concept of assembly

Answer / parthasarathi

Global assembly Cache (GAC) is a repository for all the .Net components or dll that are shared globally on a particular machine. When a .Net component or dll is installed onto the machine, the Global Assembly Cache looks at its version, its public key, and its language information and creates a strong name for the component or dll. The component or dll is then registered in the GAC and indexed by its strong name, so that even with same name of assembly could be install to GAC that will be having two different versions. Once versioning done with any assembly there will be no chance to conflict, which was earlier happening (DLL HELL).

Answer / sabari

DLL Hell is nothing but overwriting the dll in the registery. If two application are installed on a single server, one installed First and the Second Installed Later and There is a dll with same name with different functionality used in both the applications, So in this case Application one works fine all the days until application two Installed on the machine. Once the Application two is installed containing the DLL with the same name as Application one Contains then In this case the application one Fails as the DLL from Application two overwites the DLL of Application one in the Registery. So Application two works fine where as Application one Fails as the DLL is missing.

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

How does session work in asp net?

1 Answers  

What events will occur when a page is loaded?

1 Answers  

I have a method written in WebForm (means .aspx page) & now I want to call this method in WebUserControl (means .ascx page) what should I have to do?

1 Answers   Patni,

define silverlight and advantages ?

3 Answers   QA,

How do you associate two or more validators with a single input control? What do you need to do to prevent space from being reserved for a validation control thatpasses its validation test?

1 Answers  

what is session,cokkies in asp.net??

5 Answers  

Where is http session stored?

1 Answers  

What is base class of .net?

1 Answers  

Why session is necessary in web application?

1 Answers  

What Name space does the web page belon in the .net framework class hierarchy?

1 Answers   L&T, Wipro,

Explain login control and form authentication.

1 Answers  

what is silver light when will we use silver light,

1 Answers