Is the lack of deterministic destruction in .NET a problem
Answer Posted / 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 |
Post New Answer View All Answers
What are html helpers in asp.net mvc?
What are the difference between asynchronous controller implementation between asp.net mvc 3 & asp.net mvc 4?
explain lazy loading, eager loading, and explicit loading?
Is dapper better than entity framework?
In razor syntax, what is the escape sequence character for @ symbol?
How large is the .net framework 3.0? Does this change make the release larger?
Explain tempdata in asp.net mvc?
How we can multiple submit buttons in ASP.Net MVC
Give an example for authorization filters in an asp.net mvc application?
Do you know about the new features in asp.net mvc 4 (asp.net mvc4)?
why DotNetFramework is included in building a software
What is difference between viewbag and viewdata and tempdata?
In .net compact framework, can we free memory explicitly without waiting for garbage collector to free the memory?
What is entity sql? : Entity framework
Explain the methods used to render the views in mvc?