-
| The Best from DevelopMentor | MORE |
- 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 - 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 - Flowcharts in Workflow 4 and the Switch activity
Flowcharts are a nice addition to Windows Workflow Foundation 4. They allow for a lot of pretty complex behavior that is hard to do in a sequential workflow. In WF 3 we used to model these complex behaviors as state machine workflows. Enter the flowchart in Windows Workflow Foundation 4 One of the good things is that a flowchart is not another workflow type. No it is just another activity to drop in a workflow. So you are free to combine sequential work with a flowchart in one workflow. Tags: NET Workflow WF4 VS2010 So far so good. Enjoy!
The Problem Solver - Tuesday, October 27, 2009 - Online Workflow 4 presentation
Attached are the PowerPoint sheets and samples from my online Window Workflow Foundation 4 presentation today. Tags: NET Workflow WCF webcast WF4 VS2010 Let me know if you have any questions. WF4Demo.zip www.TheProblemSolver.nl Wiki.WindowsWorkflowFoundation.eu.
The Problem Solver - Tuesday, December 1, 2009 - Flowing transaction into a workflow using WF4
Beta 2 One of the things that wasn’t possible in Windows Workflow Foundation 3 was flowing transaction over a WCF service request into a workflow. Fortunately that is one the problems that Windows Workflow Foundation 4 solves for us. In WF4 we can use the ReceiveAndSendreply template to configure a workflow as a service and accept WCF calls. If we want to use transactions we need to add the TransactedReceiveScope to the workflow. Tags: NET Workflow WCF WF4 VS2010 Beta2 Note: This blog post is written using the.NET framework 4.0 else. {. Enjoy!
The Problem Solver - Monday, December 21, 2009 - Workflow 4 and Visual Basic expressions
When using Windows Workflow Foundation 4 you often need to enter expression in some activity property. After all power business users are expected to be able to modify workflows. Well it turns out workflow is smart enough to realize it can convert the string literal to a Time Span and use this. Tags: NET NetFx3 Workflow VB WF4 VS2010 The new thing is these expressions are all in the Visual Basic dialect regardless of what language you project is in. So when developing a project in C# the expressions are sill in Visual Basic. Weird right? Not very VB like right?
The Problem Solver - Monday, October 26, 2009 - 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. The Name is used throughout the workflow to store and retrieve the data.
The Problem Solver - Monday, July 20, 2009
