EndInvoke () - optional or not?

Question

Asynchronous question:

I have read many articles over the Internet for and against Delegate.EndInvoke (), which is optional. Most of these articles are 4-5 years old. Lots of dead links.

Can someone explain in .NET 2.0 is EndInvoke (), really preventing a memory leak otherwise, and if so, can you indicate what causes this leak?

In the same question: if EndInvoke () is really mandatory - I find the best way to implement the Fire-and-forget mechanism using the callback method that runs EndInvoke (). I would like to hear from everyone who thinks otherwise.

Thanks oh

Answer 1

Delegate.EndInvoke, . Control.EndInvoke WinForms , . WPF, , , , .

" " - ( "" ).

Answer 2

msdn:

EndInvoke, .

, , .