Problem with converting code

[jamesclarke112]

from C# to VB. I have the code working fine in C#.

C#

interceptor = new MessageInterceptor();
interceptor.InterceptionAction = InterceptionAction.NotifyAndDelete;
interceptor.MessageReceived += new MessageInterceptorEventHandler(OnSmsReceived);

VB

interceptor = New MessageInterceptor()
interceptor.InterceptionAction = InterceptionAction.NotifyAndDelete
interceptor.MessageReceived += New MessageInterceptorEventHandler(OnSmsReceived)

I get errors in VB on line 3 saying I have to use a RaiseEvent statement for MessageRecevied. I am not sure how to do this if anyone can help.

Thanks

[jmcilhinney]

If we as software developers cannot consult help documentation how can we expect our users to do so?

http://msdn2.microsoft.com/en-us/library/fwd3bwed.aspx

[jamesclarke112]

Yeah thanks. I did actually look at some documentation but still don't understand how to do it. I understand that because MessageReceived is an event you have to RaiseEvent it rather that call it directly, so I would therefore put the RaiseEvent infront of it. I'm still doing something wrong though.

[David Anton]

The short-form VB equivalent is:
AddHandler interceptor.MessageReceived, AddressOf OnSmsReceived

You could also code:
AddHandler interceptor.MessageReceived, New MessageInterceptorEventHandler(AddressOf OnSmsReceived)

[jamesclarke112]

So it's just like when you create a control at run time and you want to use its Click event for instance.

Is this the same as Raising and event then?

Thanks very much

[David Anton]

No - the original C# code you posted does not raise an event. It wires up the event handler.

[jmcilhinney]

Hmmm... I guess I could have read the code too. Odd that it would point you to RaiseEvent when you're trying to handle an event rather than raise one. The page I linked to does include a link to the AddHandler statement and MSDN also includes pages many topics dedicated to raising an handling events.

http://search.msdn.microsoft.com/sea...andling+Events