Why doesn't the .NET runtime offer deterministic destruction
Answer / kirti
Because of the garbage collection algorithm. The .NET garbage collector works by periodically running through a list of all the objects that are currently being referenced by an application. All the objects that it doesn't find during this search are ready to be destroyed and the memory reclaimed. The implication of this algorithm is that the runtime doesn't get notified immediately when the final reference on an object goes away - it only finds out during the next sweep of the heap.
Futhermore, this type of algorithm works best by performing the garbage collection sweep as rarely as possible. Normally heap exhaustion is the trigger for a collection sweep.
| Is This Answer Correct ? | 0 Yes | 0 No |
Define the core components of an ASP.NET MVC application?
I want to fetch data from datareader. i have three tables in datareader. i want to bind my two table with datagrid, then i want to fetch a value from my third table. do u have any idea pls help me. we use dr.nextresult() for multiple tables.
what is difference b/w .net 1.1 and .net 2.0. I need Answer in c# , asp.net and ado.net Level.Like c#1.1 and c#.1.1 , ado.net1.1 and ado.net2.0 and asp.net1.1 and asp.net2.0
Explain Keep method in Tempdata in ASP.Net MVC?
What is reflection?
5 Answers Accenture, Merrill Lynch, Microsoft,
what is connection pooling
What platforms does the .NET Framework run on?
In razor syntax, what is the escape sequence character for @ symbol?
Can we look at the IL for an assembly?
What is representational state transfer (rest) mean?
What is needed for running an application built on winfx on the .net framework 3.0?
Can you explain model, controller and view in mvc?