Featured post
where should I put the EF entity and data annotations in asp.net mvc + entity framework project -
so have dataentity class generated entityframework4 sqlexpress08 database. data context exposed via wcf data service/odata silverlight , win forms clients.
should data entities + edmx file (generated ef4) go in separate class library?
the problem here specify data annotations few entities , of them require specific mvc attributes (like compareattribute) class library reference mvc dlls. there happen entity users encapsulated or wrapped iidentity in website. pretty tied mvc website. or should maybe go in base folder in mvc project itself?
mostly website data driven around database, approve users, change global settings etc. real business happens in silverlight , win forms apps.
im using mvc3 rc2 razor.
thanks
should data entities + edmx file (generated ef4) go in separate class library?
imho data access logic specific data access technology (in case entity framework) should go separate assembly. there should no mvc specific assemblies referenced there.
in asp.net mvc application reference assembly , write view models. view models contain mvc specific attributes. map between model classes , view models passed view. automapper used facilitate task.
- Get link
- X
- Other Apps
Comments
Post a Comment