Support multiple model metadata providers in ASP.NET MVC
Aaron Shumaker commented
I did vote for this issue, as the meta data provider is often the best place to implement cross cutting changes, like automatic title casing and splitting of camel cased property labels.
However, note that you can work around this by chaining providers using inheritance. I.e. Provider1 inherits from Provider2, and so you assign Provider1 as the Current provider. Provider1 must ensure that they call base class methods when over-riding any method.