begininvoke

This page in the MS documentation , covering asynchrony in Windows Forms applications, states: You can call EndInvoke to retrieve the return value from the delegate, if neccesary, but this is not required. (emphasis added) This page covering the general case of asynchronous delegates , states something different: No matter which technique you use, always call EndInvoke to complete your asynchronous call. These two seem to be in direct conflict. Which is true? Can someone explain? see also, a post by Phil Haack . Related: Is EndInvoke optional, sort-of optional, definitely not optional? Unless

I'm trying to call System.Windows.Threading.Dispatcher.BeginInvoke . The signature of the method is this: BeginInvoke(Delegate method, params object[] args) I'm trying to pass it a Lambda instead of having to create a Delegate. _dispatcher.BeginInvoke((sender) => { DoSomething(); }, new object[] { this } ); It's giving me a compiler error saying that I can't convert the lambda to a System.Delegate. The signature of the delegate takes an object as a parameter and returns void. My lambda matches this, yet it's not working. What am I missing? Reed Copsey Since the method takes a System.Delegate ,

I've this little method which is supposed to be thread safe. Everything works till i want it to have return value instead of void. How do i get the return value when BeginInvoke is called? public static string readControlText(Control varControl) { if (varControl.InvokeRequired) { varControl.BeginInvoke(new MethodInvoker(() => readControlText(varControl))); } else { string varText = varControl.Text; return varText; } } Edit: I guess having BeginInvoke is not nessecary in this case as i need value from GUI before the thread can continue. So using Invoke is good as well. Just no clue how to use

I'm confused why I can't make this test counter application work with 2 (or more) simultaneous running countertextboxes with the use of "BeginInvoke" on my Dispatcher in the Count() method. You can solve the issue by replacing the BeginInvoke by an Invoke. But this doesn't solve my confusion. Here's the sample code I'm talking about: public class CounterTextBox : TextBox { private int _number; public void Start() { (new Action(Count)).BeginInvoke(null, null); } private void Count() { while (true) { if (_number++ > 10000) _number = 0; this.Dispatcher.BeginInvoke(new Action(UpdateText), System

I've read a couple of forums and even a stackoverflow question or two saying that Delegate.EndInvoke is necessary when using Delegate.BeginInvoke. Many of the articles I've read talking about using BeginInvoke have failed to mention using EndInvoke. Also I've deployed production code using only BeginInvoke and there doesn't appear to be any memory issues. The way I've used BeginInvoke is generally with threads that I don't care about when they finish or how long they take to process. From the MSDN article 'Calling Synchronous Methods Asynchronously' : No matter which technique you use, always

I want to display a progress bar while doing some work, but that would hang the UI and the progress bar won't update. I have a WinForm ProgressForm with a ProgressBar that will continue indefinitely in a marquee fashion. using(ProgressForm p = new ProgressForm(this)) { //Do Some Work } Now there are many ways to solve the issue, like using BeginInvoke , wait for the task to complete and call EndInvoke . Or using the BackgroundWorker or Threads . I am having some issues with the EndInvoke, though that's not the question. The question is which is the best and the simplest way you use to handle