If we not suppress finalize method in dispose what will happen?
Answers were Sorted based on User's Feedback
Answer / answerme
If we do not suppress finalize method in dispose, the
finalise method will be called twice by the garbage
collector. Once the method that is called by the developer
and once when the GC runs for checking the object that are
out of scope. This hampers the performance and is heavy on
performance.
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / seema dalal
Dispose methods can be called automatically, if client
forget to call it.
for this ,Call the Dispose method in Finalize method and in
Dispose method suppress the finalize
method using GC.SuppressFinalize. Below is the sample code
of the pattern. This is the
best way we do clean our unallocated resources and yes not
to forget we do not get the hit
of running the Garbage collector twice.
Public Class ClsTesting
Implements IDisposable
Public Overloads Sub Dispose()Implements IDisposable.Dispose
' write ytour clean up code here
GC.SuppressFinalize(Me)
End Sub
Protected Overrides Sub Finalize()
Dispose()
End Sub
End Class
| Is This Answer Correct ? | 0 Yes | 4 No |
what is ADO.NET
My organization went through the approval process of supporting the .net framework 2.0 in production. Do we need to go through the same process all over again for the .net framework 3.0? Do I need to do any application compatibility testing for my .net framework 2.0 applications?
What are the mobile devices supported by .net platform
Which is the best institute for .net?
Have you designed any components?
What is the difference between model view and controller?
How do you handle variable number of segments in a route definition?
What are the Main Features of .NET platform
how can you enhance the performance of entity framework?
When was the first version of .NET released
Is dapper better than entity framework?
What is route config?