What are the pros and cons of Areas implemented as single projects vs multiple projects in asp.net mvc
asp.net-mvc
Solution
Recommend that you use single-project areas, as we've made considerable strides in its support and stability. The multi-project areas code is very fragile, and there is a higher-than-zero likelihood that it will be removed or pushed to Futures in the near future.
Problem
The app I'm working on is large enough to break up into areas, but before I do so, I was hoping to get a better idea of when to implement areas in a single project versus multiple projects. This article only mentions team size as a factor for choosing, but that doesn't really make sense to me http://msdn.microsoft.com/en-us/library/ee461421(VS.100).aspx