Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 1231 Views
- I also Faced
- E-Mail Answers
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
How would you deploy your old applications with .net framework 4.0? Are the old applications compatible?
Why we need a separate mobile project template, while we can render our web application in mobile ?
how to disable the lazy loading framework?
Is .net core replacing .net framework?
What is presentation framework?
What is separation of concerns in asp.net mvc?
How does �side by side� work for the .net framework 3.0?
If I have multiple filters implemented, what is the order in which these filters get executed?
Explain JSON Binding?
Can you set the unlimited length for "maxjsonlength" property in config?
What is Layout in ASP.Net MVC?
How route table has been created in ASP.NET ASP.Net MVC?
Explain unit test done by tester on development team?
What are the differences between Partial View and Display Template and Edit Templates in ASP.Net MVC?
What is the version number for the next version of the .net framework, codenamed �orcas�?
