ASP.NET MVC: Need to deploy multiple copies of a site

I have an app that I need to white-label and deploy for a client. The functionality will be identical, all the pages will be nearly identical. 开发者_开发技巧The only real difference will the missing logo/styling and the use of a SSO-like system instead of regular forms auth. The authentication part is no problem, as that can just be injected. But what's the best way for me to do different master pages / config files by site?

'Best' means least likely to cause problems and maintenance headaches. Attributes that would be good: quick/easy to implement, quick/easy to maintain.

You could write your own view engine in ASP.NET which loads a different theme depending on the customer that logs in.

This way you can load different cascading style sheets, master pages, views....etc.

About a year ago I wrote a post on this:

https://github.com/geersch/ThemedViewEngine