title: Does the CLR garbage collection methodology mean it's safe to throw circular object references around?
body: <p>I have a theory that the CLR garbage collection mechanism means that I can get away with circular references in my object hierarchy without creating deadlocks for teardown and garbage collection. Is this a safe assumption to make? (Target language VB.NET)</p>