Diff between Site Pages Vs Application Pages

Site Pages:
  1. Pages that support user customization are known as site pages and stored
    in the content database.
    Ex. Site pages default.aspx, NewForm.aspx, and EditForm.aspx.

  2. Site pages customization provides flexibility but can also impact
    performance and scalability Each page would also have to be individually
    parsed and loaded into memory..

  3. Site pages do not support in-line code under the default security
    policy enforced by WSS.
Application pages:
  1. Application pages do not support customization, which gives them two
    distinct advantages over site pages.
    • First, each application page is always compiled into a single DLL so that it performs and scales better than a site page.
    • Second, application pages are allowed to have in-line code.
    Ex. Settings.aspx, uagedetails.aspx.

  2. Application pages are deployed as physical files on file system of front end
    web server on the server's file system.
    An application page, such as settings.aspx, can be accessed by adding its
    relative path within the _layouts directory to the end of a site’s URL.

  3. Application pages support customization
  • Ghosted = Un-Customized, The asp.net parser renders the page.
  • Unghosted = Customized, Controlled by the SafeMode parser.
  • Reghosting = Changing from Customized to Un-Customized.

Comments

Popular posts from this blog

Adding Contact Selector Control to InfoPath form

Adding Validation to a Custom NewForm.aspx in SharePoint & Redirect

How to add to Sub-Sub Menu in SharePoint