Windows Basics Should I use it?

Question

I am developing an application that I suspect is suitable for using a workflow. (Easily visualize the physical workflow and tasks between different users.)

My question is what are the advantages of using this method, do you recommend me to go along this route. Is there a better approach.

Did I hear the mention of a hit in the performance? Is this worth considering?

Finally, can anyone recommend a good book, which is a good introduction to the workflow?

UPDATE: A brief overview of my solution - basically it's a reservation / event / diary system. The "model" is periodically launched, which establishes the "passage" of users (H, M, L). Depending on the rating, how often the “adviser” visits the “user” depends. The requirement is to automate the appointment system, so a “preliminary” meeting is made by a “model”. The application will wait for a response confirming the appointment. The same situation with subsequent meetings, etc. Hope this is enough to help. Basically, control passes between the application and the user several times when organizing meetings.

I think an event-driven model would be most appropriate here? Any input is appreciated.

thanks

Answer 1

@Stuart , if your application needs to follow some series of discrete steps (workflow states), you can definitely use the Workflow Foundation (WF). You can keep the business process flow separate from the other logic in your application, making it loosely coupled and therefore easier to modify and improve.

If you can just decide using if-else to decide if the thread should go to the next step (state), all steps go linearly, then the Sequential workflow will be good. If you can go from one step to another when an event occurs and you can literally skip steps based on events, then State Machine workflow for you.

I read the Wrox-Professional Windows Workflow Foundation , created by Todd Kitta. This is a good book to start with. You can definitely get a ton of information and examples from the Workflow Foundation home on MSDN.