Interested to Buy Any Domain ? << Click Here >> for more details...
Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 1999 Views
- I also Faced
- E-Mail Answers
Answer / kirti
It's certainly an issue that affects component design. If you have objects that maintain expensive or scarce resources (e.g. database locks), you need to provide some way for the client to tell the object to release the resource when it is done. Microsoft recommend that you provide a method called Dispose() for this purpose. However, this causes problems for distributed objects - in a distributed system who calls the Dispose() method? Some form of reference-counting or ownership-management mechanism is needed to handle distributed objects - unfortunately the runtime offers no help with this.
| Is This Answer Correct ? | 0 Yes | 0 No |
What is Area in ASP.Net MVC?
If we write return statement in finally block will it works fine or throws any error?
What are the types of assemblies
What are the versions of .net framework?
what is dot net? what is use dot net? what is benifit of dot net?what is vb dot net? what is ado dot net? what is c#?
If Controller is not there in MVC Pattern what happens?
How OS come to know whether to load the .net framework when we run an .exe created using .Net framework?
Does the .NET Framework have in-built support for serialization?
Which is the root namespace for fundamental types in .net framework?
About .NET Framework ?
What is GC (Garbage Collection) and how it works
What is reflection?
5 Answers Accenture, Merrill Lynch, Microsoft,
Dot Net Framework 
