views:

21

answers:

0

I am quite frustrated with Entity Framework as most of the tutorials only show how to use it with one or two tables, and not multiple tables with relations. I was thinking of the following 'hack' to get my job done quickly: Create and Import procedures in the EF ORM to do most of the CRUD where multiple tables come into picture.

  1. What are the pros and cons of this approach?
  2. Can some give me a basic overview of how to do this (after adding the procedure to the model and doing a function import)? Steps on how to let the Visual Editor do most of the work on creating the front end and CRUD code for a procedure - just like for a table.

Update: Using views may be another option. 3. What are the pros and cons of using views?