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 |
Is entity framework slow?
Difference between manifest , metadata?
3 Answers Soma Technology, TCS,
Explain the difference between Viewbag and Viewdata in ASP.NET MVC?
What are bundling & minification features in asp.net mvc 4?
Explain ASP.NET MVC Identity and Security?
How does the 'page lifecycle' of asp.net mvc works?
what is difference b/w .net 1.1 and .net 2.0. I need Answer in c# , asp.net and ado.net Level.Like c#1.1 and c#.1.1 , ado.net1.1 and ado.net2.0 and asp.net1.1 and asp.net2.0
What is presentation framework?
In which circumstances you used delegates?
What is the need of .Net framework ?
What is the full form of sp?
What is the use of web api ? Why web api needed, if you have already restful services using wcf ?