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 data type should you use if you want an 8-bit value that's signed ?
What is Global Assembly Cache (GAC) and what is the purpose of it?
What are the levels at which filters can be applied in an asp.net mvc application?
Explain what platforms does the .net framework run on?
Can we add constraints to the route? If yes, explain how we can do it?
What is .net framework & its benefits?
What are the 2 popular asp.net mvc view engines?
In which assembly is the mvc framework defined?
what is way of loading data in ef (entity framework)?
What symbol would you use to denote, the start of a code block in razor views?
Why is XmlSerializer so slow
How route table is created in ASP.NET MVC?