One step to learn WF series (2)-workflow and Visual Studio

1. workflow development style

In WF, there are three ways to develop workflows.

<1> markup-only

<2> code-and-Markup

<3> code-only

Here, I don't want to take the time to give an example.

The workflow layout is in The XAML format. I believe that those who know about WPF and sivlerlight know this clearly. In fact, this is the same as WF. This is the so-called markup-only mode.

The other extreme is code-only. We still want to think about examples in WPF. If WPF is unfamiliar, let's think about examples in winform. We want to develop a login window in two ways, the first one is our most commonly used one. It is to drag some controls to the form, and the other method is to go to the new Textbox () in the background file (), set the style and position of the textbox. This method is the code-only mode.

Of course, the most common mode is our code-and-markup mode. We are no longer familiar with Visual Studio. We use ASP. net for example ,. aspx layout, we drag the control up, for example, drag a button, then double-click the button, in the background. aspx. implement the button_click event in the CS file.

If C # is for. Net sdk, only the local and csc.exe files used by the development software are available. Of course, the development work flow is also similar, just compile the script and wfc.exe. Of course, I think almost no one will use NotePad to develop a WF project.

Therefore, we do not need to take the time to understand other models. If we talk nonsense, we will step into the topic and be familiar with Visual Studio's development of the WF environment,

2. Visual Studio development environment

Visual Studio is the center of our development workflow. It provides almost all the tools and functions required for workflow development.

Next, let's begin to step into the Visual Studio environment.

Visual Studio provides the following workflow templates:

<1> SharePoint 2007 workflow: used to build a workflow project for Sharepoint

<2> Class Library: the class library is not executable, and the project input is a class library. You can create a class without a host.ProgramSet

<3> console application: This is different from the class library because it contains a host file, which is a Windows console.

Next, let's take a look at the menu items and function options related to workflows provided by Visual Studio.

First, let me enter the design interface:

Right-click the interface and a menu item is displayed:

Of course, you can also click the workflow button on the menu bar:

Among them, the most common functions are:

<1> save it as an image and copy it to the clipboard: This is easy to understand and does not explain much.

<2> Generate a handler: This option automatically generates the event methods required by the workflow on the interface.

<3> View sequentialworklow: This is the default option, that is, to view the default visual interface of the workflow.

<4> View cancellation handler: In this view, you can define a group of activities to be activated when you cancel a workflow.

<5> View error handlers: In this view, you can define a group of activities to be activated when an error occurs in your program.

<6> debugging: this is an important option:

We will frequently use this technology below.

In addition, I will no longer be familiar with interfaces like toolbar and attribute window.

It's too late. Today's content is a little small. I hope you will forgive me.

I want to go to bed and work overtime at the company during the day.

Please pay attention to the following. In the futureArticle.