SharePoint master page options

By default, Iron Speed Designer applications contain these top-level master pages:

SharePoint 2010:

SharePoint 2007:

The default top-level master page is set in the Application Generation Options dialog (Tools, Application Generation Options…).


At application run-time, application pages use SharePointMaster.master which is a copy of the default top-level master page.  Sometimes, the particular configuration of your SharePoint server can interfere with the top-level SharePoint master page used by your application.  In this case, consider using SharePointBasic.master which has only a basic set of controls.

For SharePoint 2010, SharePointMaster.master contains a ScriptManager tag as well as normal default SharePoint master page. For that reason ScriptManager asp tag is not included in the first level master pages. This is different from the SharePoint 2007 where top tier master page did not have ScriptManager reference and so it was included in the first level (i.e. HorizontalMenu.master, VericalMenu.master, etc.) master pages.

In the case you use old or different top tier master page which does not have ScriptManager tag (for example if you upgraded your SharePoint 2007 to SharePoint 2010 and decided to keep you previous master page) you can instruct Iron Speed Designer to include ScriptManager references to first-evel master pages (i.e. in HorizontalMenu,master, VerticalMenu.master, etc.)  Note, that in this case you will not be able to run application in non-SharePoint environment unless you manually remove ScriptManager reference from the top tier master page (SharePointMaster.master). To add ScriptManager change Option in Application generation options to Yes (see image above).

For SharePoint 2007, you might alternatively use SharePointFull.master which has an additional hierarchical tree control in the left vertical bar.  In some environments this control is known to interfere with applications, so this master page is not normally set as the default.

To change the master page in a deployed application, simply delete SharePointMaster.master, create a copy of desired master page (i.e. SharePointDefault.master, SharePointFull.master, or SharePointBasic.master) and rename it as SharePointMaster.master.  All pages always use SharePointMaster.master as their top-level master page unless you elected to use Microsoft SharePoint default master page, in which case the top-level master page will be retrieved from the context of the running application.


This master page does not include any SharePoint navigation controls, frames, themes and pictures. It can be used for pop-up controls, such as custom large list selectors.

See Also

Locating application files on the SharePoint server

Changing Code Access Security (CAS)

Adding navigation to your application

Uninstalling (retracting) a SharePoint solution

Using Microsoft Access databases in SharePoint applications

SharePoint master page options