Why Linq Is Having Select Clause At The End?

1.	Why Linq Is Having Select Clause At The End?
Answer» DUE to IntelliSense of Visual Studio. If the select clause was in the first of LINQ, then the IDE cannot populate the properties INSIDE the object. Eg:from F in db.Forum where f.Id > 0 select f.Name; If the select was in FRONT - the "select f." could not populate any autocomplete properties or methods. Due to IntelliSense of Visual Studio. If the select clause was in the first of LINQ, then the IDE cannot populate the properties inside the object. Eg:from f in db.Forum where f.Id > 0 select f.Name; If the select was in front - the "select f." could not populate any autocomplete properties or methods.

Answer»

DUE to IntelliSense of Visual Studio.

If the select clause was in the first of LINQ, then the IDE cannot populate the properties INSIDE the object.

Eg:from F in db.Forum where f.Id > 0 select f.Name;

If the select was in FRONT - the "select f." could not populate any autocomplete properties or methods.

Due to IntelliSense of Visual Studio.

If the select clause was in the first of LINQ, then the IDE cannot populate the properties inside the object.

Eg:from f in db.Forum where f.Id > 0 select f.Name;

If the select was in front - the "select f." could not populate any autocomplete properties or methods.

Discussion