Is the lack of deterministic destruction in .NET a problem



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

Post New Answer

More Dot Net Framework Interview Questions

The order of the filters that get executed, if the multiple filters are implemented?

0 Answers  


What is razor code?

0 Answers  


Explain entity lifecycle? : Entity framework

0 Answers  


what is dot net? what is use dot net? what is benifit of dot net?what is vb dot net? what is ado dot net? what is c#?

0 Answers  


What is the difference between using system.net and system.net.sockets?

1 Answers  






Can a nested object be used in Serialization

1 Answers  


Describe the roles of clr in .net framework.?

0 Answers  


What is the role of the jit compiler in .net framework?

0 Answers  


How to bind table coloum with gridview column

3 Answers   Sypher Technologies,


Will c# 3.0, vb.net 9.0, atlas, or linq be included in the .net framework 3.0?

0 Answers  


Explain the advantage of packaging over xcopy in .net?

0 Answers  


What is ASP.NET MVC?

1 Answers  


Categories