Handling concurrent development of workflows

Hot Topic

GeForce 6600 related Issue - Bug Report
Oct CTP Build of Vista?
Problem with "The Goods"
Workflow temporary persistence: Session?
Exchanging parameter enter the state machine workflow and the host application (web)
WF Runtime and Sharepoint Services 2.0
Userland access to avc.sys without writing a filter driver
Lab 03 - Exercice 3
Is WF right solution for high-throughput OLTP?
Call TrackData in CustomActivity on Another Thread

Windows Vista

Errors Installing Visual Studio 2005 on Vista build 5112
Error Tooltip Glyph using WorkflowDesignerControl
Dual Display Suggestion
Defining Bitmap of custom activity
ConditionalExpression in if-else-branch Activity
How to create a Custom directshow source filter
starting questions...
Vista 5308 Feb CTP installation issues.
WF Runtime and Sharepoint Services 2.0
(Beta2) How to bind WF params to activity properties at runtime?

Handling concurrent development of workflows

Hi,
how does everyone handle several developers working on the same workflow
We're developing a code based state machine workflow and need several developers to concurrently
change different parts of the workflow. However, due to the generated components (.designer.cs but mainly .resx and .layout) the merging is almost impossible.
How are people handling this
Would using a XOML based workflow be more appropriate If so, is there a way to convert an existing
code based wf to XOML

Thanks
--
Nuno

Answer this question

Handling concurrent development of workflows

  • RonFarley

    So, that allows me to convert the workflow from code based to xaml.
    What about the original question, doesn't anyone have problems having multiple developers working
    on a wf Or is everybody using XAML

    --
    Nuno

  • sqlizer

    I would think about this problem the same way you would approach web development. In a web application, you're going to have a lot of moving parts, the pages themselves, the database, the data layer, business layer, config, etc. By leveraging source control as well as modularization of your functionality, you can attempt to minimize the amount of "collisions" between developers (and the need to merge).

    If the bulk of your work is in activity development, your developers can work within the same project and not collide by assigining an activity to an individual. Another individual can work to incorporate those into the workflow as those are developed, and another can work on the communication between the host and the workflow. In this case, all three developers are working on the same workflow, but are in different files in the project (and you could separate things out into individual projects as well).



  • Ender Koroglu

    Numo,

    I think the following sample should help you:

    http://www.masteringbiztalk.com/blogs/jon/PermaLink,guid,9b1706ff-c3e9-4283-8e60-ae8eb73f3e1e.aspx

    Serge Luca

    Guidance, Belgium

    blog : www.redwood.be



  • Handling concurrent development of workflows
Answer this question