Interested to Buy Any Domain ? << Click Here >> for more details...
Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 1982 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
Describe the .net framework architecture.
What is the 'page life cycle' of an ASP.NET MVC?
Can you explain the page life cycle of mvc?
Is .net framework 4.8 the last version?
Does .NET Framework support SAX?
What are html helpers in asp.net mvc?
Describe the roles of clr in .net framework.?
What are Action Filters in ASP.NET MVC and its use?
What is separation of concerns in asp.net mvc?
what is eager loading?
What is associationset? : Entity framework
what is entity graph in entity framework?
Explain RenderBody and RenderPage in ASP.Net MVC?
what is ssdl?
What filters are executed in the end?
