workflow-foundation

I need to build an app that gets files from a server and moves to another server. It was suggested that I look into using Windows Workflow Foundation (WF). I started to build the workflow but it is getting messy and I'm not sure I'm doing it the best way possible. Here is the basic worklow activities: Get a list of sources Determine if source is ftp or disk drive Get a list of files from the server If source is ftp then get the file with ftp get else if source is drive then read file from drive If target is ftp then ftp file to server else if target is drive then write to a drive else if

There is a pretty strong need for us to design some workflows around various processes. The problem is none of us actually know any workflow technology yet, and finding good data to compare the available options has been tedious and not entirely fruitful. So I figured I'd ask you guys. The main technologies we are looking at are Windows Workflow Foundation and eDocs Workflow. What other options are there? Sharepoint 2007 has workflow functionality too, right? Is that just based on WF? What are the pros and cons of the various technologies? How do they compare? EDIT: Also, one feature the

What Java alternatives are there to Windows Workflow Foundation? I am looking for something that provides at least the same features that WWF does, and has the same flexibility and relative ease of use. I would very much prefer a free solution. Jim Blizard There are several great workflow engines for Java JBPM is one. Others can be found here . We've used OSWorkflow and had success with it. In particular, it was easy to integrate with Spring and Quartz. http://www.opensymphony.com/osworkflow/ 来源： https://stackoverflow.com/questions/762499/java-alternative-to-windows-workflow-foundation

I am currently saving my .NET FX 4.0.1 StateMachine activity like this: var sb = new StringBuilder(); var xamlWriter = ActivityXamlServices.CreateBuilderWriter( new XamlXmlWriter(new StringWriter(sb), new XamlSchemaContext())); XamlServices.Save(xamlWriter, activityBuilder); return sb.ToString(); This works fine and the generated XAML looks good. Unfortunately, it is invalid. I can read it back in using ActivityXamlServices.Load but when I execute it, it says that it doesn't know the properties defined in the workflow. Opening it in the Visual Studio designer yields the same errors: Compiler

We are in the process of selecting a workflow solution for a company that uses Microsoft products end to end. Given the news on WF4, in that it seems to be essentially a rewrite of previous versions, is it a wise move to back the current version or should we be looking elsewhere? Ie - is the current version so bad that we would not be wise to try and use it? gbanfill Haiving just launched a project which .NET 3.5 and workflow I'd say that the current release of WF is good enough to use and run with. It has helped us to get a product out quickly (we have the usual feature creep and requirements

Related to this question . I understand how to implement versioning of workflows using WorkflowApplication . If you keep the original XAML definition for older versions of your workflow around, you can load them using the right WorkflowApplication constructor. How could you ensure that WorkflowServiceHost uses the correct workflow definition when you want to host your workflows in IIS? There is a WorkflowServiceHost constructor that you can use to load a workflow definition, but when you are hosting inside IIS through a XAMLX file, you do not call WorkflowServiceHost yourself, this is handled