In general ...
N-Tier Entity Framework generates client and server code to query entities supporting sorting (orderby etc.), filtering (where), paging (skip and take), and including relations (include). This operations are end-to-end i.e. client define linq queries, transmitted to server via WCF and eventually executed on the database. More sophisticated query operations like projections, aggregations, and joins can be added manually either on server (DataService) or client data context (DataContext). All relevant interfaces and classes are generated as partial and my easily be extended using partial interfaces and classes:
on server
- partial interface IMyDataService
- partial class MyDataService
and on client
- partial interface IMyDataContext
- partial class MyDataContext
Also, stored procedures are not automatically exposed by the framework generated code. If you would like so, either modify code generation (T4 files) or add custom methods to data service and client data context.
In your case ...
Depending on what your intension is you could do something like:
var query =
from p in ctx.PROJECTS.AsQueryable()
.Include(“USER_PROJECTS_NAVIGATION_PROPERTY”)
where p.USER_PROJECTS_NAVIGATION_PROPERTY.RF_USER == 1
select p;
Or if you need something more complex, implement it as a custom method using the partial classes listed above.