I am attempting to find the best way to architect my MVC application.
Think of a school with users, but in my case users can be associated with many schools.
I am using Entity Framework with a sql backend. I have thus far created Schools, Addresses, Classes, AddressResourceMappings, and (Asp.Net)User Membership. AddressResourceMapping is used to Map Users and Schools to Addresses (Many to Many).
My thought is to use an admin area(new to asp.net MVC). what i am not sure of is if two areas should be created, acutally three ie. Admin (area1) School(area2) Users(area3) but how to share Address between the two?
problem 1. allow admins specific to their school to edit information. Some admins may be able to edit other schools as well. (I have been thinking Session variable, but i dont know if this would be the best route)
problem 2. Within the masterpage show, in left hand column, information links to open Address, classes, and more will be entered later. when clicked only specific information based on School or user in content area. (I think this deals with routing, but i am not sure). my thought is something like /school/address/id, /User/address/id, /school/Class/id, or /user/class/id. Id rather not create a category type list, just to house links. Id rather it be dynamic so i can add more controller types later.
I would like to do this without having to rewrite code over and over and be as dynamic as possible, especially within the views.
I have been reading books and blogs on MVC, but I cannot grasp the architecture that is needed for this type of application.
I hope someone can help, and your help would be greatly appreciated.