This means any custom columns you have added will not be available. Note that if this value is omitted, by default your layout will be associated with the basic 'Page' content type from the publishing feature. This means the layout will automatically have this binding and will be ready for use.
Let's talk through the values used in the example below. An example of an elements manifest file to deploy 2 master pages and 3 page layouts is shown at the end of this post. create the feature.xml and element manifest file for the feature.The best solution is to copy the contents of the final file into notepad, and save the file to the filesystem with the same name. Unfortunately, SPD will actually screw up hyperlinks and some control references when you do this - in particular references to user controls using the '~/_controltemplates/' path. save each file to the filesystem (as opposed to the Master Page Gallery) ready to be added to a feature.develop master pages/layouts using SharePoint Designer (SPD).I'll also cover web part deployment in a forthcoming post. Now that we have content types and all the supporting artifacts deployed, we can focus on deploying the things that make a real difference to how our site works - master pages and page layouts. Last time we looked at deploying content types as a feature.
#Publisher master page from file how to
This is the fourth article in my series of how to create common SharePoint site artifacts as features.