> I could be wrong but it seems to me that this is just an > issue with the way help files are generated.
Certainly docs can be/have been wrong, but if you're implying that maybe it's okay to skip calling EndInvoke because the docs I cited are wrong, it's not. Microsoft personnel have confirmed that the runtime "reserves the right" to leak if EndInvoke is not called. So I cited a spot in the 1.1 docs where they actually wrote it down as public confirmation of the private phone calls/emails I've been privy to off-list. So the error is that the 1.0 docs never mentioned this and that the 1.1 docs still don't mention it in the reference pages for the Delegate class (it's only mentioned in the context of the sample I cited). So I simply put the warning (and work around) out as a public service announcement :-), since I know that many people (myself included) have been using a fire-and-forget model for the last couple years now. -Mike DevelopMentor http://staff.develop.com/woodring
