1)Site pages support customisation while application pages do not.
2)Application pages allow in-line code.
Example of site pages are the home page, and pages that have lists.
Wednesday, November 7, 2007
Sharepoint: Page Ghosting
Page Ghosting - The page template is loaded from the file system of the web server. No access to the content database is required. The opposite of this occurs when you have saved customised a page -changes are saved to the content database. This is known as unghosted pages.
The SPVirtualPathProvider is responsible for retrievin unghosted pages from the content database.
The SPVirtualPathProvider is responsible for retrievin unghosted pages from the content database.
Tuesday, November 6, 2007
Sharepoint: Two methods for Restarting an Application Pool
Two different methods for restarting an application pool
1) IISRESET
-this restarts all the processes associated with IIS
2) cscript.exe c:\windows\system32\iisapp.vbs /a ""DefaultAppPool"
- This restarts a specific application npool (/a parameter with the name of IIS application pool)
1) IISRESET
-this restarts all the processes associated with IIS
2) cscript.exe c:\windows\system32\iisapp.vbs /a ""DefaultAppPool"
- This restarts a specific application npool (/a parameter with the name of IIS application pool)
Thursday, November 1, 2007
Sharepoint: Customisation vs Personalisation
Personalisation - changes made are only seen by the person making them,
Customisation - seen by all users, performed by administrators.
Sharepoint stores personalisation and customisation separately in the content database.
Customisation - seen by all users, performed by administrators.
Sharepoint stores personalisation and customisation separately in the content database.
Subscribe to:
Posts (Atom)