Asp.net MVC Architecture -


i'm coming end of first mvc project, , i'm not overly happy how constructed model objects , i'm looking ideas on how improve them.

i use repositories each db table get, save, delete etc methods. repositories use linq2sql db access.

i mapping linq2sql objects mvc model objects, in main, these 1 1 mappings.

my problem is, don't think mvc model objects granular enough, , passing more data , forth needed.

for example, have user table. admin can edit users details can user themselves, reckon should have "adminusermodel" , "usermodel" objects, "adminusermodel" has greater set of values (isenabled example).

so bigger question really, kind of architectures people using out there in wild, in order map many similar, related model objects down through layers db?

any sample architecture solutions can suggest beyond nerddinner?

thanks in advance!

in case of user model, should use inheritence in stead of 2 seperated models. in way can use code created user in ones inherite it.

the type of model use depends on want it. thing might take @ patterns , try patterns working needed situation...


Comments

Popular posts from this blog

android - Spacing between the stars of a rating bar? -

aspxgridview - Devexpress grid - header filter does not work if column is initially hidden -

c# - How to execute a particular part of code asynchronously in a class -