Answer Posted / kishoreg

This is not a good and safe practice to call a Dispose.
In "Dot Net" it is automatically handle by Garbage
collection. It is the responsibility of GC to call the
Dispose and clear the memory.. but it is not sure that when
GC will call the Dispose.

so in that case we can forcefuly call it.

Consider one case when we forcefully destroy the object and
after some time i will try to use the same object at that
time u will get the error msg.

so better to object = null;

other material:
http://blogs.msdn.com/irenak/archive/2006/10/05/SYSK-
212_3A00_--Does-.NET-Garbage-Collector-call-Dispose_3F00_--
Dispose-_1320_-Best-Practices_2E00_.aspx

What is Implementation inheritance and interface inheritance?

926

---

How are delegates chosen?

837

---

How do I format in c#?

825

---

How do you comment out code in c#?

844

---

Is python easier than c#?

881

---

What is the difference between interface and abstract class in c#?

853

---

What is c sharp used for?

832

---

What is xaml file in c#?

899

---

Is Multiple-inheritance supported by c#?

931

---

Explain About delegates

970

---

What is deferred execution?

822

---

What is using in c#?

804

---

What is eager loading in c#?

837

---

Explain the difference between a Private Assembly and a Shared Assembly

904

---

What is the output of TextWriterTraceListener redirected?

994

---