Workflow Application part1

To this point we have focused on creating an activity and invoking it in the simplest way possible with the WorkflowInvoker class. The WorkflowInvoker.Invoke method is simple because it is synchronous and invokes the workflow on the same thread as the caller.

Education and Training Interview Question

Q1. ‘Why did you decide to go to college?’
This requires a full answer, and you need to go back to when you left school in order to be able to answer it. What were your long-term ambitions at the time? Were there certain subjects you particularly enjoyed at school and wished to continue to study? How and why did you choose your particular course and your specialist subjects?

Testing Workflows

Up to this point the application is not very interesting. It is only working in a console and does not receive any input arguments. Most applications that do meaningful work will have to deal with input and output arguments. Additionally, the application is not easily tested in its current form.

Interview Questions

Question No. 1: "Tell me about yourself." This is usually the opening Question in an interview and it's the perfect moment for you to toot your own horn -- not to tell your life history. Your answers should be a quick rundown of your qualifications and experience. Talk about your education, work history, recent career experience and future goals.

Dynamic Workflows with XAML

Up to this point we have been authoring workflows in .xaml, .cs or .vb files. These files then get compiled into types that are included in the assembly of the project and run by the workflow runtime. 

The CodeActivity

We have open project from last post Refactoring Workflows as we seen on it, WF4 consists of a designer that edits .xaml files and a runtime that invokes activities. When we author a workflow, we are creating a new kind of activity and because activities are just classes that inherit from System.Activities.Activity or one of its subclasses, we can declare workflows using C#, VB or XAML. In this post, we will implement our “greeting” business process by creating an activity in C# or VB.

Refactoring Workflows

We will refactor the solution created in last post Hello Workflow . Even though we have a working application, we might want to make a few improvements. In this post, as Workflow1 is not a very descriptive name, you will change it to SayHello.

Hello Workflow

Creating a Simple Hello Workflow Application

We will create a very simple workflow that will be the equivalent to this code: