what additional considerations should we have when creating a new "custom" activity for use in both a Sequential AND State driven workflow
asked another way:
Do we need to create two different Activities one for Sequential and another for State driven -OR- can we have a single Activity that supports both workflow types
LaVinci.
considerations when designing a new custom Activity
Hot Topic
- problems with vista install error occured setup to boot into next stage
- Compilation failed for Travel Demo
- idle state
- Cleaning Persisted Workflows
- So can I call into Indigo Service ?
- Property declared in Custom State Machine Workflow not accessible in Activity reference
- A problem with the sample "playwnd" in platform builder
- About the Role in WWF
- DigitalTVTuningSpace and MSVidCtl (timeshifting)
- Seeking Suggestions on DirectX - A simple Measuring tool
Windows Vista
- AV's cause access failures.
- ASP.NET and workflow foundation
- regarding passing parameters between workflow and activities
- unresolved linking errors whilst upgrading to visual studio 2005
- build failure
- Windows Vista 5308 install problems
- Custom Properties and SQL Persistence
- Strange problem on XP & VOB files
- Regarding Font Obfuscation - embedding
- taskbar tooltips - please fix!
considerations when designing a new custom Activity
Hiralshah
In general the same activity should work for both types of workflows. However, State Machine workflows do not allow more than 1 (i.e. the first) activity that implements IEventActivity inside the State activity.