Have you enabled double buffering in your form? Do this in your initialisation (I put it in my Form constructor after the IntializeComonent() call. this.SetStyle(ControlStyles.DoubleBuffer | ControlStyles.UserPaint | ControlStyles.AllPaintingInWmPaint, true); this.UpdateStyles();

Actually I wrote the email after reading the Proramming for Garbage Collection article. I guess the reason why I need to Dispose() managed objects like Button() is if holds unmanaged resources, such as maybe icon, brush, etc. But now I realise that I probably don't need to call Dispose() directly on these controls, because when I call base.Dispose(bool) in the Dispose(bool) override that I have in my form, it will presumably call Dispose() for every control that it has (in the Controls collection). Other components such as Timer will be disposed when I call components.Dispose(). This is a guess, which I will verify later on.

According to MSDN doc, when I derive a class that implements IDisposable, I need to override protected virtual void Dispose(bool disposing). And in this function, if disposing is true, I need to call Dispose() on all managed objects that I own (in addition to releasing unmanaged resources). Now, when I create a new Form object, the wizard gives me the overridden Dispose(bool) method with the only statement being: if (disposing) { if (components != null) components.Dispose(); } base.Dispose(disposing); However, if I add a control, say a button named button1, it doesn't add the statement button1.Dispose() into the above method. Is this a mistake? I mean, do I need to manually add this statement, or is it already called implicitly somewhere?

What is the common practise of updating build and revision number if I want to increase it sequentially (i.e. not using the automatic VS.NET way) for every build? If I increase build number on every build, what about revision number? Does build number and/or revision number ever get reset to 0?

Thanks for the info. The problem I have is that I have a library project which gets referenced (yes, project reference) by some exe projects. Everytime I compile one exe project, the library project also gets compiled too. Isn't it better to use assembly references in this case? That way, I only build the library project whenever I change it?

Everytime I open up a C# project and click build, a new assembly gets created even if none of the source files and references are modified. However, once I build once, then for that session, any further build will not create a new assembly (unless I change something of course). How to make the first build after opening the project to also not build if nothing has changed?