Sharepoint Pages Overview

  • SharePoint pages are built on the foundation of ASP.NET. As a SharePoint developer, you must be aware of two different types of SharePoint pages.
  • These are Application pages and Site pages. Application pages, such as Settings.aspx, are used for all Windows SharePoint Services sites. Therefore, if you modify or extend the functionality in this type of page, your changes will apply to all SharePoint sites. Application pages are stored in the file system of the front-end Web server. They are located in the TEMPLATE\LAYOUTS folder in the Web Server Extensions path. Each SharePoint Web includes a virtual directory, named _layouts, that points to this physical location. So, for example, the Settings page is accessible by using the relative URL of /_layouts/Settings.aspx.
  • In contrast, Site pages, such as Default.aspx, can be customized on a site-by-site basis.
  • Newly-created sites start with site pages based on page templates on the front-end Web server. For example, sites based on the Team Site template contain a Default.aspx page from the TEMPLATE\SiteTemplate\sts folder. These pages are known as uncustomized pages.
  • When a site designer or developer customizes a site page for a specific site, the customized copy is stored in the site database and served from there when requested.
  • SharePoint pages are built on the foundation of ASP.NET 2 master and content pages.
  • Windows SharePoint Services uses master pages and content pages to achieve a rich level of page-templating and manageability.
  • Master pages typically contain layouts, graphics, and functionality, such as standard navigation controls, which can be re-used on multiple pages.
  • Master pages also contain one or more content placeholder controls that define where content pages can add specific page content.
  • Content pages reference master pages to re-use all of these features. They also contain content controls that map to the content placeholder controls in the master page.All Windows SharePoint Services site pages are content pages.
  • They reference master pages that are stored and managed in the Master Page Gallery of the SharePoint site.Application pages are also content pages.
  • They reference a master page that is stored in the file system of the front-end Web server.For example, the Settings.aspx application page references the application.master page, which is stored in the TEMPLATE\LAYOUTS folder in the Web Server Extensions path.
  • You can customize master pages so that all content pages which reference them inherit your changes.
  • You can use the new SharePoint Designer tool to edit master pages, or you can use text editors or Visual Studio 2005 to customize master page appearance and functionality.

More to come...

Cheers...

Comments

Post a Comment

Popular posts from this blog

PowerShell to update SharePoint Online User Profile property from Azure AD

Image
Hi Friends, in this post, I am gonna walk you through the steps to update the SharePoint Online User Profile property from Azure AD. You may think, why this is necessary since SharePoint online will sync automatically with Azure AD. The tricky part is the auto-sync may take up to 24 hrs to sync Azure AD to SharePoint UPS. The next tricky part is not all the AAD profile properties are synced to SharePoint UPS. Only a few of the properties are synced and below are the list of properties relevant to the profile that is synced to SharePoint UPS User Name First name Last name Name Office phone Department Job title Manager Office Office phone What about the other properties like 'Mobile Phone' that are relevant to the user??? What about if there is a drastic change in the Organization structure and you want the SharePoint UPS to reflect immediately??? To resolve all these obstacles and issues, we need to use PowerShell Now you understand why there i...
Read more

SPFx - Office UI Fabric react DetailsList & PropertyFieldCodeEditor to show the CSV data

Image
Hi Friends, this is a series of the post explains different capabilities of the web part using SPFx. Using DateTime control PropertyFieldCollectionData Property Pane Control Using FilePicker and FileTypeIcon control Office UI Fabric react DetailsList & PropertyFieldCodeEditor to show the JSON data Office UI Fabric react DetailsList & PropertyFieldCodeEditor to show the CSV data  --> You are here In this post, I am gonna show you how we can use  DetailsList   from  UI Fabric  and  PropertyFieldCodeEditor  property pane control from PnP on the SPFx web parts. The code walkthrough shown below will display the ' CSV ' data in the DetailsList. Regarding the creation of the basic project stuff, please refer to the  blog post . I hope those who are familiar with SPFx would know how to create the project and add the dependent npm packages. The following are some of the pre-requisites for the solution to work. Used  S...
Read more

Using React Context API in SPFx

Image
Introduction   Hi friends, this blog post will guide you through the usage of  Context API  which is one of the new features introduced in the latest version of React   in SPFx projects .  What is React Context and When to use it In a normal React application, the properties are passed top-down from parent to child and then to the grandchild via props. It works great in simple react applications, but this will be very tedious for complex applications.  Context  provides us an easy way to share the props without having them pass through all the intermediate components.  Context  should be primarily used when the properties must be accessible by many components at different nesting levels. We must apply it with cautious because sometimes it makes the reuse of the components more difficult. How can we use it in SPFx?   I hope many of you are aware of the SPFx development model, where we might need to pass the properties that are captured ...
Read more