asp.mvc model design
Posted
by
Radu D
on Stack Overflow
See other posts from Stack Overflow
or by Radu D
Published on 2011-01-04T15:50:36Z
Indexed on
2011/01/04
15:54 UTC
Read the original article
Hit count: 275
Hi,
I am pretty new to MVC and I am looking for a way to design my models.
I have the MVC web site project and another class library that takes care of data access and constructing the business objects.
If I have in that assembly a class named Project that is a business object and I need to display all projects in a view ... should I make another model class Project? In this case the classes will be identical. Do I gain something from doing a new model class? I don't like having in views references to objects from another dll ... but i don't like duplicating the code neither.
Did you encounter the same problem?
© Stack Overflow or respective owner