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

Do you know about the new features in asp.net mvc 4 (asp.net mvc4)?

0 Answers  


what is entity graph in entity framework?

0 Answers   Microsoft,


what are partial classes?

12 Answers   Digimaker, HP, N Tech, TCS,


What are the components required to create a route in mvc?

0 Answers  


Explain RenderBody and RenderPage in ASP.Net MVC?

0 Answers  






Why is the .net framework 3.0 a major version number of the .net framework if it uses the .net framework 2.0 runtime and compiler?

0 Answers  


sql related question (outer join, left, right etc) array vs hashtable CRL sqldatareader vs dataset what is WPF, WCF, compare to WinForms Webservices Asp.net MVC vs WebForms?

0 Answers   Avanade,


Iam using an asp.net application . i want to update one of my table in database at 4pm every day how it is possible.

6 Answers   ABC, Evalueserve,


What are the main features of asp.net mvc 4 used by asp.net web api?

0 Answers  


what is ADO.NET

8 Answers   NIIT,


Explain JSON Binding?

0 Answers  


Where are the value-type variables allocated in the computer RAM ?

1 Answers  


Categories