Weighing pros and cons of using WF for our new flowcharting application
Posted on 2010-09-21
We are creating a new ASP.NET MVC2 application where various workflows have been flowcharted, so that our completed code will fullfill those workflows. We are considering coding this with good old fashioned Objects OR using Workflow Foundation. One con for WF, according to our team, is the learning curve, although it looks like it wold be pretty short to me.
After we coded the flowcharts in WF designer, how easy is it to use those WF flowcharts as a reference? I mean if we would write our own GUI, and keep the flowcharts in the background, would tha t save us loads of programming effort?
I expect that it would, but I am not the decision maker. Instead I am trying to get real world advice from other developers who have used this new tool (WF 4.0).
Please give me your thoughts.