browse.develop.com
Browse.develop.com is a community that was established to collect and organize valuable web information. Our technical staff have selected and indexed information and courses that they feel will help you stay current on best practices across the SDLC.

154 Articles match "Workflow"

  • The Best from DevelopMentor

    154 Results found
    Showing page 1 of 16   Next >

  • Windows Workflow Foundation 4 and persistence
    The persistence class out of the box is called SqlWorkflowInstanceStore and as the name suggests it saves workflow data in either SQL Server 2005 or 2008. We can attach it to either a WorkflowApplication or a WorkflowServiceHost and persist workflows when we want. This can be used to run only short lived workflows and doesn’t support persistence. var instanceStore = new SqlWorkflowInstanceStore(connStr); WorkflowApplication app = new WorkflowApplication(workflow); app.InstanceStore = instanceStore; app.Run(); Okay its a little more involved then that. Enjoy!
    The Problem Solver - Thursday, November 19, 2009
  • Versioning long running Workflow Services in WF4
    One of the problems with the current version of Windows Workflow Foundation is how to handle different versions of your workflows. With short running workflows this is no big deal, workflows do whatever they are supposed to do and finish, and you can deploy a newer updated version of your XAMLX files whenever you want. However as soon as we get into long running workflows and the SQL Workflow Instance Store things get quite a bit more complicated. It uses this data to differentiate between different workflow service definition. Unfortunately not.
    The Problem Solver - Thursday, November 4, 2010
  • Rehosting the Workflow Designer in WF4
    Beta 2 With Windows Workflow Foundation 3 it was possible to rehost the workflow designer in your own application. With Windows Workflow Foundation 4 live has become much better on the rehosting front In fact it is possible to create the fully functional and useful workflow editor below in about 200 lines of code. And loading or saving a workflow is easy to, all it takes is a Load() and Save() function pointing to a XAML file. One thing that is needed is to register the workflow activity designer metadata. Validating the workflow. null ). {.
    The Problem Solver - Wednesday, December 23, 2009
  • Workflow parameters in Window Workflow Foundation 4
    Creating parameters for a workflow is quite easy to do in WF 4. Just open the arguments tab in the workflow and add each input or output parameter you need and the required type. Now in WF 3 passing data to a workflow was done using a Dictionary to specify the input. Every time you create an in or out argument the workflow will also get a corresponding public property. Tags: Workflow WF4 VS2010 This is very flexible but also very brittle as it is all magic of key names matching property names. This approach still works as the following code demonstrates.
    The Problem Solver - Friday, October 23, 2009
  • Converting a C# workflow into XAML
    A interesting question that came up last week was how to convert workflows defined in C# to XAML. co worker of one of the attendees of the Essential Windows Workflow Foundation 4 course had been experiencing a lot of problems with the workflow designer and decided to create their workflows in C# instead of using the designer to generate XAML. While these workflows run just fine you do lose the visual aspect of the designer, one of the benefits of workflow in the first place. Take the following workflow defined in C#. Enjoy!
    The Problem Solver - Saturday, August 28, 2010
  • Versioning long running Workflow Services in WF4, the code
    In my previous WF4 post I described the principal of how to version workflow services using the WCF 4 RoutingService. The workflow service with 2 different versions of same workflow. The second version of the workflow has more activities in the tree so it can’t load workflow instances from version 1. Each workflow is hosted in a different XAMLX file and the second was created by copying the first and making the required changes to it. It knows about one existing workflow instance previously created and will create a new one. class Program. {.
    The Problem Solver - Tuesday, November 16, 2010
  • Hiding the XAMLX from a workflow service
    In Windows Workflow Foundation 4 it’s easy to create a workflow and expose it as a WCF service. But one thing is that it exposes a XAMLX endpoint to each client can see the service actually implemented as a workflow service instead of a regular service. One way to hide that is to use a regular SVC file as the implementation and point that to a workflow using the WorkflowServiceHostFactory. First we need to use a regular workflow instead of a workflow service. Tags: NET Workflow WCF WF4 VS2010 data]. data.ToString()]. Enjoy!
    The Problem Solver - Tuesday, May 18, 2010
  • Workflow Receive activity and message correlation
    With WF4 it is quite easy to use data that is part of the request message, for example an order identifier, to route multiple WCF messages to the same workflow. It is also possible to have multiple messages that can start a new workflow. In this blog post I am going to show both these concepts in a single workflow. This workflow is going to be able to receive three different messages, AddItem, AddExpensiveItem and Submit. Either AddItem or AddExpensiveItem can start a new workflow while Submit can only be done with an existing workflow. ReferenceID0.
    The Problem Solver - Wednesday, April 28, 2010
  • Workflow 4 and soap faults
    RC 1 Using the ReceiveAndSendReply activity template and the WorkflowServiceHost it is easy to create a workflow service. Other applications can communicate with the workflow just as if it is a regular WCF service, they never need to know the difference. Throwing a FaultException When a FaultException is thrown in a workflow service pretty much the expected thing is done. But with a workflow service there is no service contract class we can add the attribute to. So how do we specify the fault contract with a workflow service? But what about faults? Enjoy!
    The Problem Solver - Wednesday, March 24, 2010
  • Throttling workflow services in WF4
    Windows Workflow Foundation 4 makes it real easy to create workflow services that do long running work on a server. However when we are doing long running work there could be an issue with lots of workflows being started and to many workflow instances competing for the same data and threads thereby causing problems like database timeouts or thread pool starvation. originally expected the loop to quickly start 1000 workflows and the workflows to complete after 15 seconds. Throttling the Workflow Service. Creating a batch of Workflow Services.
    The Problem Solver - Wednesday, November 17, 2010
<< 1 2 3 ... 15 16 >>
%>