Interested to Buy Any Domain ? << Click Here >> for more details...
Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 1913 Views
- I also Faced
- E-Mail Answers
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 |
About .NET Framework ?
why DotNetFramework is included in building a software
How can I stop my code being reverse-engineered from IL
Explain Bundle.Config in ASP.Net MVC4?
What is asp net framework?
What is the full form of sp?
what is VSS? Where we are using?
Can two application one using private assembly and other using Shared assembly be stated as a side-by-side executables?
Why are there five tracing levels in System.Diagnostics.TraceSwitcher?
what is split entity?
How to update one of my table in database at 4pm every day how it is possible?
what do you mean by table-per-hierarchy?
Dot Net Framework 
