Note: This topic applies to a WCF Service Application using scaffolding only. Refer to Creating a WCF Service Application using Scaffolding for more information.
Scaffolding is the technique used to generate the presentation code that the application can use at run time. The generated code represents a useful starting point for your application that you may want to further modify to refine the application.
Refer to the following topics for more information:
To scaffold one or more data sources in your presentation project, do the following:
Click Build and select Build Solution to build the solution.
In Solution Explorer, right-click the WCF service project, select Add, then select New Scaffolded Item.
The Add Scaffold dialog opens.
On the Add Scaffold dialog, select Unisys WCF Service for ePortal Data Source and click Add.
The Scaffold Unisys WCF Service for ePortal Data Source Dialog opens.
Complete the dialog as described below.
After completing the dialog fields, click OK to start scaffolding.
Note: If scaffolding would overwrite any existing files, you are given a chance to confirm before overwriting.
Dialog Fields
The dialog fields are described below:
ePortal Data Source
Select the name of the data source to scaffold from the dropdown list.
Note: If you do not see the data source project you are looking for, ensure that the data source project is opened in the current solution and a reference has been added. Refer to Using Multiple Data Source Projects for more information.
Service scaffolder
Select the scaffold template to use to generate the service code from the dropdown list. Refer to Scaffold Templates and Creating Custom Scaffold Templates for more information.
Service name
Enter the name for the service.
Note: If you change the default setting, you must edit the Web.config file to update the service element to match the name you select here. Refer to Modifying the Web.config File for more information.
Service namespace
Enter the namespace to use for the Web service.
Each XML Web Service needs a unique namespace in order for client applications to distinguish it from other services on the Web. By default, ASP.Net Web Services use http://tempuri.org/ for this purpose. While this is suitable for XML Web Services under development, published services should use a unique, permanent namespace.
Your XML Web Service should be identified by a namespace that you control. For example, you can use your organization's Internet domain name as part of the namespace. Although many namespaces look like URLs, they do not need to point to actual resources on the Web.
Contract name
Enter the externally visible name of the service contract.
Contract namespace
Enter the namespace of the service contract.
See Service namespace above for information about selecting an appropriate namespace.
Web method prefix
Enter the prefix to apply to the web methods used to submit a message to the web service.
Session required
If the web service requires a session (that is, is a stateful application), select this option.
Code file name
Enter the name of the service code file to be generated.
Implementation namespace
Enter a C# identifier to serve as the namespace to use for the Web service project code.
Note: If you change the default setting, you must edit the Web.config file to update the service element to match the name you select here. Refer to Modifying the Web.config File for more information.