MVC 5 compatibility

[yishaigalatzer]

We should review the MVC compatibility and expand to a set of updates.

Things that where brought up before

Route definition
Namespaces
Area registration
Caching of child actions/view components

Things that where brought up before and explicitly decided not to do

Child Action -> Replaced by view components.

[dougbu]

See also

• Revive ModelMetadata.Container property #298
• Restore missing ModelMetadata properties (additional metadata) #324
• Revive ViewContext.FormIdGenerator #440 (which I've suggested we don't fix)
• one of the Web API Shim bugs may also cover adding a Controller.Initialize() method (in MVC 5.2 / Web API 3.2 that method exists in both Controller and `ApiController)

[yishaigalatzer]

#842

[yishaigalatzer]

@dougbu these are not compatibility shim bugs, these are just bugs

[dougbu]

@yishaigalatzer tomato / tomatoe. I referenced those bugs because compat would be the reason to fix them. but agree that, if we fix most, we probably wouldn't do it in an "MVC compat shim". guess I was confused by the bug's title 😈

[dougbu]

If we provide IHtmlHelper.AttributeEncode() methods (big if), we should do them in a compat shim. There is no reason for methods that should do exactly what the existing IHtmlHelper.Encode() methods do except back-compatibility.

See #81 for a bit more discussion of these methods.