According to Paul Andrew (MS) , to host an WWF workflow in an asp.net app with beta 2 or 2.2 TODAY :
1. if you want your asp.net application to scale (1 http thread), use the ManualWorkflowSchedulerService but your workflow won’t react correctly to timer events.
2.if you want your application to respond correctly to timer events :
, use the DefaultWorkflowSchedulerService, but your workflow won’t run in the http thread and won’t scale well.
This will be fixed in a new release…