WCF (Windows Communication Foundation) - 2.0

Extension ID


What’s new?

See WCF - 2.0 - Release Notes for more information.


This extension provides support for WCF (Windows Communication Foundation). The calculation of Automated Function Points for your .NET analyses will be supplemented through the creation of new objects and links specific to the WCF framework that will link back to objects/links produced by the base .NET Analyzer.

In what situation should you install this extension?

If your .NET application contains WCF (Windows Communication Foundation) source code and you want to view these object types and their links, then you should install this extension.

WCF framework support

The following WCF frameworks are supported by this extension:

Version Supported
All versions up to 4.5 ✔️

Function Point, Quality and Sizing support

This extension provides the following support:

  • Function Points (transactions): a green tick indicates that OMG Function Point counting and Transaction Risk Index are supported
  • Quality and Sizing: a green tick indicates that CAST can measure size and that a minimum set of Quality Rules exist
Function Points (transactions) Quality and Sizing
✔️ ✔️

A Transaction definition is automatically imported when the extension is installed. This definition will be available in the CAST Transaction Configuration Center.


CAST Imaging Core release Supported Technology
8.3.x ✔️ C# and VB.NET

Download and installation instructions

The extension will be automatically downloaded and installed in CAST Imaging Console. You can manage the extension using the Application - Extensions interface:

What results can you expect?


Icon Description
WCF Configuration
WCF Client Endpoint
WCF Service Endpoint
WCF Operation Contract
WCF Service Contract
WCF Service
WCF Operation Method Delete
WCF Operation Method Get
WCF Operation Method Post
WCF Operation Method Put
WCF Post Resource Service
WCF Data Contract

Configuration objects

Configuration objects are mapped on the Web.config or App.config file available in the csharp project:

        <service name="TrailService.Service2">
             <endpoint address="http://localhost:59364/Service2.svc/Service2WebConfig" binding="basicHttpBinding" bindingConfiguration="HttpBinding" contract="TrailService.IService2"></endpoint>
                    <add baseAddress="http://localhost:59364/Service2.svc/Service2WebConfig" />

      <service name="TrailService.CalculatorService">
        <endpoint address="CalculatorService" binding="basicHttpBinding" bindingConfiguration="HttpBinding" contract="TrailService.ICalculator"></endpoint>
        <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />
            <add baseAddress="http://localhost:59365/Service1.svc/" />
                <add baseAddress="http://localhost:59365/Service1.svc/dummy" />
          <endpoint address="http://localhost:59363/ClientService/ClientService"
                binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding_IClientService"
                contract="IClientService" name="BasicHttpBinding_IClientService" />

Operation objects

The following .NET code is supported:

[ServiceContract(Namespace = "http://Microsoft.ServiceModel.Samples")]
public interface ICalculator
    double Add(double arg1, double arg2);
    double Sub(double arg1, double arg2);
    double Mul(double arg1, double arg2);
    double Div(double arg1, double arg2);

Four “WCF Operation Contract” operations are created with urls constructed from interface namespace, interface name and method names.

    public interface IRestServiceImpl
        [WebInvoke(Method = "PUT", ResponseFormat = WebMessageFormat.Json, BodyStyle = WebMessageBodyStyle.Wrapped, UriTemplate = "todos/{id}")]
        void UpdateTodos(string id);

A “WCF Operation PUT” operation is created from UriTemplate parameter:

  • todos/{id}
    public interface IRestServiceImpl
        [WebGet(UriTemplate = "/todos")]
        void GetTodos();

A “WCF Operation GET” operation is created from UriTemplate parameter:

  • todos

Resource service objects

The following .NET code is supported:

    [System.CodeDom.Compiler.GeneratedCodeAttribute("System.ServiceModel", "")]
    [System.ServiceModel.ServiceContractAttribute(Namespace="http://Microsoft.ServiceModel.Samples", ConfigurationName="ServiceReferenceTrailService.ICalculator")]
    public interface ICalculator {
        [System.ServiceModel.OperationContractAttribute(Action="http://Microsoft.ServiceModel.Samples/ICalculator/Add", ReplyAction="http://Microsoft.ServiceModel.Samples/ICalculator/AddResponse")]
        double Add(double arg1, double arg2);
        [System.ServiceModel.OperationContractAttribute(Action="http://Microsoft.ServiceModel.Samples/ICalculator/Sub", ReplyAction="http://Microsoft.ServiceModel.Samples/ICalculator/SubResponse")]
        double Sub(double arg1, double arg2);
        [System.ServiceModel.OperationContractAttribute(Action="http://Microsoft.ServiceModel.Samples/ICalculator/Mul", ReplyAction="http://Microsoft.ServiceModel.Samples/ICalculator/MulResponse")]
        double Mul(double arg1, double arg2);
        [System.ServiceModel.OperationContractAttribute(Action="http://Microsoft.ServiceModel.Samples/ICalculator/Div", ReplyAction="http://Microsoft.ServiceModel.Samples/ICalculator/DivResponse")]
        double Div(double arg1, double arg2);

Four “WCF POST resource service” resource services are created with urls constructed from “Action” OperationContractAttribute parameter.

  • http://Microsoft.ServiceModel.Samples/ICalculator/Add
  • http://Microsoft.ServiceModel.Samples/ICalculator/Sub
  • http://Microsoft.ServiceModel.Samples/ICalculator/Mul
  • http://Microsoft.ServiceModel.Samples/ICalculator/Div

Data contract object

    [DataContract(Namespace = "")]
    public class AddressDetails
        public string Street1 { get; set; }

        public string City { get; set; }

        public string Country { get; set; }

        public string PostalCode { get; set; }

Source Link type Target Example
.NET Interface or class referLink WCF Service Endpoint
WCF Operation referLink WCF Service Endpoint
.NET Interface or class referLink WCF Client Endpoint

All links are “callLink” type.

  • from the .NET method to the WCF resource service corresponding to the method.
  • from the WCF operation to the .NET method corresponding to the operation.
  • from the WCF resource service to the WCF operation. This last link is created by the “web service linker” extension comparing the urls which are matching.

Links are:

  • accessWriteLink from the .NET class constructor to the WCF Data contract object.
  • accessReadLink from each .NET getter of each property of the class to the WCF Data contract object.
  • accessWriteLink from each .NET setter of each property of the class to the WCF Data contract object.

If a property has no getter or setter:

  • accessReadLink from the property to the WCF Data contract object.

Structural rules

The following structural rules are provided:

Release Link
2.0.11-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.11-funcrel
2.0.10-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.10-funcrel
2.0.9-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.9-funcrel
2.0.8-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.8-funcrel
2.0.7-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.7-funcrel
2.0.6-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.6-funcrel
2.0.5-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.5-funcrel
2.0.4-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.4-funcrel
2.0.3-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.3-funcrel
2.0.2-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.2-funcrel
2.0.1-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.1-funcrel
2.0.0-funcrel https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.0-funcrel
2.0.0-beta1 https://technologies.castsoftware.com/rules?sec=srs_wcf&ref=||2.0.0-beta1


In this section we list the most significant functional limitations that may affect the analysis of applications using WCF:

  • If the configuration of WCF service is done through the code (endpoint configuration, service creation), this is not supported.
  • Concerning rules about configuration, violations are reported only if violations are in configuration files or in CSharp code, but not in VB code.