<< Back To All Blogs
Adding a Custom ASP.NET Page to MOSS/WSS
Sunday, May 3rd, 2009
There are often times that adding a custom ASP.NET page to SharePoint can be quite useful to assist in exporting data, normalizing data, or further enhancing the abilities of SharePoint. This is mostly a trivial process, but setting up the page to work as you need can slow you down a bit at times.
There are also a number of different methods to implementing this ability. An entire ASP.NET application can also be deployed. For the purpose of this article, we are going to focus on a single-file, inline-code C# file that will be added to the layouts folder in SharePoint to extend the ability in all sites.
There is really not much to this process. But you do need to declare things properly in a single file (no code-behind), and register any tag prefixes that you intend to use.
The example I have pasted below is a general layout which you can use while publishing a custom ASP.NET page to SharePoint:
<%@ Page Language="C#" AutoEventWireup="true" %>
<%@ Assembly Name="Microsoft.SharePoint.ApplicationPages, Version=220.127.116.11, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=18.104.22.168, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register Tagprefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=22.214.171.124, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Import Namespace="System.Linq" %>
<%@ Import Namespace="System.Xml.Linq" %>
// This code will run at the load-time of the page
protected void Page_Load(object sender, EventArgs e)
// An example below of retrieving the context, checking for validity
// You can then access lists, document libraries, etc from the retrieved context
SPContext ctx = SPContext.Current;
if (ctx != null)
SPWeb web = ctx.Web;
if (web != null)
What causes "Please wait while scripts are loaded..." in SharePoint
Using Data Protection Manager 2007 For Disaster Recovery on SharePoint
Receiving "The specified file is not a valid spreadsheet or contains no data" when importing to Office 365
Automatically Setting File Name in SharePoint when submitting an InfoPath 2007 Form
Currently no comments.
Add A Comment
Email Address: (not public, used to send notifications on further comments)
Enter the text above, except for the 1st and last character: