10 Articles match "Windows","Windows Workflow Foundation"

53 Articles match "Windows","Windows Workflow Foundation"

• The Best from DevelopMentor

  MORE

• Getting started with Windows Workflow Foundation 4
  
  As you may have heard Windows Workflow Foundation 4 is not an upgrade from Windows Workflow Foundation 3 (or 3.5). In fact Windows Workflow Foundation 3 was the first version and 3.5 That might be a bit surprising, after all we still have activities and a workflow runtime right? Creating workflows is done by creating a WorkflowInstance object. This object is raises events for that workflow and only for that specific workflow. For now just select the “Sequential Workflow Console Application”.
  The Problem Solver - Monday, June 22, 2009
  READ MORE
• 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
  READ MORE
• The new Windows Workflow Foundation 4 runtime
  
  With WF3 there was a central workflow runtime environment called the WorkflowRuntime and used to manage the lifetime of workflow instances. In WF4 this central class no longer exists and we manage individual workflows. It basically runs a workflow and prints a message when done: static void Main( string [] args). {. Console.WriteLine( "The workflow has completed." Console.WriteLine( "The workflow has completed." quot; ); }; myInstance.Run(); Console.WriteLine( "Waiting for the workflow to complete." Nice right!
  The Problem Solver - Tuesday, June 23, 2009
  READ MORE
• Activity correlation in Windows Workflow Foundation 4
  
  There are two types of correlation to think about in Windows Workflow Foundation: Message correlation Basically sending multiple requests to the same workflow. However sometimes we might need to do so ourselves because we create a workflow in a different way, like using regular code. How much varies and depends on both the workflow and the hosting environment we use. The obvious one is using the WorkflowApplication or WorkflowInvoker to run our workflows. Tags: NET Workflow WCF WF4 VS2010 Think about the Send and ReceiveReply activities.
  The Problem Solver - Wednesday, December 2, 2009
  READ MORE
• Passing data into a Windows Workflow Foundation 4 workflow
  
  Passing parameters into a workflow is similar in WF4 as it was in WF3. In both case a Dictionary is passed in when creating the workflow instance object. basically on the outside you have to create a dictionary with as key something inside of the workflow. keep in mind that workflows tend to be complex and long running things not very well suited to unit testing. Starting a workflow with a parameter: Shared Sub Main(). To allows us to pass data into a workflow, or get something out, we need to use an Argument. No compile time checking. myInstance.Run().
  The Problem Solver - Tuesday, June 30, 2009
  READ MORE
• Data and Windows Workflow Foundation 4
  
  One thing that has completely changed in Windows Workflow Foundation is the way we work with data in a workflow. Dependency properties left the way data was stored to be handled by the workflow runtime but in our program we could use them just like any other property. The actual data is stored somewhere inside of the workflow using a LocationEnvironment. To store some data inside of your workflow we need to add a Variable to the workflow or one of the nested activities. Creating the workflow using code. In WF 4 this has all changed!
  The Problem Solver - Monday, July 20, 2009
  READ MORE
• Using Windows Workflow Foundation 4 Receive from an non WF client
  
  In a previous blog post I described how to use the WorkflowServiceHost and host a workflow with a Receive activity that waits for WCF messages. However a lot of clients out there are not going to be workflows but “regular” code that calls into out workflow. In our workflow the operation is named “Operation1” and our service contact name was “MyService” with the default namespace of “ [link] ”. Using these WCF definitions creating a simple console app that calls the workflow is a breeze. Tags: NET NetFx3 Workflow WCF WF4 VS2010 interface MyService. {.
  The Problem Solver - Wednesday, August 19, 2009
  READ MORE