Interested to Buy Any Domain ? << Click Here >> for more details...
Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 2079 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 |
What is serialization in .NET? What are the ways to control serialization?
What is difference between constants, readonly and, static
mention what is the key advantage of using entity framework or ef?
What is the difference between string and String
What are the types of assemblies
How to return the JSON from action method in ASP.Net MVC?
what is lazy loading in entity framework?
What is the meaning of unobtrusive javascript?
What is the domain object?
Explain encapsulation
1 Answers HPCL, Hughes Systique Corporation,
What is inline schema, how does it works
What are delegates?where are they used
Dot Net Framework 
