I\'ve successfully got a few workflows going with Server AppFabric. What i have noticed however is that when i try to use namePipeBinding to communicate with the workflow then the call works successf
I have a number of xaml sub-workflows that I would like to reuse in other xaml workflows. These sub-workflow use receive and send activities so writing them in code is a pain for us mortals.
I\'m having trouble finding any documentation on how the SqlWorkflowInstanceStore and how it handles retires.
Lets say i have an activity with InArgument<int> ProductId I\'d like to expose in the activity designer a combobox to show all Products and the user can select a product.
I have a workflow started and persisted using messaging activities. The correlation between the Start initial command and the Stop final command works well if they\'re sent within few seconds.
We have a business logic for managing the document life cycle. This is implemented using Workflow Foundation 4 and WF Persistence.
Let\'s say i have a workflow that has been executer on a WCF service, and its waiting for the user input for some value.
I have workflow with correlation. When I call twice some method with the same parameters i ha开发者_运维问答ve the following error:
In Workflow 3.x you can have a dependency property List<int> and in the designer you could click on the \"...\" and add values directly to the list<int>
I understand that the WorkflowDesigner can receive a dragged item in several ways, for example: By dragging an item from the toolbox and dropping it on the designer: an empty activity of that type w
加载中,请稍侯......