Interested to Buy Any Domain ? << Click Here >> for more details...
Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 2003 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
What are the 3 main components of an asp.net mvc application?
What is the meaning of unobtrusive javascript? Explain us by any practical example.
Explain bundle.config in mvc4?
Explain unit test done by tester on development team?
What is viewbag?
What is clr? How does work clr & wht is work of clr?
What is .net core framework?
What is ado.net data provider? : Entity framework
Mention two instances where routing is not implemented or required?
What “beforFilter()”,“beforeRender” and “afterFilter” functions do in Controller?
How we can multiple submit buttons in ASP.Net MVC
What is needed for running an application built on winfx on the .net framework 3.0?
In Server how to check whether model has error or not in ASP.Net MVC
How to use Jquery Plugins in ASP.Net MVC validation?
Mention what is the difference between “ActionResult” and “ViewResult” ?
