I'm somewhat surprised that DevForce won't support SPs until fall 2010 (which I guess could be as early as 9/23 or as late as 12/20/2010) considering you managed to release your 2010 version just 3 days after Visual Studio 2010 was released:
DevForce 2010 has no support for any kind of stored procedure. We expect to repair these deficits by fall 2010. Meanwhile, you can write Server Methods that talk directly to EF or use ADO.Net to invoke the stored procedures; you then can pour their results into entities that you return to the client.
If we use SPs in EF and add them (via function imports) to the data model, will DevForce code generation just ignore them? I assume it must since you're saying we can talk to EF directly on the server-side.
If we talk directly to EF, does that mean we'll have to enable EF class generation, which is now off by default? Same question for server-side PassThruESQLQueries.