Handling Multiple Areas for Enterprise level Application

Question

Hi,
In one of our client place, an existing Enterprise level application with 150 modules developed using ASP.NET 2.0 is being revamped with ASP.NET MVC.

The new solution has the following structure:

1. Web UI ( MVC Project )
• Areas
1. Module1-Area
2. Module2-Area
3. Module3-Area
2. Core
3. Entitities 
4. Business
5. Data

The current production environment is comprised of four WFE servers and one load balancer. 

Client wants to have the same Authentication and Branding logic across the modules under the same solution. As of now, team is working on three modules using the Areas concept and going forward other modules would be added as and when possible.

 

The question is,  what is the best practice to handle this kind of scenario? do we need to keep the modules under Areas and continue adding additional modules going forward or do we need to have a separate project for each module under the same solution?

 
If in case keeping them as separate project is the good option, how about handling build and deployment process?.

The constraint what we have is client doesn't want to have multiple solutions. 

 

Experts advise please.

 

Thanks,

Saravanan