• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Linq - checking for nulls"

Collapse

  • wurzel
    replied
    Originally posted by Jaws View Post

    Code:
    var result = from e in response.entitlements ?? Enumerable.Empty<Entitlement>() 
                      where e != null // this may no longer be necessary
                      select new {...}
    Excellent, just what I was looking for. Thanks.

    Leave a comment:


  • Jaws
    replied
    The e != null means it will include any elements in the collection that are not null. It does not account for a null collection which, if I understand correctly, is the cause of the problem here.

    You could use the coalesce operator (??) to use an empty collection when the property value is null. For example if the type of the elements in the response.entitlements collection is Entitlement you'd do something like the following:

    Code:
    var result = from e in response.entitlements ?? Enumerable.Empty<Entitlement>() 
                      where e != null // this may no longer be necessary
                      select new {...}
    Last edited by Jaws; 28 December 2011, 22:47.

    Leave a comment:


  • wurzel
    started a topic Linq - checking for nulls

    Linq - checking for nulls

    Using the query syntax, how do you check if a collection is null?


    var result = from e in response.entitlements where e != null
    select new {...}

    response.entitlements is an array & when it's null I get a null reference exception but according to MSDN this where clause should handle it
Working...
X