dilemma: Within Visual Web Developer Express, Should I...
1. Allow Entity Framework to create model and CRUD scaffolding for a project.
2. connect to existing SQL database without the benefit of Entity creating the model.
Is there an advantage to allowing the columns / fields to be created through Entity Framework?
If I create model through Entity, I will have to reenter field details for about 100 columns / fields (e.g. distinguishing field type detail such as int / tinyint / small int / bigint/ varchar(max 50 / varchar)).
3v3rhart
Member
159 Points
317 Posts
Entity Framework CRUD Scaffolding v existing SQL database
Feb 02, 2012 12:38 AM|LINK
dilemma: Within Visual Web Developer Express, Should I...
1. Allow Entity Framework to create model and CRUD scaffolding for a project.
2. connect to existing SQL database without the benefit of Entity creating the model.
Is there an advantage to allowing the columns / fields to be created through Entity Framework?
If I create model through Entity, I will have to reenter field details for about 100 columns / fields (e.g. distinguishing field type detail such as int / tinyint / small int / bigint/ varchar(max 50 / varchar)).
Thanks!
Dean