I have a user control (A) that contains children of another type of user control (B). Now I've added code in the A.Dispose() to remove the B children. The problem is that about 1 in 100 occurence of running this Windows app, I get the error of my app trying to reference a B that's already disposed. The error happens randomly, so I cannot replicate the error by doing a certain step. So I'm supposing that I'm not disposing my controls correctly.

Could someone please help tell me if there is a correct procedure of disposing of dynamically created controls? Thanks.

 Omar, I'm not sure if I've been able to get in on the ground floor of this issue with the
provided information, because all I have is a Control called A and its children so
intuitively named Bs. :)

 But it could be a problem stemming from the Garbage Collection’s nature of happening at
'its own will', and even if your program has officially disposed off the objects, its at
this stage that the objects actually gets destroyed .

 I think if you just force the garbage collection once you are through with Bs you will
be more sure of when you 'dont have' those objects anymore.

 You can force the garbage collections with

   System.GC.Collect


Regards
Ankur Verma

Thanks Verma.

I suspect it's a Garbage collector problem too. That's why I wonder if I should dispose the children controls myself or just let the GC do it when the parent control gets disposed of.