When a WCF Web Service project is scaffolded or built, code files that contain the service contract (as a C# interface) and implementation (as a C# class) are generated.

For the WCF Service Application using Scaffolding, the generated files are I<Service>.cs and <Service>.svc.cs in the root of the project, where <Service> is the name that you specified on the Scaffold Unisys WCF Service for ePortal Data Source Dialog for the Code file name. Similarly, the names of the generated interface and and classes in the code files matches the value you specified on the scaffold dialog.

For all other WCF projects, the generated files are IService.cs and Service.cs in the App_Code folder of the project; the names of the code files, interfaces, and classes are hard-coded.

The IService code file declares the partial interface IService, and the Service code file implements IService as a partial class Service. By using partial interface and class definitions, the user is allowed to extend the interface and class.

In separate files, additional partial interface IService and partial class Service code can be written to add Data Members to the Data Contract, methods to the Operation Contract and to implement the Service Behavior for the methods.

Adding a method

Add New Item, C# class, to the App_Code directory. Set the Build Action to compile. Add the following code:

using System;
using System.ServiceModel;

namespace WcfService1
{
    partial interface IService
    {
// If RequiresSession is false use this attribute
[OperationContract]
// If RequiresSession is true use this attribute
        [OperationContract(IsInitiating = false, IsTerminating = false)]
        String Hello(String name);
    }
    public partial class Service : IService
    {
        public String Hello(String name)
        {
            return "Hello " + name;
        }
    }
}

The namespace must be the same as the namespace used in your project.