Share via

Walkthrough: Creating a Custom ASP.NET Web Service

Applies to: SharePoint Foundation 2010

This programming task provides an overview of how to create a custom Web service that operates within the context of Microsoft SharePoint Foundation. It steps through the process of creating a simple "Hello World" Web service in Microsoft Visual Studio 2010, and then shows how to modify the service so that it implements the SharePoint Foundation server-side object model to return site and list data.


Custom ASP.NET Web services will function in SharePoint Foundation 2010, but it’s recommended that you instead create custom WCF services. For more information about WCF services, see WCF Services in SharePoint Foundation 2010. For a walkthrough that shows how to create a custom WCF service, see Walkthrough: Creating and Implementing a Custom WCF Service in SharePoint Foundation.

Basic Steps for Creating an ASP.NET Web Service

  • Create a Microsoft ASP.NET Web service in Microsoft Visual Studio.

  • Generate and edit a static discovery file and a Web Services Description Language (WSDL) file.

  • Deploy the Web service files to the _vti_bin directory.

  • Make your Web Service discoverable by listing it in Spdisco.aspx

  • Create a client application to consume the Web service.

  • Create a class library within the Web service that defines the programming logic for the Web service.

Creating an ASP.NET Web Service in Visual Studio

The first step is to create a Microsoft ASP.NET Web service Web site in Visual Studio.

To create an ASP.NET Web service

  1. In Visual Studio, click File, point to New, and then select Web Site.

  2. In the New Web Site dialog box, select .NET Framework 3.5 as the target framework, select Visual Basic or Visual C# as the programming language under Installed Templates, select the ASP.NET Web Service template, select File System in the Web location box, specify a location for the project, and then click OK.

  3. Within the new Web service solution, create a separate class library project to contain the Web service logic. To create the project, click File, point to New, and then select Project.

  4. In the New Project dialog box, expand either Visual Basic or Visual C# under Installed Templates, select Class Library as the template, provide a name and location for the project, select Add to Solution in the Solution box, and then click OK.

  5. Add a reference to the System.Web.Services namespace in the class library project. Right-click the project in Solution Explorer, click Add Reference, select System.Web.Services on the .NET tab of the Add Reference dialog box, and then click OK.

  6. Replace the default class file in the class library project with the default service class file that Visual Studio provides in the App_Code folder of the Web service.

    To replace the class file with the service class file

    1. In Solution Explorer, drag the Service.cs or Service.vb file to the top node in the class library project.

    2. Delete the Class1.cs or Class1.vb file, and also delete the Service.cs or Service.vb file that remains in the App_Code folder.

  7. Create a strong name for the class library:

    1. In Solution Explorer, right-click the class library project, and then click Properties.

    2. In the Properties dialog box, click Signing, select Sign the assembly, and then select <New> in the Choose a strong name key file list.

    3. In the Create Strong Name Key dialog box, provide a file name for the key, clear the Protect my key file with a password check box, and then click OK.

  8. To build only the class library project, right-click the project in Solution Explorer, and then click Build.

  9. To add your assembly to the global assembly cache (GAC), you can either drag the assembly into the %windows%\assembly directory using two instances of Windows Explorer, or use gacutil.exe, the command-line utility that is installed with theMicrosoft .NET Framework 2.0 Software Development Kit.

    To use gacutil.exe to copy the class library DLL into the GAC

    1. To open the Visual Studio command prompt, click Start, click All Programs, click Microsoft Visual Studio 2010, click Visual Studio Tools, right-click Visual Studio Command Prompt (2010), and click Run as administrator.

    2. At the command prompt, type a command in the following form, and press ENTER.

      gacutil.exe -if "<Full file system path to DLL>".

  10. Now you are ready to modify the assembly information in the default Service.asmx file of the Web service by using information about the DLL that can be found in the GAC. To get information from the GAC, open the %windows%\assembly directory in Windows Explorer, right-click your assembly, and click Properties.

  11. To open Service.asmx in Solution Explorer, right-click the file and click Open.

  12. Remove the CodeBehind attribute from the page directive in Service.asmx, and modify the contents of the Class attribute so that the directive matches the following format, where the assembly name "MyServiceAssembly" and the public key token are values specified in the Properties dialog box that you opened in step 10.

    <%@ WebService Language="C#" Class="Service, MyServiceAssembly, Version=, Culture=neutral, PublicKeyToken=8f2dca3c0f2d0131" %>

    In Visual Basic, include the namespace to identify the class, for example, Class="MyServiceNamespace.Service, MyServiceAssembly, Version=, Culture=neutral, PublicKeyToken=8f2dca3c0f2d0131".

  13. Rename your .asmx file appropriately, and then save your changes.

