Refer to Choosing WCF or Web API for additional information on WCF and Web API.
This presentation project provides a WCF service interface compatible with 1.2 SOAP clients for a ClearPath Data Source application. This type of service may have an intimate dependency on ASP.Net session state and requires ASP.Net compatibility mode to function correctly.
This project uses aspNetCompatibility mode. The Web.config file comes configured with a basicHttpBinding with default security. Security is enhanced by deploying the application with SSL as a requirement or by modifying the parameters under security in the Web.config file.
Procedure 1 - Creating a WCF ASP.Net Compatibility Service Application
In Solution Explorer, right-click the solution node, click Add, click New Project....
In the Create a new project dialog box, do the following:
Notes:
Select C# or All Languages from the Language list.
Select Windows or All Platforms from the Platform list.
The ePortal templates are not displayed if other values are selected.
Select ePortal Previous Versions from the Project Type list.
The ePortal Previous Versions templates are displayed.
Do any one of the following to select the template:
From the templates list, select WCF ASP.Net Compatibility Service Application, and then click Next.
Enter WCF ASP.Net Compatibility Service Application in the search option, select the template from the search result, and then click Next.
Optionally, change the Project name, Location, and Framework, and click Create.
Notes:
If you do not select a desired Framework, a default Framework version is selected.
For information on selecting the .NET version, refer to Multi-Targeting Issues.
On the Presentation Generation Options dialog, enter values for the generation. Refer to Presentation Generation Properties for a WCF ASP.Net Compatibility Service Application.
Click OK. The presentation project appears in Solution Explorer.
Procedure 2 - Building the Project
In Solution Explorer, right-click the WCF ASP.Net Compatibility Service Application project node, and then click Build. Refer to Building Your ePortal Solution for more information.
When the project is built, ePortal generates the files to implement a Web Services Application based on the data source.
Refer to Consuming the Web Service Methods by a Web Service Client for information about using the methods in a Web service client.
Generated Files
Building the project generates the following files:
In the App_Data directory: data source specific data files
In the project root directory: Service.svc, ApplicationInfo.xml file, epconfig files, epuo file and Web.config. The Web.config file specifies the endpoint, binding, behavior, and security of the Web Service.
In the App_Code directory: IService.cs, Service.cs. IService.cs contains the definition of the service contract. Service.cs contains the code that implements the service contract.
Procedure 3 - Preparing to Use the Presentation Project
To prepare the use the project, do the following:
Modify the Web.config file.
Perform custom programming, if required.
Modifying the Web.config File
For this project type, the Web.config file comes configured with basicHttpBinding (name=AspcompBinding).
For information on the use of this binding refer to Modifying the Web.config File.
Performing Custom Programming
When you create and build the project, ePortal Developer generates code to implement your service. Refer to Controlling the Runtime Behavior for WCF and WCF ASP.Net Services for information for customizing this implementation.
Procedure 4 - Testing
Refer to Testing a Presentation Project.
Procedure 5 - Modifying the Service.svc File
When you build the solution, ePortal Developer sets the Service.svc file as the following example shows:
<%@ ServiceHost Language="C#" Debug="true" Service="WcfAspService1.Service" Factory="ServiceFactory" CodeBehind="~/App_Code/Service.cs, WebSupport.dll" %>
Before you stage the Web site to ePortal, set the Debug option to false.
Next Step