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 |
In which circumstances you used delegates?
What is the difference between viewbag and viewdata in asp.net mvc?
What are actions in mvc?
Can I redirect tracing to a file
In razor syntax, what is the escape sequence character for @ symbol?
If you change something in web.config file.Do u need to compile again?
5 Answers Broadridge, SMNetserv,
What are the options can be configured in AJAX helpers?
Where are the value-type variables allocated in the computer RAM ?
What is the main difference between VS 2005 and VS 2003?
How can I tell what .net framework is installed?
Difference between manifest , metadata?
3 Answers Soma Technology, TCS,
How do you sort a dataset?