We all now understand for sure the "Context"...
a. Sharepoint context - where we are underneath the hood of Sharepoint. These include any page / list / control that is pretty much sitting underneat sharepoint content database. These include Settings Pages, Default Pages, Configuration, Application Management pages, Users Page and so on. These are known as SITE or CONTENT Pages
b. Application Pages - You can create custom application pages to add user interface components to a custom solution based on Microsoft Windows SharePoint Services 3.0. Unlike site pages (for example, default.aspx), a custom application page is deployed once per Web server and cannot be customized on a site-by-site basis. Application pages are based in the virtual _layouts directory. In addition, they are compiled into a single assembly DLL. They are also used across all sites within a server farm. For these reasons, they perform better than site pages. With application pages, you can also add inline code. With site pages, you cannot add inline code.
a. Sharepoint context - where we are underneath the hood of Sharepoint. These include any page / list / control that is pretty much sitting underneat sharepoint content database. These include Settings Pages, Default Pages, Configuration, Application Management pages, Users Page and so on. These are known as SITE or CONTENT Pages
b. Application Pages - You can create custom application pages to add user interface components to a custom solution based on Microsoft Windows SharePoint Services 3.0. Unlike site pages (for example, default.aspx), a custom application page is deployed once per Web server and cannot be customized on a site-by-site basis. Application pages are based in the virtual _layouts directory. In addition, they are compiled into a single assembly DLL. They are also used across all sites within a server farm. For these reasons, they perform better than site pages. With application pages, you can also add inline code. With site pages, you cannot add inline code.
Comments