You can also cast the anonymous delegate to MethodInvoker.

Invoke((MethodInvoker)delegate() { _activityStrip.Text = value; });

Still not ideal, but better.

Or why don't you add an overload to your base Form that takes a MethodInvoker:

public void Invoke(MethodInvoker invoker)

{

           Invoke((Delegate)invoker);

}

Now you can call Invoke with an anonymous method.

I still think is has performance issues.

I have taken an example to update progressbar while reading a huge file. If I update in unsafe way in the thread, the program executes amazingly fast.

MethodInvoker myCallback = new MethodInvoker(

               delegate()

{

progressBar1.Value = m_iPercentage;

});

//progressbar percentage

Double perRead = (Convert.ToDouble(fStream.Position) / Convert.ToDouble(fStream.Length)) * 100.0;

m_iPercentage = Convert.ToInt32(perRead);

progressBar1.Value = m_iPercentage;

//Invoke(myCallback);

as soon as i comment progressbar1.value = m_iPercentage; and run through Invoke(myCallback); the program runs hell lot slower.

Do know what to do here.

Try using BeginInvoke instead so your thread doesn't block waiting for the target thread's message loop.

Also, you really should keep track of your last percentage and avoid doing the invoke all together unless the value has changed.  Invokes by their very nature are slow and even if you don't block on them it'll be better for your application if you don't invoke unless you absolutely have to.

Calling Control.Invoke() with anonymous methods

In 3.5, you could create a simple extension method on the Control object with this overload which will allow a anony delegate to be passed to invoke:

public static void Invoke(this Control c, MethodInvoker mi)

{

   c.Invoke((Delegate)mi);

}

get { return _activityStrip.Text; }

is that threadsafe???

doesnt look like it

i wrap get and sets with invokes