Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 1543 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 |
can we call the garbage collector to run explicicitly?
what is entity graph in entity framework?
What is display mode in mvc?
what is conceptual model?
what is msl?
What is the 'page life cycle' of an ASP.NET MVC?
Explain the .net framework.
Can we access the web controls in a page pre initialising event?
mention what is code first approach and model first approach in entity framework?
How do assemblies find each other?
What is work of clr?
What is the difference between model and entity?
Dot Net Framework 
