Is the lack of deterministic destruction in .NET a problem
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 Reference type and value type
What is the difference between model and entity?
What is the use of trace utility ?
How to return the JSON from action method in ASP.Net MVC?
What is entity framework? : Entity framework
How to bind table colum with gridview column?
What is mapping in entity framework? : Entity framework
What are the sub types of ActionResult?
What is .net core framework?
Which is the best institute for .net?
What are Model Binders in ASP.Net MVC?
What's different about namespace declaration when comparing that to package declaration in Java ?