Reply to thread

Message

[QUOTE="jmcilhinney, post: 184098, member: 641"]
By the way, don't use [I]FirstOrDefault[/I] if you don't care about the object but only whether the object exists. If you were going to do it like you were, rather than this:
[CODE=vbnet]findObj = distinctList.FirstOrDefault(Function(xx) xx.ValueX = itm.Prop2)

If findObj Is Nothing Then[/CODE]
you would do this:
[CODE=vbnet]If Not distinctList.Any(Function(xx) xx.ValueX = itm.Prop2) Then[/CODE]
Also, don't create objects that you never use. What is the point of this:
[CODE=vbnet]Dim findObj As New OnePropObj

findObj = distinctList.FirstOrDefault(Function(xx) xx.ValueX = itm.Prop2)[/CODE]
You declare the variable and assign a new object to it, then you immediately discard that object and assign the result of a method to the variable. Only use the [I]New[/I] keyword if you actually want a new object. That code should have been this:
[CODE=vbnet]Dim findObj As OnePropObj

findObj = distinctList.FirstOrDefault(Function(xx) xx.ValueX = itm.Prop2)[/CODE]
or, even better, this:
[CODE=vbnet]Dim findObj = distinctList.FirstOrDefault(Function(xx) xx.ValueX = itm.Prop2)[/CODE]
There's no point separating the declaration and initialisation of a variable if nothing happens in between. There's also no need to specify the type of a variable if it can be inferred from the initialising expression, although you can if you want to:
[CODE=vbnet]Dim findObj As OnePropObj = distinctList.FirstOrDefault(Function(xx) xx.ValueX = itm.Prop2)[/CODE]
[/QUOTE]

Verification