Interested to Buy Any Domain ? << Click Here >> for more details...
Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 2000 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 roles of clr in .net framework.?
What are the main components of .net framework?
What is viewdata?
Name a few different return types of a controller action method?
Explain Sections is ASP.Net MVC?
Is it possible to combine asp.net webforms and asp.mvc and develop a single web application?
What is .net architecture and framework?
Explain RenderBody and RenderPage in ASP.Net MVC?
explain lazy loading, eager loading, and explicit loading?
Do you know about the new features in ASP.Net MVC 4 ?
Is it possible to cancel filter execution?
explain what is ado.net entity framework?
Describe the .net framework architecture.
What is .net framwork?
What is display mode in mvc?
