Databases
StackOverflow2013
Postsdbo
POPros & cons between LINQ and traditional collection based approaches
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPros & cons between LINQ and traditional collection based approaches
    primarykey
    data
    text
    <p>Being relatively new to the .net game, I was wondering, has anyone had any experience of the pros / cons between the use of LINQ and what could be considered more traditional methods working with lists / collections? </p> <p>For a specific example of a project I'm working on : a list of unique id / name pairs are being retrieved from a remote web-service.</p> <ul> <li>this list will change infrequently (once per day), </li> <li>will be read-only from the point of view of the application where it is being used</li> <li>will be stored at the application level for all requests to access</li> </ul> <p>Given those points, I plan to store the returned values at the application level in a singleton class.</p> <p>My initial approach was to iterate through the list returned from the remote service and store it in a NameValueCollection in a singleton class, with methods to retrieve from the collection based on an id:</p> <pre><code>sugarsoap soapService = new sugarsoap(); branch_summary[] branchList = soapService.getBranches(); foreach (branch_summary aBranch in branchList) { branchNameList.Add(aBranch.id, aBranch.name); } </code></pre> <p>The alternative using LINQ is to simply add a method that works on the list directly once it has been retrieved:</p> <pre><code>public string branchName (string branchId) { //branchList populated in the constructor branch_summary bs = from b in branchList where b.id == branchId select b; return branch_summary.name; } </code></pre> <p>Is either better than the other - is there a third way? I'm open to all answers, for both approaches and both in terms of solutions that offer elegance, and those which benefit performance.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USIan
    1. USIan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPros & cons between LINQ and traditional collection based approaches
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPros & cons between LINQ and traditional collection based approaches
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPros & cons between LINQ and traditional collection based approaches
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload