title: How to move from LINQ to SQL to "LINQ to WCF"?
body: <p>I'm putting together a WPF application which will eventually use WCF web services as its data source.</p>
  
  <p>During the prototyping phase, I'm using LINQ to SQL on an SQL 2008 database and have come to appreciate the ease with which I can do "Add New Item  | LINQ to SQL Classes" and generate a model class for a table, then speak to it with LINQ and pass this to my XAML UI, very nice.</p>
  
  <p>But what happens when we switch the datasource from SQL Server to WCF web services?  In order to continue using LINQ, am I going to have to:</p>
  
  <ul>
  <li>write my own LINQ-to-web-service classes manually (using IQueryable etc.?)</li>
  <li>is there a code generation tool that does this, something like "LINQ-to-WCF" (strange that this term doesn't even come up in Google)</li>
  <li>or will I have to inefficiently get large amounts of records from my web service, create objects out of them, and then to LINQ-to-objects to query them?</li>
  </ul>
  
  <p>Thanks for any direction you can give here.</p>
  
  <h3>ADDED: thanks for the answers, very helpful, but led to some confusion:</h3>
  
  <ul>
  <li>this <a href="http://msdn.microsoft.com/en-us/library/cc907912.aspx" rel="nofollow noreferrer">MSDN tutorial</a> says to "Add New Item | <strong>ADO.NET Entity Data Service</strong>"</li>
  <li>I have VS2008 and can just do "Add New Item | <strong>ADO.NET Entity Data Model</strong>"</li>
  <li>this <a href="http://msdn.microsoft.com/en-us/data/cc745968.aspx" rel="nofollow noreferrer">MSDN video</a> says to create a new project with the <strong>ADO.NET Data Service</strong> template which I don't have in VS2008</li>
  <li>what are the differences between all of these, which are used most commonly?</li>
  <li>and from what I have read so far anything that has to do with "LINQ to Entities" entail costs whereas "LINQ to SQL" is free, so do the "Entity Data Service/Model" options above have to do with LINQ to Entities?</li>
  </ul>