Packaging Workflows into .NET Code Libraries
The previous lab had you build a console-based workflow application. Using this project template, the
workflow and runtime hosting logic are compiled into a single executable.
In a production-level environment, it would be preferable to package workflows in a dedicated .NET *.dll.
By packaging workflow instances into a .NET code library, you are able to model common business
processes that can be reused easily at a binary level. Therefore, any sort of .NET application (ASP.NET,
Windows Forms, WPF, console programs, other *.dlls, and so on) can make use of the same business
processes. Obviously, this is helpful, particularly when a particular business process, such as credit card
validation, may need to be reused among multiple projects.
Recall that Visual Studio provides Sequential / State Machine Class Library projects. These templates will
provide you with the same design-time experience as seen in your previous lab.
Client applications will reference this *.dll just like any other .NET library. The client application will also
need to construct the infrastructure manually to host the workflow instance in the WF runtime.
The previous lab had you build a console-based workflow application. Using this project template, the
workflow and runtime hosting logic are compiled into a single executable.
In a production-level environment, it would be preferable to package workflows in a dedicated .NET *.dll.
By packaging workflow instances into a .NET code library, you are able to model common business
processes that can be reused easily at a binary level. Therefore, any sort of .NET application (ASP.NET,
Windows Forms, WPF, console programs, other *.dlls, and so on) can make use of the same business
processes. Obviously, this is helpful, particularly when a particular business process, such as credit card
validation, may need to be reused among multiple projects.
Recall that Visual Studio provides Sequential / State Machine Class Library projects. These templates will
provide you with the same design-time experience as seen in your previous lab.
Client applications will reference this *.dll just like any other .NET library. The client application will also
need to construct the infrastructure manually to host the workflow instance in the WF runtime.
.NET Code Libraries
Table of Contents
Copyright (c) 2008. Intertech, Inc. All Rights Reserved. This information is to be used exclusively as an
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
online learning aid. Any attempts to copy, reproduce, or use for training is strictly prohibited.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
Courseware
Training Resources
Tutorials
Services
