Another round begins.

(Note: The title is irrelevant to the content of the article)

I personally think that learning workflow is to learn the train of thought and the train of thought for solving problems.

Net programmers like to rely on products released by MS, JAVA Programmers like to do their own, each has its own advantages and disadvantages

Some people say they want to wait for the official version of WWF to learn more,

However, WWF will never have the final official version, because the activity of exploring things solutions will never stop.

I like WWF very much, because it is not a final solution provided by MS to programmers, but a platform provided by MS for programmers to solve problems independently. From this point on, MS has actually improved.

I first posted a Tracking article ................

When learning Tracking classes, do not learn methods, learn events, and learn attributes as before. First, read the library structure and table structure of Tracking, and then include the information as needed, if you find it inconvenient to use the jobs that come with Tracking, you can rewrite them. You can also directly operate on the database and add custom tables to the Tracking database for your own needs, add custom fields and triggers to their own tables. write an independent engine in parallel with WWF.
In this way, you will find that all code is written for your needs. What you see in your mind is no longer a method parameter but a business behavior.

When learning Tracking, open SQL event Tracking and follow the heartbeat of WWF to see how WWF methodically expresses complex behaviors in a relational structure.
Bytes ------------------------------------------------------------------------------------------------------

In addition, I wrote a simple example of using State, EventDriven, Code, ifElse, and While in a State machine to learn about WWF, it is still detailed. You only need to use VS2005 to get started.

I wrote an example.