title: Reusable Querying in Entity Framework WITHOUT Repository. How?
body: <p>Let me say, I have come to the conclusion (after a lot of trial) that Repository &amp; Unit of Work when using Entity Framework is just wrong, wrong, wrong and <a href="https://stackoverflow.com/questions/5488313/organizationally-where-should-i-put-common-queries-when-using-entity-framework-c/5488947#5488947">this says why</a> quite well.</p>
  
  <p>But I really hate on those embedded queries. Question is, where can I put them instead if I'm so against a repository, etc? (clean answers only please, examples much appreciated).</p>
  
  <p>I just nuked two projects containing my repositories, unit of work and interfaces with <em>hundreds</em> of files because the payback was nowhere to be seen. I think lots of people, myself included, just jumped on the Repository bandwagon because that's what everybody else was doing but in retrospect, I think it's really a ride to nowhere.</p>
  
  <p>/sigh</p>
  
  <p>Richard</p>