Constructor and Destructor

Thanks.....

Hi vineet,


Please refer Our recommended articles section.


Thanks

There can be at most one destructor. Also see Destructor Syntax in C# and C++ which says "Managed code does not support anything similar to C++ destructor semantics.". The C# language and .Net uses garbage collection, to make programming easier. As a result, destruction can be very confusing and difficult to get right without spending a lot of time studying how to do it.

The important thing is that most classes do not need a desctructor. There is also the IDisposable inerface and the Finalize method; they are also not needed for most things. Also, developers experienced with C++ but not C# have a tendency to call GC.Collect when they don't need to.

The most likely palces that things like that are needed is when a class calls unmanged code. Managed classes will take care of themselves.

I assume you are familiar with C++, which is very precise about destruction. C# is quite imprecise about destruction and you must accept that.

Hi Vineet,

Please refer to this article on C# Corner:

http://www.c-sharpcorner.com/UploadFile/rajeshvs/ConsNDestructorsInCS11122005010300AM/ConsNDestructorsInCS.aspx