Search

Search:

Namespace:

Search Result
.

You can use the workflow communication activity command-line utility, wca.exe, to generate interface specific subclasses.

.

The Windows Workflow SDK includes a command line tool called the Windows Workflow Communications activity generator. This tool runs from the command line, and you can find it in the SDK directory with a name of wca.exe.

.

We can pass wca.exe the path to a .NET assembly (.dll) and the tool will look through the assembly for interfaces decorated with the ExternalDataExchange attribute. When the tool finds such an interface it will generate dedicated activities for calling the methods and handling the events of the interface.

.

Run wca.exe with no parameters to see a list of options.

.

The Windows Workflow SDK includes a command line tool called the Windows Workflow Communications activity generator. This tool runs from the command line, and you can find it in the SDK directory with a name of wca.exe.

.

We can pass wca.exe the path to a .NET assembly (.dll) and the tool will look through the assembly for interfaces decorated with the ExternalDataExchange attribute. When the tool finds such an interface it will generate dedicated activities for calling the methods and handling the events of the interface.

.

Run wca.exe with no parameters to see a list of options.

.
Summary
.

The workflow communication activity generator command-line utility, wca.exe, is used to generate strictly bound communications activities from a compiled ExternalDataExchange interface. Whereas the HandleExternalEventActivity and CallExternalMethodActivity activities can both be used directly to handle generic communications in a workflow, the ExternalDataExchange interface strictly bound derived activities provide a better designer experience. These activities improve performance by removing the use of reflection and easing customization for frequently used ExternalDataExchange interfaces.

.

For each operation on the ExternalDataExchange interfaces in the input assembly, wca.exe generates code for the corresponding activity. Events on the interface become derivatives of HandleExternalEventActivity, and methods become derivatives of CallExternalMethodActivity.

.

The wca.exe tool provides the command-line parameters /collapseArgs and /includeSender to determine how the HandleExternalEventActivity subclass properties appear. The /collapseArgs parameter causes a single E property of the EventArgs type to be generated instead of the default, which generates one property on the activity for each public property and field of the EventArgs. The /includeSender parameter includes a Sender property on the activity of type object, which is populated by the sender parameter of the event handler.

.

The output files of the wca.exe tool can be compiled, without editing, to create strictly bound activities that are ready to use. The output files can be set to either the C# or the Visual Basic language by the /language command-line parameter. For a full list of available options, run wca.exe with the /? parameter, for example C:\wca.exe /?.

.

You can use the workflow communication activity command-line utility, wca.exe, to generate interface specific subclasses.

.

Use this utility to generate activities to work with ExternalDataExchange services. Basically you need to create your interface, decorate it with the ExternalDataExchange attribute and compile that. Next you run wca.exe against the generated assembly and this will produce two source files, one to call the external methods (the Invokes file) and a second to receive the events (the Sinks file).