A good reason for calling GC.Collect()

A good reason for calling GC.Collect()http://blogs.msdn.com/ddietric/archive/2007/09/23/a-good-reason-for-calling-gc-collect.aspxYou've probably heard that you should not call GC .Collect() and generally speaking this is absolutely correct. Yes, there are probably exceptions to that rule but unless you know for sure that calling GC .Collect() will improve the runtime behavior ofen-USCommunityServer 2.1 SP1 (Build: 61025.2)A good reason for calling GC.Collect()http://blogs.msdn.com/ddietric/archive/2007/09/23/a-good-reason-for-calling-gc-collect.aspx#5093906Mon, 24 Sep 2007 13:02:45 GMT91d46819-8472-40ad-a661-2c78acb4018c:5093906DotNetKicks.com<p>You've been kicked (a good thing) - Trackback from DotNetKicks.com</p> Additional information on the garbage collector and weak referenceshttp://blogs.msdn.com/ddietric/archive/2007/09/23/a-good-reason-for-calling-gc-collect.aspx#5217685Mon, 01 Oct 2007 05:57:08 GMT91d46819-8472-40ad-a661-2c78acb4018c:5217685Dennis "D.C." Dietrich<p>I received some feedback on my previous post A good reason for calling GC.Collect() basically saying</p>