Home/ Questions/Q 9131397
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-17T08:08:05+00:00

In C# (new Action(() => MessageBox.Show(Hello))).BeginInvoke(null, null); In VB the translated code doesn’t compile

  • 0

In C#

(new Action(() => MessageBox.Show("Hello"))).BeginInvoke(null, null);

In VB the translated code doesn’t compile

(New Action(Sub() MessageBox.Show("Hello"))).BeginInvoke(nothing, nothing)

But in VB I can set the result of BeginInvoke to implicit variable a and it will run (thanks @Ric for this suggestion in another post)

Dim a = (New Action(Sub() MessageBox.Show("Hello"))).BeginInvoke(Nothing, Nothing)

But now I want to know why VB requires something to be set on the left hand side in this case, where C# does not.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    VB.NET simply requires an identifier. You can’t invoke a sub or other member directly like that. You can, however, use Call instead.

    You typically use the Call keyword when the called expression doesn’t start with an identifier. Use of the Call keyword for other uses isn’t recommended.

    http://msdn.microsoft.com/en-us/library/sxz296wz(v=vs.110).aspx

    Call (New Action(Sub() MessageBox.Show("Hello"))).BeginInvoke(nothing, nothing)
    • 0