Weighing pros and cons of using WF for our new flowcharting application

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.

newbieweb
newbiewebSr. Software EngineerAsked:
Who is Participating?
 
Jaime OlivaresConnect With a Mentor Software ArchitectCommented:
You are right about the learning curve. But this should not be a barrier. It will take some few weeks to tame it.
The main benefit of WF is that you can change the workflow at any moment in a visual fashion, and the workflow engine complexities are handled by WF itself, not by you. So, you will have a moderate savings at the first time, but lot of time while mantaining your application.
About the GUI, WF is a backend facility, you have to build your GUI by yourself.
0
 
newbiewebSr. Software EngineerAuthor Commented:
Thanks a lot.
0
All Courses

From novice to tech pro — start learning today.