How does assembly versioning in .NET prevent DLL Hell?
- 3 Answers
- 14780 Views
- Satyam, Siebel Systems, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / sivaraj.t
here is the answer : : :
The runtime checks to see that only one version of an
assembly is on the machine at any one time.
.NET allows assemblies to specify the name AND the version
of any assemblies they need to run.
The compiler offers compile time checking for backward
compatibility.
It doesn.t.
| Is This Answer Correct ? | 26 Yes | 0 No |
Answer / sathiya
Using Zero impact deployment in .Net to prevent the DLL
Hell Proplem.
| Is This Answer Correct ? | 11 Yes | 2 No |
Answer / himanshu raj
dll hell problem occurs due to more than one assembly being used for single application. How the applic ation will know which assembly to use? Assembly name and number that is version is specified so that the application can use specific assemblies.
| Is This Answer Correct ? | 1 Yes | 4 No |
How do you register a .NET assembly?
How do you reference to a private & shared assembly ?
Explain the differences between marshal by value and marshal by reference?
what are the requirements to enable remote components to interact each other?
What do you mean by windows authentication?
what are the various type of channels used by .Net remoting and which is the best one?
What security measures exist for .NET Remoting in System.Runtime.Remoting?
What is boxing and unboxing ?
4 Answers Amdocs, BirlaSoft, TCS,
explain is .NET Remoting?
Define singleton activation mode in .net remoting?
What are channels in .NET Remoting?
What is fundamental of published or precreated objects in remoting?
Dot Net Framework 
