LINQ, “Value cannot be null”, yet query evaluates?

If this is in a loop test in the locals window contains the last value of test from the last iteration of the loop Edit: This has really nothing to do with LINQ, but how the debugger works.

If this is in a loop test in the locals window contains the last value of test, from the last iteration of the loop. Edit: This has really nothing to do with LINQ, but how the debugger works.

Ah ha! Well, I did say the answer might be obvious. Thanks a bunch!

– user500038 Dec 1 '10 at 21:39.

It fails on this piece of code, "Value cannot be null, parameter name: source" ... yet it also displays, in the local variables window, "test" as a variable with all its properties populated. VendorContactItem is null. Presumably this would be the first element to be added to the list.

So how is "test" evaluating correctly while simultaneously throwing up that error? I'm new to Linq, so excuse me if this is an obvious question.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions