Question of Style for Delegate creation

[Just_a_fan]

Both of the Dim statements work in the following. Is there a preference
and why? (Of course, you would not use them both but each, by itself,
works and enables the Invoke to function properly)

Dim newDelegate As New UIDelegate(AddressOf StatusAdd)
Dim newDelegate As UIDelegate = AddressOf StatusAdd
lblStatus.Invoke(newDelegate)

And a follow-on topic:

Actually, this brings up the whole subject of "New". It is something
new to me and I would like to know if there is something written up
explaining about why one uses "New", when it should be used and any
other implications of using it. Coming from VB6, this is foreign to me.

If there is something already written up, then that's great but I don't
know how to find something this esoteric and general. The functional
helps tell "what" but rarely "why".

Thanks for any pointers. I have been wondering about "New" for a while
and the example, above, really pointedly makes me want to know about
this syntax element.

Mike

[rowe_newsgroups]

On Apr 14, 6:00 am, [e-mail] wrote:

Both of the Dim statements work in the following. Is there a preference
and why? (Of course, you would not use them both but each, by itself,
works and enables the Invoke to function properly)

Dim newDelegate As New UIDelegate(AddressOf StatusAdd)
Dim newDelegate As UIDelegate = AddressOf StatusAdd
lblStatus.Invoke(newDelegate)

And a follow-on topic:

Actually, this brings up the whole subject of "New". It is something
new to me and I would like to know if there is something written up
explaining about why one uses "New", when it should be used and any
other implications of using it. Coming from VB6, this is foreign to me.

If there is something already written up, then that's great but I don't
know how to find something this esoteric and general. The functional
helps tell "what" but rarely "why".

Thanks for any pointers. I have been wondering about "New" for a while
and the example, above, really pointedly makes me want to know about
this syntax element.

Mike

From what I can tell with Reflector, both do exactly the same thing.
The only difference I can see is where the constructor is called. In
the first sample, you call New in the standard way, but in the second
it is called implicitly by the AddressOf keyword.

For your other question, 'New' tells the compiler to create a new
instance of that type and calls its constructor (Public Sub New(...)).
The constructor performs startup tasks such as variable initialization
or property settings that are required for the type to function. For
example, in Window's forms, all the child controls are created and
added to the forms during the form's constructor. Things don't get too
confusing until you see the types such as String that don't require
you to use 'New' to create an instance, all it needs is to have it's
value set as the constructor will be called implicitly. That probably
wasn't the best explanation, so let me know where I can clarify.

Thanks,

Seth Rowe [MVP]

[Lloyd Sheen]

<Ju********@home.netwrote in message
news:gg********************************@4ax.com...

Both of the Dim statements work in the following. Is there a preference
and why? (Of course, you would not use them both but each, by itself,
works and enables the Invoke to function properly)

Dim newDelegate As New UIDelegate(AddressOf StatusAdd)
Dim newDelegate As UIDelegate = AddressOf StatusAdd
lblStatus.Invoke(newDelegate)

And a follow-on topic:

Actually, this brings up the whole subject of "New". It is something
new to me and I would like to know if there is something written up
explaining about why one uses "New", when it should be used and any
other implications of using it. Coming from VB6, this is foreign to me.

If there is something already written up, then that's great but I don't
know how to find something this esoteric and general. The functional
helps tell "what" but rarely "why".

Thanks for any pointers. I have been wondering about "New" for a while
and the example, above, really pointedly makes me want to know about
this syntax element.

Mike

Coming from VB6 I understand why the first style would not be used. VB6
would recreate objects that used this style on its own causing reference
problems. It was widely known not to use that style.

LS