March 18, 2013 at 5:38 pm
We are going to develop a new .net application that we think we may use entity framework model.
And as I understand it can generate code like insert, update but not use stored procedures.
Can anyone recommend articles or tutorial of how to develop the model and also database development cycle.
and pros and cons by using insert, update in code in this model instead of using stored procedures
Thanks
March 18, 2013 at 6:16 pm
You absolutely can use stored procedures:
http://msdn.microsoft.com/en-us/data/gg699321.aspx
Personally I'd recommend building a good data model and database first, then point EF at it. However I'd search around for what other people have done as well and make an educated decision for your environment and goals.
March 18, 2013 at 8:23 pm
We found a full EF was way overkill for what we wanted.
We decided to go for a lightweight alternative in PetaPoco.
Before you go down the EF route make sure it is something that you really do require.
How we use it is basically create the webservices and point them to stored procs for all the CRUD (create read update delete) operations - works quite well.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply