i want develop simple cms.
i want add ability add modules cms.
what need architecture such cms?
a solution , mvc project site , admin? or 1 project area admin?
in mvc each of modules have controller,model , views. if put in 1 project, mix of module ,each module in 3 folders (controller,model , views).
how need arrange them code nice , clean?
since separating type of user, can surely (and easily) include in 1 project. of admin controllers should have [authorize(roles="admin")] on them limit them admin. mixing them fine, other applications mix user roles in application on regular basis, limit difference security (and dont use url restrictions in web.config - use [authorize] attribute on controllers instead!! if expect differences in both applications huge can separate project, i'm imagining can reuse including them in same project.
how architect very broad question. basic project include in 1 project. prefer break out models , data access code separate project , try code interfaces as possible unit testing purposes. think bit beyond scope of posting here though. start - work mentioned attribute , think develop. start unit testing , think steer right direction. read on dependency injectiom , unit, ninject, etc ways dynamically bind implementation classes makes unit test go quite bit smoother well.
Comments
Post a Comment