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 |
The order of the filters that get executed, if the multiple filters are implemented?
What is razor code?
Explain entity lifecycle? : Entity framework
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#?
What is the difference between using system.net and system.net.sockets?
Can a nested object be used in Serialization
Describe the roles of clr in .net framework.?
What is the role of the jit compiler in .net framework?
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?
Explain the advantage of packaging over xcopy in .net?
What is ASP.NET MVC?