You define basic properties for a WCF Services project when you create its target in the WCF Service wizard. You can define and modify all its properties later using the Project painter.
Most of the settings in this tab are also defined in the WCF Service target wizard.
Setting | Description |
---|---|
Project name | Name of the project object the wizard creates. |
Library | Name of the library directory the wizard creates. By default, this includes the current solution path and takes the name you enter for the project object with a PBL extension. |
Target | Name of the target the wizard creates. By default, this includes the current solution path and takes the name you enter for the project object with a PBTX extension. |
Library search path | Lets you add PBL directories to the search path for the new target. |
WCF service assembly name | File name of the WCF service assembly. The WCF service assembly is created in the output directory. For an IIS host, it is also copied to the virtual directoy. |
Output directory | The full path where the service is deployed. |
Application file name | The console application file name. This .exe
file is created in the output directory. Note: Do not specify the
same name as the assembly
file.
|
Base address | For console hosts only. The base URL for deployed WCF Services.
Use this syntax: [transport protocol]://[machine name or domain name][: port number] For example:
http://localhost:8001 net.tcp://localhost:8002 net.pipe://localhost You
can deploy multiple WCF Services under the base address. For
example:
http://localhost:8001/MyService http://localhost:8001/MyOtherService |
Web service virtual directory name | The virtual directory name that the IIS-hosted WCF Service is deployed to. |
Service URL preview | Automatically displays the URL accesses the service, based on the virtual directory name. |
Build type | Choose either Debug or Release. |
Options | Any of these settings: Use .NET nullable types – Maps PowerScript standard datatypes to .NET nullable
datatypes when selected. Nullable datatypes are not
Common Type System (CTS)-compliant, but they can be used
with .NET Generic classes if a component accepts or
returns null arguments, or if reference arguments are
set to null. Enable DEBUG symbol – Choose this option if the nonvisual objects you deploy
as a Web service contain code with the DEBUG conditional
compilation symbol, and you want this code to run. Verify CLS compliance – If you choose this option, the PowerBuilder to .NET
compiler (pb2cs) sets CLSCompliantAttribute to true for
the component, and the C# compiler applies Common
Language Specification (CLS) rules to the public methods
of the component. If you set this value for a component
that is not CLS-compliant, the compiler issues the
appropriate warnings. |
Deployment options | Choose one of these deployment modes, also specified in the
wizard: Setup file name – If you enter a file name with no path information, the
file is created in the directory where the PowerBuilder
target file exists. If you enter a file name with the
path, make sure that the directory exists before
deployment begins. Deploy directly to IIS – Enter the machine name or IP address of an IIS
server. |
To implement a WCF Service, you must define its properties in the Objects tab. The tree view on the left of the tab lists the available NVOs. Select an NVO to set its Web service name and target namespace, and to specify which functions to expose as Web service methods.
NVO icons in the tree view indicate which NVOs are configured and to be deployed; NVOs without the icon are not deployed.
The remaining tabs in the Project painter are identical to the same tabs in the .NET Assembly Project painter.