My question is related to best practice for splitting asp.net mvc web application. I am creating a fairly simple application that has two main sections: open and closed. Basically, I ran into the problem of collisions between controllers. I want to have URLs like / public / portfolio, but also have / private / portfolio.
By exploring some options, it seems that areas will work well for this situation. Are there other alternatives, for example, some kind of creative routing scheme that I should consider?
CocoB source
share