Generating and Modifying Static Discovery and WSDL Files

To provide discovery and description for your custom Web service, you must create a .disco file and a .wsdl file. Because SharePoint Foundation virtualizes its URLs (for example, http://MyServer/MySite/MySubsite becomes http://MyServer), you cannot use the .disco and .wsdl files that are autogenerated by ASP.NET. Instead, you must create a .disco page and a .wsdl ASPX page that provide the necessary redirection and maintain virtualization.

You can use ASP.NET to generate the .disco and .wsdl files by temporarily hosting your Web service in a virtual directory, such as /_layouts, and then by using the Microsoft .NET Framework Web Service Discovery tool (Disco.exe) to obtain the generated files.

To generate and edit the static discovery and WSDL files

  1. In Windows Explorer, copy the .asmx file of your Web service to %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS.

  2. Run Disco.exe at the command prompt from the LAYOUTS directory to generate .disco and .wsdl files. Run a command in the following format to generate the files in \LAYOUTS:

    disco http://MyServer/_layouts/MyCustomWebService.asmx

  3. To register namespaces of the SharePoint Foundation object model, open both the .disco and .wsdl files and replace the opening XML processing instruction -- <?xml version="1.0" encoding="utf-8"?> -- with instructions such as the following.

    <%@ Page Language="C#" Inherits="System.Web.UI.Page" %> 
    <%@ Assembly Name="Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> 
    <%@ Import Namespace="Microsoft.SharePoint.Utilities" %> 
    <%@ Import Namespace="Microsoft.SharePoint" %>
    <% Response.ContentType = "text/xml"; %>
  4. In the .disco file, modify the contract reference and SOAP address tags to be like the following example, which replaces literal paths with code generated paths through use of the Microsoft.SharePoint.Utilities.SPHttpUtility class, and which replaces the method name that is specified in the binding attribute.

    <contractRef ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request) + "?wsdl"),Response.Output); %> 
    docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %> 
    xmlns="" />
    <soap address=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %> 
    xmlns:q1="" binding="q1:HelloWorld" xmlns="" />
    <soap address=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %> 
    xmlns:q2="" binding="q2:ServiceSoap12" xmlns="" />
  5. In the .wsdl file, make the following similar substitution for the SOAP address that is specified.

    <soap:address location=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(SPWeb.OriginalBaseUrl(Request)),Response.Output); %> />
  6. Rename both files in the respective formats MyCustomWebServicedisco.aspx and MyCustomWebServicewsdl.aspx so that your service is discoverable through SharePoint Foundation.

Deploying the Web Service Files to the _vti_bin Directory

The _vti_bin virtual directory maps physically to the %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\ISAPI directory, which contains the default Web service files that are used in SharePoint Foundation. Copy the new MyCustomWebServicewsdl.aspx and MyCustomWebServicedisco.aspx files, and also the MyCustomWebService.asmx file, to the ISAPI folder.

From the _vti_bin directory, a Web service offers its functionality to the site that is specified when adding a Web reference for the service.

To verify that your custom Web service is discoverable, navigate to http://MyServer/_vti_bin/MyCustomWebService.asmx.

Listing the New Web Service in spdisco.aspx

To make your Web service discoverable in Visual Studio as a Web service along with the default SharePoint Foundation Web services, open the spdisco.aspx file that is located in %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\ISAPI and add the following code, specifying the .asmx file for your Web service.

