Interested to Buy Any Domain ? << Click Here >> for more details...
Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 1916 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 |
Why do I get errors when I try to serialize a Hashtable
How we can add the CSS in ASP.Net MVC?
Can you explain the page life cycle of mvc?
What is .net framwork?
What is the domain object?
how do you truncate a table using entity data model?
Difference between ASP.NET MVC and ASP.NET WebForms?
What is the use of web api ? Why web api needed, if you have already restful services using wcf ?
What is the necessity for singning an assembly with a strong name?
If we write any code for DataGrid methods, what is the access specifier used for that methods in the code behind file and why?
what are the different stepts to create shared assemblies?
What are Scaffold templates in ASP.Net MVC?
Dot Net Framework 
