Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / anisha
DLL HELL was there in earlier version of .Net .With the
latest Version .Net handles this automatically.
It arised due to two main reasons.:-
1.> While the dll are named the name may match with those
existing by default in windows folder or if the dll has not
been updated after adding an additional functionality then
the application will throw error and this resulted in DLL
hell.This can be avoided by either updating the DLL or by
changing the version in web.config through strong tag.
2.> There may be a side effect with dll as particular
memory reference may get deleted then the application will
throw error and result in DLL hellas it wont get that
referenced memory required in the application
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
How response object is related to asp's response object?
Is asp.net different from asp? If yes, explain how?
Explain the path instructions in xaml?
Give an example of what might be best suited to place in the application_start and session_start subroutines?
What are validator? How do you disable them?
what is loosely coupled solution? How it can be used?
What are different methods of session maintenance in asp.net?
How do we assign page-specific attributes?
Explain the difference between or and orelse?
I’m having some trouble with cas. How can I diagnose my problem?
How do I debug an asp.net application that was not written with visual studio.net and that does not use code-behind?
How do we ensure view state has not tampered?
What is the life cycle of web page?
Should I delete cookies?
How many validators do ASP.NET have?
