Do you need to dispose of objects and set them to null?

Question

Do you need to dispose of objects and set them to null, or will the garbage collector clean them up when they go out of scope?

Answer 1

I have to answer, too. The JIT generates tables together with the code from it's static analysis of variable usage. Those table entries are the "GC-Roots" in the current stack frame. As the instruction pointer advances, those table entries become invalid and so ready for garbage collection. Therefore: If it is a scoped variable, you don't need to set it to null - the GC will collect the object. If it is a member or a static variable, you have to set it to null