Generic Handlers (.ashx files) deployed to the _layouts directory are not directly supported by Visual Studio 2010 SharePoint projects like custom .aspx application pages are. This post will cover how to add them to your Visual Studio project and deploy them properly to the ISAPI folder.

Overview

Visual Studio Item Templates for Generic Handlers (.ashx files) are not directly supported by Visual Studio 2010 or 2012 SharePoint projects.

If you try to Add New Item… and select the Web or SharePoint categories in a VS 2010 SharePoint project, you won’t find Generic Handler anywhere.

You’ll find ASP.NET Handler, but this will require you to create entries in web.config to make your handler work. In order to add a new .ASHX generic handler and get it to deploy properly, you can use the following steps:

• Right-click the project, and select Add New Item…
• Choose the Application Page template.
• In the name box, enter a name for your file, with an .ashx extension.
  
• Open the .ashx file, delete the contents and replace with the following, changing your Class= attribute with your desired namespace and class name:
  
  <%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %> <%@ Assembly Name="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ WebHandler Language="C#" Class="MyNamespace.MyGenericHandler" %>

  1 2 3

  <%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %> <%@ Assembly Name="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> <%@ WebHandler Language="C#" Class="MyNamespace.MyGenericHandler" %>

  
  

  Note

  If you want to reference other SharePoint assemblies in your code-behind, you will need to add an @ Assembly directive for each DLL.

• Open the ashx.cs file.
  • Add a using statement for System.Web.
  • You probably don’t need the using statement for Microsoft.SharePoint.WebControls, so remove it.
  • Change your namespace if necessary.
  • Change the class to inherit from IHttpHandler.
  • Implement the IHttpHandler interface. Your code should now look something like this:
    
    using Microsoft.SharePoint; using System.Web; namespace MyNamespace { public partial class MyGenericHandler : IHttpHandler { #region IHttpHandler Members public bool IsReusable { get { throw new NotImplementedException(); } } public void ProcessRequest(HttpContext context) { throw new NotImplementedException(); } #endregion } }

    1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

    using Microsoft.SharePoint; using System.Web;   namespace MyNamespace {     public partial class MyGenericHandler : IHttpHandler     {         #region IHttpHandler Members           public bool IsReusable         {             get { throw new NotImplementedException(); }         }           public void ProcessRequest(HttpContext context)         {             throw new NotImplementedException();         }           #endregion     } }

• In the Solution Explorer, delete the ashx.designer.cs file, it is not needed.
• In the Solution Explorer, click the .ashx file, and in the Properties pane, set the Build Action to Content.
• In the Solution Explorer, click the .ashx.cs file, and in the Properties pane, set the Build Action to Compile.
• Make sure to enable Token replacement for .ashx extensions. This will replace the $SharePoint.Project.AssemblyFullName$ token with the full strong name of your assembly, enabling you to reference other classes in your compiled assembly from the ashx code-behind.You can read more about token replacement here. To enable this for your Project, Unload your Project, Edit the .csproj file and add the following text to a PropertyGroup, and Reload your project:
  
  <PropertyGroup> <TokenReplacementFileExtensions>ashx</TokenReplacementFileExtensions> </PropertyGroup>

  1 2 3

  <PropertyGroup> <TokenReplacementFileExtensions>ashx</TokenReplacementFileExtensions> </PropertyGroup>