<contractRef ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/MyCustomWebService.asmx?wsdl"), Response.Output); %> 
docRef=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/MyCustomWebService.asmx"), Response.Output); %> 
xmlns=" " />
<discoveryRef ref=<% SPHttpUtility.AddQuote(SPHttpUtility.HtmlEncode(spWeb.Url + "/_vti_bin/MyCustomWebService.asmx?disco"),Response.Output); %> 
xmlns="" />

Creating a Windows Application to Consume the Web Service

After you copy the Web services files to the _vti_bin directory, the next step is to create a Windows Application to consume the Web service.

To create a Windows Application that consumes the Web service

  1. Open Visual Studio, and on the File menu, point to New, and then click Project.

  2. In the New Project dialog box, select Visual C# or Visual Basic, and then select the Windows Forms Application template.

  3. Type a name for the application in the Name box, specify a location for the project files in the Location box, and then click OK.

  4. In Solution Explorer, right-click the project, and then click Add Service Reference.

  5. In the Add Service Reference dialog box, click Advanced, and in the Service Reference Settings box, click Add Web Reference.

  6. In the address bar of the Add Web Reference browser, type the URL for the site to apply the service to, as follows,


    and then press ENTER.

  7. Click Add Reference to download the service contract for the Web service.

  8. Open Form1 in Design view, display the Toolbox, and then drag a button onto the form.

  9. Double-click the Button1 control on Form1 to display the code-behind file in the code editor, and add the following code that calls your custom method.

    Dim MyCustomService As New Web_Reference_Folder.MyServiceClass()
    MyCustomService.UseDefaultCredentials = True
    Web_Reference_Folder.MyServiceClass MyCustomService = new Web_Reference_Folder.MyServiceClass();
    MyCustomService.UseDefaultCredentials = true;
  10. Press F5 to compile and run the project and see a message box that displays "Hello World".

Implementing the SharePoint Foundation Object Model

Now you are ready to try out types and members of the SharePoint Foundation object model in the class library of your Web service.

To implement the SharePoint Foundation object model

  1. Add a reference to the Microsoft.SharePoint assembly. Right-click the class library project in Solution Explorer, click Add Reference, select SharePoint Foundation, and then click OK.

  2. In your project Service.cs or Service.vb file, you must import the appropriate namespaces in the object model. For example, to use types and members of the Microsoft.SharePoint and Microsoft.SharePoint.Utilities namespaces, add the following directives.

    Imports Microsoft.SharePoint
    Imports Microsoft.SharePoint.Utilities
    using Microsoft.SharePoint;
    using Microsoft.SharePoint.Utilities;
  3. Rename the method in Service.cs or Service.vb. For example, change the name from HelloWorld to GetSiteListCount.

  4. Add the following code to display the name of the Web site and the number of lists that it contains.

    Dim myWebSite As SPWeb = SPContext.Current.Web
    Dim lists As SPListCollection = myWebSite.Lists
    Return myWebSite.Title + " contains " + lists.Count.ToString() + 
    " lists."
    SPWeb myWebSite = SPContext.Current.Web;
    SPListCollection lists = myWebSite.Lists;
    return (myWebSite.Title + " contains " + lists.Count.ToString() + 
    " lists.");


    If your code modifies SharePoint Foundation data in some way during an HttpGet request, you may need to allow unsafe updates on the Web site, which you can do by setting the AllowUnsafeUpdates property.

  5. To rebuild the class library DLL and copy it to the GAC, repeat steps 8 and 9 in "To create an ASP.NET Web service."

  6. Reset Internet Information Services (IIS) for changes in the DLL to take effect.

  7. To generate new versions of the .disco and .wsdl files, repeat the steps in "To generate the static discovery and WSDL files," but change the method binding name in the .disco file as appropriate, for example, to GetSiteListCount.

  8. Copy the new versions of the MyCustomWebServicedisco.aspx and MyCustomWebServicewsdl.aspx files to the ISAPI folder.

  9. Open the Windows application that you created previously, delete the previous Web service reference for the Hello World example, change the method name as appropriate, and add a new Web reference to the revised Web service.

  10. Press F5 to compile and run the project and see a message box that displays the Web site name and the number of lists that it contains.