In SP 2013 the publishing architecture is not compatible with the Minimal Download Strategy. As far as I can tell this is because the Microsoft.SharePoint.Publishing.dll assembly is not signed with the
[MdsCompliant(true)] attribute and the
PublishingPage class does not inherit from the
DeltaPage class like the
WebPartPage and the
UnsecuredLayoutsPageBase classes do.
Why is this?
Is it because publishing pages are scheduled (hence inheriting from
Is there some other technical reason why the page type is incompatible?
Or is Microsoft just trying to push people away from using the publishing architecture?
Stumbled upon this article by Wictor Wilen again a few months after asking this question, and it looks like he's updated the post:
[Added 2012-08-16] The MdsCompliant attribute is set on the whole Microsoft.SharePoint.dll assembly, but not on the Microsoft.SharePoint.Publishing.dll assembly. This is a bummer. This means that all the Field Controls, used in page layouts, are not MDS compliant – which means no MDS on publishing sites.
So I was right about the assembly attribute being missing from Microsoft.SharePoint.Publishing.dll. Still wondering why MSFT went this route for publishing.